-
Notifications
You must be signed in to change notification settings - Fork 14
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
Error during handshake: error on replay: wrong Block.Header.AppHash. Expected DD1BA... , got BE03... #9
Comments
I am very sorry for the inconvenience. Due to the difference in the upgrade block height between the If you expect to run the testnet, please use |
All of above was done for testnet using container. Using snapshot data and from scratch. Each time failing at random times (at different block heights). I can try using non-container version if that makes any difference. When using snapshot data, it fails with different error:
so I think the version is mismatched. Maybe the snapshot was done using earlier version? Btw where this version is defined, so I can check which I have? |
Which branch has the latest testnet changes? |
We are very sorry, we submitted the wrong testnet docker image, we have fixed it, please re-acquire |
Because we have upgraded the testnet many times, resynchronization will check the fork as soon as possible. You can use the
|
The master branch is the latest, and the testnet branch is to be compatible with the old developer documentation. The seed nodes provided by both versions are available. After a period of time, we will abandon the testnet branch. I’m sorry to bring it to you trouble. |
No worries, good the problems has been discovered, I'll re-test now using the fixed container. |
While started a testnet node with sync from scratch:
Can you try to upgrade
tendermint
to the latest? Maybe it's going to help.As for the workaround, I can only try to re-do the sync again.
Related: cosmos/cosmos-sdk#10281
--
I've also tried from the snaphot (2021-11-08), similar error:
Another one after re-run from scratch:
The text was updated successfully, but these errors were encountered: