-
Notifications
You must be signed in to change notification settings - Fork 42
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
Graft under 51% attack #208
Comments
Great work ! Thanks alot for keep me (and others) update. |
Correction, seems like there was a counter attack to regain some blocks. Maybe only 10, mostly from hashvault, will be orphaned. They were unlucky to have high luck at the wrong time. I think exchanges were informed at some point. |
For future reference: (From https://www.nicehash.com/algorithm/cryptonightv8) EDIT: Note that this is the NiceHash graph of power available to rent on demand, not a chart of Graft hashrate. |
The nominal hashrate seems to be 50% off in that graph. |
Graft Nethash is roughly 10 MH/s and appears to trend around that level. The graph is not showing Graft hashrate, it is showing NiceHash's available power to rent. You'll note that, during the attack and counterattack period, "paying" went up - indicating people were bidding on CryptoNightV8 hashpower - which drove up the actual hashrate available. In other words, the bidding attracted more miners (through automation and manual choices), increasing the hashrate in the NiceHash CryptoNightV8 market. |
Yes, you're right. Sorry about that, I didn't read properly. |
Attacker returned about 15 hours ago, in case anyone noticed. |
Since this issue strongly related to PoW change, it will be closed after merging Reverse Waltz tweak and planning new HF. If you have other suggestions, please, inform me. |
I've been informed a 51% attack on graft began 45 minutes ago. Current blocks may suffer a rollback to 261669. So 261670 up until now could become invalid.
edit: An hour after it began, attacker's chain ended at 261703 while the one it's replacing is at 261696. So it looks like 27-blocks will be orphaned.
The text was updated successfully, but these errors were encountered: