panic: unknown field "abstain" in v1.TallyResult

[iamyulong]

Hi, we're getting the following error when launching a testnet node. Can someone help?

11:45AM INF Optimistic execution disabled module=main
11:45AM INF starting node with ABCI CometBFT in-process module=main
11:45AM INF State store key layout version  module=main version=vv1
11:45AM INF Blockstore version module=main version=v1
11:45AM INF WARNING: deleting genesis file from database if present, the database stores a hash of the original genesis file now module=main
11:45AM INF service start impl=multiAppConn module=proxy msg="Starting multiAppConn service"
11:45AM INF service start connection=query impl=localClient module=abci-client msg="Starting localClient service"
11:45AM INF service start connection=snapshot impl=localClient module=abci-client msg="Starting localClient service"
11:45AM INF service start connection=mempool impl=localClient module=abci-client msg="Starting localClient service"
11:45AM INF service start connection=consensus impl=localClient module=abci-client msg="Starting localClient service"
11:45AM INF service start impl=EventBus module=events msg="Starting EventBus service"
11:45AM INF service start impl=PubSub module=pubsub msg="Starting PubSub service"
11:45AM INF service start impl=IndexerService module=txindex msg="Starting IndexerService service"
11:45AM INF ABCI Handshake App Info hash=E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 height=0 module=consensus protocol-version=0 software-version=v1.16.0-beta.4
11:45AM INF ABCI Replay Blocks appHeight=0 module=consensus stateHeight=0 storeHeight=0
11:45AM INF InitChain chainID=injective-888 initialHeight=2533984 module=main
11:45AM INF initializing blockchain state from genesis.json module=main
11:45AM INF Closing application.db module=main
11:45AM INF Closing snapshots/metadata.db module=main
panic: unknown field "abstain" in v1.TallyResult

We followed this guide, https://docs.injective.network/infra/join-a-network

[iamyulong]

Just to report back that this is only an issue if you try to sync from scratch.

We can work around this by downloading the state snapshot.

Thanks for the help offered by the team!