Solve for %51 attact #21282

issue onuratakan opened this issue on February 23, 2021
  1. onuratakan commented at 5:43 PM on February 23, 2021: none

    Is your feature request related to a problem? Please describe. Yes, this problem is security problem for pow consensus protocol.

    Describe the solution you'd like Solution is basic, the new consensus algorithm Safe Proof of Work, blocks will have a two hash block, and miner select from random, first hash mining or second hash mining. this is changed all mining proccess. And add into the hash, the merkle root of the blocks of the blockchain the miners wants to add. If first hash blocks merkler root not equal second hash blocks merkle root, all nodes and miners restart process.

    Describe alternatives you've considered If you want to know more, you can check the my github repository. (onuratakan/SPOW) I published with mozilla public license.

  2. onuratakan added the label Feature on Feb 23, 2021
  3. CrommVardek commented at 6:07 PM on February 23, 2021: none

    So a miner can force a process to restart by adding an erroneous hash block ?

  4. sipa commented at 6:09 PM on February 23, 2021: member

    Discussions about fundamental changes to Bitcoin belong on the bitcoin-dev mailinglist, not the issue tracker of one single implememtation.

  5. sipa closed this on Feb 23, 2021

  6. fanquake locked this on Feb 23, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-02 12:14 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me