-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-Algo - Defence against 51% attacks? #100
base: 0.14.0
Are you sure you want to change the base?
Conversation
and print in debug log. fix getblocktemplate to use miningAlgo
…culty as well as algorithm used to mine each block. also exposing the PoW hash
check for invalid algo ids. prevent versionbits producing errors due to algo encoding
Very cool to see, and you've already done a lot of the leg work too. Kudos for the pull request! |
Wouldn't this theoretically increase the risk of a 51% attack given attack vectors and unknown unknown's of a PoW's attack surface to an attack vector? Similar to the theoretic sides of cryptography on when it makes sense to combine methods vs not (rarely). Not to shoot this down (cool idea) but what type of formalism can we use to at least semi-formalize this? |
What's here is the foundation for migrating VTC to a multi-algo coin. History has shown this to be far more resilient to 51% attacks than a traditional single PoW algorithm.
What needs more time, attention, and discussion: