# \[DRC\] Proposal for dYdX Protocol Upgrade to v9.8

**URL:** <https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-8/5165>\
**Category:** dYdX Chain\
**Tags:** protocol-upgrade, community-input, drc\
**Created:** [October 7, 2026, 2:56pm UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-8/5165 "2026-10-07T14:56:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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:** [October 7, 2026, 2:56pm UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-8/5165/1 "2026-10-07T14:56:48Z")

</div>

![dYdX Protocol Upgrade v9_8](https://europe1.discourse-cdn.com/flex013/uploads/dydx/original/2X/5/51b814d97bfd182793d54539ac2a6f8d92344539.jpeg)

> TL;DR: (summary)
> 
> We would like to submit for consideration a software upgrade proposal for the **dYdX Protocol v9.8**. This version introduces **sensitive** security fixes produced from a private fork of the public dydxprotocol repository.

# Introduction:

Hello dYdX Community,

We’re bringing to your attention the dYdX Protocol release `v9.8`, which addresses sensitive security topics and will thus be released from a private fork of the public `dydxprotocol` repo.

**Note** : the adoption of `v9.8` is subject to software upgrade via a governance proposal.

# Specification:

Detailed information on `v9.8` should be uploaded post-rollout on the [public protocol GitHub repository](https://github.com/dydxprotocol/v4-chain) only after dYdX Labs have made the decision to disclose them.

The `v9.8` binaries are made available under `https://dydx-protocol-releases.s3.ap-northeast-1.amazonaws.com/releases/` - the security patches location that has been used in the past:

- `https://dydx-protocol-releases.s3.ap-northeast-1.amazonaws.com/releases/v9.8.0-9ab4e17a/dydxprotocold-v9.8.0-linux-arm64.tar.gz`

- `https://dydx-protocol-releases.s3.ap-northeast-1.amazonaws.com/releases/v9.8.0-9ab4e17a/dydxprotocold-v9.8.0-linux-amd64.tar.gz`

```auto
dYdX Protocol Release
version: v9.8.0
build-date: 2026-10-06

sha256:
  dydxprotocold-v9.8.0-linux-amd64.tar.gz ea887b0909dcf2a5b762d4d935b47ce59a6a712ba79ade92372a0cd8c936f80a
  dydxprotocold-v9.8.0-linux-arm64.tar.gz 8eb9be61cde8f94efe90a0da9005c4334990d263ac6696aa413fe6eb161bb605

To verify:
  shasum -a 256 dydxprotocold-v9.8.0-linux-*.tar.gz
  # compare each line against the values above

```

# Next Steps:

Feedback is welcome on this DRC. The dYdX Operations subDAO suggests the following timeline for proceeding with the governance proposal:

- **Proposal Submission** : Oct 8, 2026
- **Expected Vote Outcome** : Oct 11, 2026
- **Upgrade Date** : Oct 12, 2026
- **Suggested Block Height** : [109170000](https://www.mintscan.io/dydx/block/109170000)

**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 **Oct 12, 2026** - especially in case the ETA of **109170000** 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.8` in the proposal JSON.

—

Thank you for your continued participation and support in the governance and improvement of the dYdX Chain.

dYdX Operations SubDAO

---

<div class="post-metadata">

**Author:** ![eguegu](https://dub1.discourse-cdn.com/flex013/user_avatar/dydx.forum/eguegu/32/1113_2.png) [@eguegu](https://dydx.forum/u/eguegu)\
**Post date:** [October 8, 2026, 2:27am UTC](https://dydx.forum/t/drc-proposal-for-dydx-protocol-upgrade-to-v9-8/5165/2 "2026-10-08T02:27:09Z")

</div>

We’ve submitted this [proposal-398](https://www.mintscan.io/dydx/proposals/398).  
Don’t miss the change to vote!