Summary
This is a proposal to update the next_block_delay parameter found in SynchronyParams under the x/block-time module with the goal of reducing block times on the dYdX Chain.
Abstract
The v8.0 protocol upgrade on the dYdX Chain introduced SynchronyParams under the x/block-time modules that enables governance to control the next_block_delay parameter, which can be used to define block times.
We propose setting the next_block_delay to 400ms, replacing the existing timeout_commit configuration of 500ms across most validators. In doing so, the adjustment is expected to reduce block times by 100ms, improving network efficiency and performance.
Motivation
The next_block_delay parameter was introduced as a replacement to the now depracted timeout_commit parameter, serving a similar purpose of defining the time delay between the last block and the start of the next height. This allows the protocol to configure the delay globally, instead of depending on each individual validator node setting their own delay period with timeout_commit. More information on the rationale for deprecating timeout_commit can be found here.
With this change, the protocol improves the predictability of block times by enforcing post-commit delays across all nodes and validators. By setting next_block_delay to 400ms, we hope to improve block production speeds with greater consistency, making the dYdX Chain run more efficiently.
Specification
The proposal will update the protocol’s next_block_delay parameter to 400ms, enforcing a consistent post-commit duration, while deprecating the use of timeout_commit across validators.
Next Steps
We welcome community feedback on the proposed update, followed by an on-chain governance vote on Monday, March 10, 2025 to implement the change.