-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reorg ropsten solution #2419
Reorg ropsten solution #2419
Conversation
Just fyi, I'm already reorging ropsten, for geth you would just need to full sync with the fixed version (which rejects the bad block) and then mine on top. I'm at 10,682,071 which is ~2000 blocks ahead from the bad block. But the bad chain keeps on advancing too |
Thank you! The reason I am doing this PR is to make sure we have tools to do something like this on the main net, if it happens |
* Reorg ropsten solution * Add option * Print TD recalc * Correct fix for eip1559 * Try to fix the unwind * Print header progress and hash * Not insert descendants of bad headers * Print some more * Print less * Better way of marking bad headers * Disable inSync * Penalise peers who give incorrect chain pieces * better fix for initial cycle * Clean up Co-authored-by: Alexey Sharp <alexeysharp@Alexeys-iMac.local>
No description provided.