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

Reduce ZetaChain Blocktime #3681

Open
CharlieMc0 opened this issue Mar 10, 2025 · 2 comments
Open

Reduce ZetaChain Blocktime #3681

CharlieMc0 opened this issue Mar 10, 2025 · 2 comments
Labels
epic Group issues under a high-level objective feature:idea An early idea for a feature. Used as reference to follow new feature integrations

Comments

@CharlieMc0
Copy link
Member

We want to reduce the ZetaChain blocktime down to 2 or 3 seconds. This will make it easier for developer and users to submit data on-chain and reduces the wait time after submitting a transaction. It also makes are more competitive with other L1s when comparing specs side to side.

Describe the solution you'd like
Ultimately we want 3 seconds or faster block times. I think 2 seconds is achievable with minimal changes.

@CharlieMc0 CharlieMc0 added epic Group issues under a high-level objective feature:idea An early idea for a feature. Used as reference to follow new feature integrations labels Mar 10, 2025
@CharlieMc0
Copy link
Member Author

These are the subtasks I know about but there are probably more I am not thinking of.

  • Remove any hardcoded references to the 6 second block time
  • Ensure emissions calculations are updated
  • Force all nodes to update their timeout_commit and other values in config.toml at upgrade time.

@swift1337
Copy link
Contributor

I think this one (#350) is a blocker as well...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Group issues under a high-level objective feature:idea An early idea for a feature. Used as reference to follow new feature integrations
Projects
None yet
Development

No branches or pull requests

2 participants