terra-money/core

wrong Block.Header.LastResultsHash

gitmewai opened this issue · 1 comments

We are setting up a new terra 2.0 node under pisco-1 testnet using the latest terrad v2.1.4. We used the snapshot from https://snapshots.synergynodes.com/terra_v2_testnet/terra_v2_1749961.tar.lz4 to sync the node.

The block started syncing from 1749961 and up to 1755427. Then the following error is observed:

Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF executed block height=1755426 module=state num_invalid_txs=0 num_valid_txs=1
Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF commit synced commit=436F6D6D697449447B5B31333920332031363620323138203930203330203136382031343720313531203130302039342031333820313938203830203938203234332032323620363620313820313533203139332032333420393220323531203738203539203138312037312032353520313431203231312033305D3A3141433932327D
Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF committed state app_hash=8B03A6DA5A1EA89397645E8AC65062F3E2421299C1EA5CFB4E3BB547FF8DD31E height=1755426 module=state num_txs=1
Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF indexed block height=1755426 module=txindex
Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF minted coins from module account amount=678526331uluna from=mint module=x/bank
Oct 24 02:07:36 terra-node terrad[2627]: 2:07AM INF executed block height=1755427 module=state num_invalid_txs=0 num_valid_txs=3
Oct 24 02:07:37 terra-node terrad[2627]: 2:07AM INF commit synced commit=436F6D6D697449447B5B3137312032353520313139203132203439203932203135322034372034382034392031353420313432203233203233372031373620323820313438203234203138322031363320363020313036203231342035332034302035203130392031203130302031333420313739203135335D3A3141433932337D
Oct 24 02:07:37 terra-node terrad[2627]: 2:07AM INF committed state app_hash=ABFF770C315C982F30319A8E17EDB01C9418B6A33C6AD63528056D016486B399 height=1755427 module=state num_txs=3
Oct 24 02:07:37 terra-node terrad[2627]: 2:07AM ERR Error in validation err="wrong Block.Header.LastResultsHash.  Expected 969C125A2FE1B959758161FC219ECFDA9FE9AFB32DF4697D3C74AA16FDA56F82, got B695DA4E3DC3A3F625F28EB9C4125F6AD9DD4D0B533769C3C1152520B7ED1B7A" module=blockchain
Oct 24 02:07:37 terra-node terrad[2627]: 2:07AM ERR Stopping peer for error err="blockchainReactor validation error: wrong Block.Header.LastResultsHash.  Expected 969C125A2FE1B959758161FC219ECFDA9FE9AFB32DF4697D3C74AA16FDA56F82, got B695DA4E3DC3A3F625F28EB9C4125F6AD9DD4D0B533769C3C1152520B7ED1B7A" module=p2p peer={"Data":{},"Logger":{}}

Our questions:

  1. Is v2.1.4 supported on pisco-1? Or which latest version should be used on pisco-1 testnet?
  2. Is there any hardfork at v2.1.4 on phoenix-1 mainnet? (However, we cannot test the upgrade with the same binary on pisco-1 testnet first)
  3. What is the plan on using single binary across pisco-1 and phoenix-1 networks?

Thanks!

pisco-1 version is presently v2.2.0
A governance proposal is being created to upgrade phoenix-1 to the same release version (v2.2.0)