Simple Summary
This proposal seeks to update the next_block_delay parameter found in the SynchronyParams under the x/block-time module to reduce the average block time of dYdX Chain.
Abstract
Following the addition of SynchronyParams of the x/block-time module on the dYdX Chain v8.0, as well as the introduction of Designated Proposer Set and Order Gateway under the dYdX Chain v9.0, the dYdX community can now control the next_block_delay and, therefore, optimize the dYdX Chain block time.
We propose to set the next_block_delay to 300ms, replacing the previous value of 400ms. This adjustment is expected to reduce block time and improve trading experience on dYdX.
Motivation / Rationale
Before v9.0, reducing next block delay carried higher risks because proposers were less predictable, and orders could take multiple hops to reach them. Shortening the delay could increase missed blocks or empty blocks if the network wasn’t tightly synchronized.
After v9.0 improvements:
- Designated Proposer Set ensures that block proposers are selected deterministically from a smaller, governance-controlled set of validators. This reduces block-time variance and makes block production more reliable, even with shorter delays.
- Order Gateway introduces a direct, one-hop route from traders to proposers. This means orders reach the proposer faster and more consistently, ensuring that blocks are well-filled even when block times shrink.
These improvements allow for the removal of the “safety buffer” previously needed without compromising liveness or reliability.
Specification
We propose to set the next_block_delay to 300ms.
Next Steps
We welcome community feedback on the proposed update, followed by an on-chain governance vote on Tuesday, September 16, 2025 to implement the change.