The dYdX Chain status page still carried a deposit-and-withdrawal pause notice when checked on November 18 at 16:00 Israel time. The November 17 incident says the team is moving USDC to an Injective route and working with Skip to enable it. A familiar token balance does not establish that a familiar deposit route is available.

The exchange notice names block 114,220,000 as the upgrade target. Separately, the protocol’s release notes describe a move from Noble-backed USDC to Injective-backed USDC. These are two distinct records: Bybit describes its own funding arrangements, while the software release describes what the chain is designed to do.

The status notice and the software plan

The incident opened at 15:47 UTC on November 17. Its latest displayed update, at 16:07 UTC, said work on a fix was continuing. At this review, the page marked the trading frontends as degraded while listing the chain protocol as operational. Those labels describe different parts of the service; protocol availability does not cancel a transfer warning.

Bybit separately announced support for the v9.9.0 upgrade on November 17. The protocol release explains why the direction of a USDC transfer matters.

The same balance can sit behind a different route

According to the dYdX release notes, the migration preserves the existing USDC asset identifier and denomination. Existing balances, positions, orders and MegaVault shares are not meant to change. That continuity matters because a transfer-route change need not require users to exchange one displayed balance for another.

The upgrade handler enters a gradual migration mode. From the upgrade height, the release specifies that new Noble-origin USDC deposits are rejected, with an error acknowledgment that returns the funds on Noble. Withdrawals toward Noble remain available under existing rate limits. Injective USDC deposits and withdrawals use the existing connection to that chain.

This is a description of the published software behavior, not an independent confirmation that every application or service has completed the transition. It also does not establish the timing of a particular user’s refund or exchange credit.

Bybit’s funding notice has a narrower scope

Bybit said DYDX-network deposits and withdrawals would be suspended around the upgrade while trading remained unaffected. It directs customers to the deposit or withdrawal page for a resumption alert and says it will not publish a separate reopening announcement.

That notice concerns the exchange’s DYDX funding service. It should not be read as a universal status report for USDC transfers throughout the dYdX ecosystem. Nor does an active trading screen demonstrate that withdrawals are enabled. A customer can have access to an exchange market while the relevant transfer channel is under maintenance.

Check the direction before sending

For a transfer, the useful question is specific: which asset is moving, from which chain, through which service, to which destination? Writing down those four details is more informative than asking whether “dYdX deposits” are open. The route used to bring funds in may have different conditions from the route used to take them out.

Before authorizing a transfer, compare the sending service’s selected network with the receiving service’s current instructions. If the receiving interface does not clearly support the proposed route, resolve that uncertainty before sending. Do not use an old successful transfer as proof that the same path remains supported after an upgrade.

The broader mechanics are covered in our guides to stablecoin networks and backing and cross-chain transfers. For this upgrade, the key distinction is directional: the published plan preserves existing accounting while changing how new USDC can arrive. Actual availability still needs to be checked at the service being used.