Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add delay period to tendermint client #7133

Open
3 tasks
Tracked by #7134
colin-axner opened this issue Aug 12, 2024 · 0 comments
Open
3 tasks
Tracked by #7134

Add delay period to tendermint client #7133

colin-axner opened this issue Aug 12, 2024 · 0 comments

Comments

@colin-axner
Copy link
Contributor

Summary

Add a delayPeriod to the tendermint client state

Problem Definition

With eureka, the connection layer is removed entirely. If we want to support the ability for clients to have delay periods to increase security, we should add it to the tendermint client (any other clients which would like to add this feature should also add it)

Proposal

Add the delay period to the tendermint client. Set it to 0 by default (this should allow the client state encoding to remain unchanged for backwards compatibility - soon shouldn't be a consideration with removal of self client/consensus state validation).

In Eureka, setting the client to a non-zero delay period would be no problem and give support for delay periods.

In classic, it would be a problem, only if the two chains haven't updated to: v7.8+, v8.5+, v9+. To remedy and support a removal of the connection layer entirely, we should:

Thus, if connections have non zero delay periods, gov can choose to update or leave as is for the underlying client before we remove connections and thus create the same fundamental security layer for connections sharing the same client.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo 🏃
Development

No branches or pull requests

2 participants