cosmos-sdk: Join mainnet fail with panic "Wrong Block.Header"

Summary of Bug

Follow the Join Mainnet doc but always fail with panic Wrong Block.Header.AppHash:

I[2019-05-02|13:22:35.897] Executed block                               module=state height=1 validTxs=0 invalidTxs=0
I[2019-05-02|13:22:40.438] Committed state                              module=state height=1 txs=0 appHash=442D1FDAF0435EC2BF9884D3A0D222FFCF1EF1C4B8FBA1B9775E1A6501247E78
panic: Failed to process committed block (2:6874A607AABF97B8D0627ADDF4B7501CCE74ECAB82E44A6C4F39A4562D75601B): Wrong Block.Header.AppHash.  Expected 442D1FDAF0435EC2BF9884D3A0D222FFCF1EF1C4B8FBA1B9775E1A6501247E78, got 056A9CA652FC5DD667A19362081216A57A70F87A256FD62B3131673BCDBD969B

Version

$ gaiad version --long
cosmos-sdk: 0.34.3-80-gf4a96fd6
git commit: f4a96fd6b65ff24d0ccfe55536a2c3d6abe3d3fa
go.sum hash: 
build tags: netgo ledger
go version go1.12.4 linux/amd64

Steps to Reproduce

Genesis:

$ curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaiad/config/genesis.json

~/.gaiad$ shasum -a 256 config/genesis.json

1e349fb39b85f7707ee78d39879f9d5d61f4d30f67980bb0bf07bd35b2f8bf30  config/genesis.json

Seed config:

# Comma separated list of seed nodes to connect to
seeds = "ba3bacc714817218562f743178228f23678b2873@public-seed-node.cosmoshub.certus.one:26656"

It’s one of seeds provided here

For Admin Use

Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 21 (7 by maintainers)

Most upvoted comments

@garyyu we’ve had other instances of similar issues. It’s almost certainly to do with your seeds/peers, since you are on the correct version. I’ll try to find some good seeds or persistent peers for you.

alexanderbez on May 4, 2019

It’s usually always one of the following reasons:

Your node is using the wrong app version (and/or) 1a. This can be easy to confirm but the app root hash mismatch can occur at any block really.
Your node is using the wrong genesis file (and/or) 2a. This is easy to confirm – you’ll get an invalid app root hash at block 1
Your node is connected to peer(s) where (1) and/or (2) holds true for them

alexanderbez on May 26, 2020

I have the same issue. To get a mainnet full node running is currently only possible by checking out tag v0.34.3

1ultimat3 on May 7, 2019