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

Notes on changing SLOT_DURATION #389

Open
seunlanlege opened this issue Feb 27, 2025 · 0 comments
Open

Notes on changing SLOT_DURATION #389

seunlanlege opened this issue Feb 27, 2025 · 0 comments

Comments

@seunlanlege
Copy link
Member

seunlanlege commented Feb 27, 2025

Hyperbridge nexus currently uses a slot duration of 12 seconds on mainnet. If for whatever reason, this needs to change, whether to support elastic scaling. It's important that connected chains do not learn of an incorrect state commitment timestamp, more critically a timestamp that is incorrectly greater than hyperbridge's timestamp as this enables timeouts for arbitrary requests, even delivered ones.

So updating the SLOT_DURATION requires some coordinated effort. Solochains and parachains must disconnect from hyperbridge before it performs it's slot duration change. Only reconnecting with the updated slot duration after the change is completed. Evm chains must be configured with a new consensus client ahead of the change, so they never calculate the incorrect timestamp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant