Callum Waters

Yeah. I'm going to close this PR in favour of https://github.com/tendermint/tendermint/pull/9261.

Closing in favour of #9459

> What do you mean the same? async just sends the transaction w/o waiting for CheckTx Yeah that's what I thought until I was looking at the code recently. Seems...

I think in v0.37 we will look to simplify broadcasting txs to a single method. It's redundant to add the asynchronous method when txs can already be submitted in parallel.

I've started making some modifications to support changes to the store an application has (so we have the correct stores and module for each version as these affect the app...

Ok latest update. Stores are the same. We have an apphash mismatch with upgrade: `main`: `E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855` `v1.x`: `EF4C6B20D316A771F8841921A97CEA58E911391A7A90E374E3A2BDB57DCC4522` Note that for main, the hash is for an empty store

This turned out to be the problem: https://github.com/celestiaorg/celestia-app/blob/91b6827a80ef8a4d0048ca81f9eda4c88f37a2ef/app/app.go#L577 Which btw is totally useless since we don't even use the upgrade keeper for that

Also got this error when statesyncing: ``` 11:33AM INF Applied snapshot chunk to ABCI app chunk=54 format=2 height=1258500 module=statesync total=56 11:33AM ERR failed to restore snapshot err="multistore restore: cannot import...

Can confirm that I got the exact same app hash mismatch at height 44. I will start posting my progress on it here.

Ok so module hashes are as follows: For `main`: ``` key KVStoreKey{0xc0010ba1e0, acc} hash D15BFF423553FBC6B2F5DF05087DC756EC5256B5BF7DA3F3D92C7BB9AF1FE295 key KVStoreKey{0xc0010ba1f0, authz} hash E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 key KVStoreKey{0xc0010ba200, bank} hash 672309A593A157B6371E46C448EA955ECC51849968813D50D29FBAE1D8BF9FD4 key KVStoreKey{0xc0010ba210, staking} hash 49E515A45D96E3FFA4B3031FD5F0F6212127CDEF0592158F326D8BE6A489A84A...