-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
mismatched block state root on mainnet #7188
Comments
I can add to this as well. I have a reth alpha 22 instance that recently ran across this
using db format 1 as this is still alpha that particular instance will run for approx 8 min and then die due to the above. |
Was anyone here able to move forward without deleting the entire data dir and start over? |
Hi @argakiig / @pires are you still experiencing state root mismatch? if so, could you send the most recent ~50-100 lines of failure logs, and the full output of |
I have not had the issue in quite a bit thankfully |
Good to hear! @0xc0ffeebabeeth forgot to tag you in the above comment - mind providing that info if you're still experiencing this? |
Fixed in #7753. |
Describe the bug
The error initally happened after upgrading from reth alpha 9 to 22 at block height ~19426610.
After downgrading to alpha 21 it initally seemed to move on just fine with syncing, but subsequently failed at 19426745:
Steps to reproduce
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
Official reth-v0.1.0-alpha.21, reth-v0.1.0-alpha.22 and reth-v0.1.0-alpha.9 builds from github releases.
What database version are you on?
Nuked the box and resynced with reth beta, presumably the default one of reth 9 since thats what was initally synced with.
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: