Tracking issue for tendermint v0.34

[tac0turtle]

This issue is meant as a tracking issue for the upcoming tendermint release and things that need to be completed in the sdk:

• Evidence is capped to an absolute number. max_num was added to consensus evidence params
• Add block pruning support #6164 ABCI update for block pruning. ResponseCommit.retain_height which gives the applicaiton control over block pruning.
• Application should change tendermint consensus params: Add an ability to update ConsensusParams #6197
• All key types will be migrated to []byte instead of an array.
• Tendermint removed libs.KV, this is used in the sdk, it will need to be brought back in the sdk
• Tendermint will allow runtime indexing.
• Support arbitrary initial height #7018
• Return app hash from InitChain #7020 (PR Return app_hash in InitChain #7208)
• Add state sync support #7166
• SDK handling of new evidence types #7190 (PR Cleanup of evidence types #7251)
• update to final release version 0.34.0
• register new evidence type with amino (Cleanup of evidence types #7251 (comment))

Here is the Tendermint v0.34 tracking issue: tendermint/tendermint#5288

For Admin Use

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

[cmwaters]

This might be relevant here. The new evidence that can be detected and committed to a block is:

• DuplicateVoteEvidence
• PhantomValidatorEvidence
• LunaticValidatorEvidence
• AmnesiaEvidence

It is also possible to commit PotentialAmnesiaEvidence but the consensus algorithm alone won't do it.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tac0turtle]

* DuplicateVoteEvidence

* LunaticValidatorEvidence

* AmnesiaEvidence

phantomevidence was removed

[tac0turtle]

tm-db 0.6.x is returning more errors now instead of panicking. A walkthrough of the code base is recommended to check errors.

[clevinson]

@marbar3778 is it required for 0.40 that we update x/evidence to hande the new evidence types above?

[tac0turtle]

@marbar3778 is it required for 0.40 that we update x/evidence to hande the new evidence types above?

It is recommended but if not then IF something happens the sdk wont handle it. @cwgoes if the evidence updates don't land in 0.40 would it be a problem?

[cwgoes]

@marbar3778 is it required for 0.40 that we update x/evidence to hande the new evidence types above?

It is recommended but if not then IF something happens the sdk wont handle it. @cwgoes if the evidence updates don't land in 0.40 would it be a problem?

The SDK definitely needs to handle all evidence types Tendermint might send over ABCI and slash validators accordingly, yes.

[robert-zaremba]

@marbar3778 , there are still few open issue.
Is there anything we should help / watch on coming from the Tendermint side?

[tac0turtle]

@marbar3778 , there are still few open issue.
Is there anything we should help / watch on coming from the Tendermint side?

Everything from the Tendermint side is almost complete, outstanding is evidence.

The only thing I would say is outstanding on the SDK side is block pruning support.

[robert-zaremba]

Thanks, are there going to be any changes which will require updates on this work (SDK side)?

[tac0turtle]

Thanks, are there going to be any changes which will require updates on this work (SDK side)?

I don't see any changes needed after your PR is merged, but take that with a grain of salt. lol 😄

[tac0turtle]

This issue can be closed, not sure the benefit of keeping it open for only updating to the latest release of tendermint?