# \[DRC\] Proposal for dYdX Protocol Upgrade to v9.6 **URL:** \ **Category:** dYdX Chain\ **Tags:** protocol-upgrade, community-input, drc\ **Created:** [January 23, 2026, 5:13pm UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-6/4973 "2026-01-23T17:13:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dYdX\_Ops\_subDAO](https://dub1.discourse-cdn.com/flex013/user_avatar/dydx.forum/dydx_ops_subdao/32/797_2.png) [@dYdX\_Ops\_subDAO](https://dydx.forum/u/dYdX_Ops_subDAO)\ **Post date:** [January 23, 2026, 5:13pm UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-6/4973/1 "2026-01-23T17:13:49Z")
![v9.6](https://europe1.discourse-cdn.com/flex013/uploads/dydx/original/2X/f/f1810db0dbc864fb01630c50b406db76c181c68c.jpeg) > TL;DR: (summary) > > We would like to submit for consideration a software upgrade proposal for the [dYdX Protocol v9.6](https://github.com/dydxprotocol/v4-chain/releases/tag/protocol%2Fv9.6.0-rc1). This version introduces governance-controlled tuning of tick size and step size for perpetual markets. # Introduction: Hello dYdX Community, We’re bringing to your attention the dYdX Protocol release `v9.6`, which enables the dYdX community to modify market tick size and order step size via governance proposals. If approved, updates are applied consistently across both the CLOB keeper and memclob to keep market behavior in sync. **Note** : the adoption of `v9.6` is subject to software upgrade via a governance proposal. # Specification: Detailed information on `v9.6` can be found in the [release notes](https://github.com/dydxprotocol/v4-chain/releases/tag/protocol%2Fv9.6.0-rc1). Key updates include: - **Governance-driven market parameter updates** - Adds support to update `SubticksPerTick` (tick size) and `StepBaseQuantums` (step size) through governance, with coordinated updates to the CLOB keeper and `memclob` to ensure consistency across the system. **Note** : The GitHub release tag for `v9.6` is `protocol/v9.6.0-rc1`. # Next Steps: Feedback is welcome on this DRC. The dYdX Operations subDAO suggests the following timeline for proceeding with the governance proposal: - **Proposal Submission** : Jan 26, 2026 - **Expected Vote Outcome** : Jan 28, 2026 - **Upgrade Date** : Jan 29, 2026 - **Suggested Block Height** : [73737000](https://www.mintscan.io/dydx/block/73737000) **NOTE** : _We advise that the potential proposer revise the suggested block height at the time of proposing and pick an upgrade height close to 5:00 PM (UTC) on **Jan 29, 2026** - especially in case the ETA of **73737000** has shifted dramatically._ **NOTE** : Please make sure to include the required [info-fields](https://github.com/cosmos/cosmos-sdk/blob/main/x/upgrade/types/upgrade.pb.go#L51) in the proposal. **NOTE** : The protocol software has dropped patch number from upgrade name, therefore mandating the use of `v9.6` in the proposal JSON. — Thank you for your continued participation and support in the governance and improvement of the dYdX Chain. dYdX Operations SubDAO ---
**Author:** ![dYdX\_Ops\_subDAO](https://dub1.discourse-cdn.com/flex013/user_avatar/dydx.forum/dydx_ops_subdao/32/797_2.png) [@dYdX\_Ops\_subDAO](https://dydx.forum/u/dYdX_Ops_subDAO)\ **Post date:** [January 27, 2026, 6:08am UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-6/4973/2 "2026-01-27T06:08:59Z")
Hello, dYdX Community, A patch version for `v9.6` has been released: [Release Release protocol/v9.6.1 · dydxprotocol/v4-chain · GitHub](https://github.com/dydxprotocol/v4-chain/releases/tag/protocol/v9.6.1) We recommend all validators use that in the upcoming `v9.6` upgrade. Also, a proposal for the upgrade has been submitted: [#342](https://www.mintscan.io/dydx/proposals/342) - **Expected Vote Outcome** : Jan 29, 2026 - **Upgrade Date** : Jan 30, 2026 - **Upgrade Block Height** : [73860000](https://www.mintscan.io/dydx/block/73860000) – dYdX Operations SubDAO