Skip to content
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.

Sign up for GitHub

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

Jump to bottom

blockchainReactor validation error: wrong Block.Header.AppHash #97

Open
xueyuchen opened this issue Mar 9, 2023 · 3 comments
Open

blockchainReactor validation error: wrong Block.Header.AppHash #97

xueyuchen opened this issue Mar 9, 2023 · 3 comments

Comments

@xueyuchen
Copy link

block number: 804212

block height not change, how can i fix this problem? THX

ERR Stopping peer for error err="blockchainReactor validation error: wrong Block.Header.AppHash.  Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76, got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815" module=p2p peer={"Data":{},"Logger":{}} server=node
@tster
Copy link

tster commented Mar 22, 2023

For an archive node, try using the patched v2.0.2 binary where you would usually upgrade to v2.0.0.

Full guide: https://docs.canto.io/canto-node/archive-node

@xueyuchen
Copy link
Author

thx

@AndreMiras
Copy link

I no longer see the v2.0.2 tag, I guess the code is still in the thomas/archive-patch branch, but could we tag it still?
That would make things easier for people syncing archive nodes from scratch

AndreMiras added a commit to AndreMiras/docker-canto that referenced this issue Jan 5, 2025
@AndreMiras
✨ Build thomas/archive-patch as 2.0.2
b6d8dd4 
2.0.0 is leading to a AppHash at block 804212.
This is fixed via thomas/archive-patch, but not tagged as of 2025/01.
The error was:
```
validation error: wrong Block.Header.AppHash.
Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76,
got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815
```
See upstream issue for more details:
Canto-Network/Canto#97
AndreMiras added a commit to AndreMiras/docker-canto that referenced this issue Jan 5, 2025
@AndreMiras
✨ Build thomas/archive-patch as 2.0.2
81d1894 
2.0.0 is leading to a AppHash at block 804212.
This is fixed via thomas/archive-patch, but not tagged as of 2025/01.
The error was:
```
validation error: wrong Block.Header.AppHash.
Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76,
got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815
```
See upstream issue for more details:
Canto-Network/Canto#97
AndreMiras added a commit to AndreMiras/docker-canto that referenced this issue Jan 5, 2025
@AndreMiras
✨ Build thomas/archive-patch as 2.0.2
5df5905 
2.0.0 is leading to a AppHash at block 804212.
This is fixed via thomas/archive-patch, but not tagged as of 2025/01.
The error was:
```
validation error: wrong Block.Header.AppHash.
Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76,
got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815
```
See upstream issue for more details:
Canto-Network/Canto#97
AndreMiras added a commit to AndreMiras/docker-canto that referenced this issue Jan 5, 2025
@AndreMiras
✨ Build thomas/archive-patch as 2.0.2
91c2f8d 
2.0.0 is leading to a AppHash at block 804212.
This is fixed via thomas/archive-patch, but not tagged as of 2025/01.
The error was:
```
validation error: wrong Block.Header.AppHash.
Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76,
got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815
```
See upstream issue for more details:
Canto-Network/Canto#97
AndreMiras added a commit to AndreMiras/docker-canto that referenced this issue Jan 6, 2025
@AndreMiras
✨ Build thomas/archive-patch as 2.0.2
fe3ecc1 
2.0.0 is leading to a AppHash at block 804212.
This is fixed via thomas/archive-patch, but not tagged as of 2025/01.
The error was:
```
validation error: wrong Block.Header.AppHash.
Expected AE0346892A400D6EB0B956FC5B5806FCCEE5A5679102E6DFD8BEE92BE40DDD76,
got 374EC05458F04346A1F0F97EFB0DDF9133F510EF28F453849955FC0C23539815
```
See upstream issue for more details:
Canto-Network/Canto#97
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AndreMiras @tster @xueyuchen