Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

State root of best block header always valid #96

Closed
plexar88 opened this issue Nov 13, 2020 · 5 comments
Closed

State root of best block header always valid #96

plexar88 opened this issue Nov 13, 2020 · 5 comments
Labels
duplicate This issue or pull request already exists user-report User report

Comments

@plexar88
Copy link

Before filing a new issue, please provide the following information.

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

Thread 'IO Worker #2' panicked at 'State root of best block header always valid.: InvalidStateRoot(0xc9c4d3176e7b19d5f6b378feea89f3d760aab017cd7d45b5abbd5531bdfd1477)', ethcore/src/client/client.rs:1179

@rakita
Copy link
Contributor

rakita commented Nov 13, 2020

Hi, this looks like #69

@plexar88
Copy link
Author

I removed few last blocks with "openethereum db reset xx" and now it start with message "State root not found for block #11247017 (f6d42a06fcf4dd642d8296e97e346908aaf47507d4ec27fb5ab98a36c4822585)" then stop with error "Thread 'IO Worker #0' panicked at 'State root of best block header always valid.: InvalidStateRoot(0x4a9cd3c47d3a6c8dbbd6461a3a52bbc1628b066aafad612acf5a2a4c39105a57)', ethcore/src/client/client.rs:1179" How I can fix it without remove db and start synch agan?

@rakita
Copy link
Contributor

rakita commented Nov 13, 2020

Did you execute 3 and 4th step from here: https://gist.github.com/adria0/1a4505e1823373b03db37a0de5e92b75

@plexar88
Copy link
Author

I got error on step 3: "Found argument 'experimental-drop-future-blocks' which wasn't expected, or isn't valid in this context". I compiled it from sources https://github.com/openethereum/openethereum/tree/adria0/dbtools then run .target/release/openethereum db experimental-drop-future-blocks --base-path path-to-my-blockchain-storage

@adria0 adria0 added the user-report User report label Nov 18, 2020
@rakita
Copy link
Contributor

rakita commented Dec 4, 2020

Duplicate of #69, fix is made here: #149

@rakita rakita closed this as completed Dec 4, 2020
@rakita rakita added the duplicate This issue or pull request already exists label Dec 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists user-report User report
Projects
None yet
Development

No branches or pull requests

3 participants