Tendermint 35.6 Testing Release

[faddat]

• chore: tm 0.34 changes cosmos/cosmos-sdk#12221

... is a reversion from tm 35 to 34 because of what sounds like the same issue that we had with our testnet. I believe that these issues stem from problems in pure propagation in tendermint 35.

How much like middle wear this is another crossroads for us. We will need to Refactor CW and ABC go once again if SDK 46 reverts to TM 35. I assume that the changes will be approximately as large as the middle where changes so about one week on timeline. When I was speaking with Chalabi earlier he suggested, why don't we put up a test net work and invite maintainers at https://github.com/tendermint/tendermint to run nodes, so that we can all try and solve the problem.

So I am cutting a testnet from the current code after only a brief review.

the goal is to enable the sdk to ship with tm 35, and to fix the bug in tm 35.

[faddat]

Please put any blockers to putting up a very fast testnet (we don't need all features just need to know our chaincode is sound) with our more experienced validators, and inviting the tendermint team here.

[Reecepbcups]

as per cosmos/cosmos-sdk#12221, tm was revered back to v0.34.20 instead of the 35.6. closing