Bybit’s November 18 notice set 12:00 UTC as the cutoff for Cosmos-network ATOM deposits and withdrawals around the Cosmos Hub’s Gaia v29.1.0 upgrade, while leaving trading unaffected. By the afternoon review, that scheduled cutoff had passed. The notice directs customers to the funding interface for a reopening alert; it does not establish that transfers have resumed.
The November 18 notice gives an approximate upgrade time of 12:30 UTC and identifies block 33,935,300 as the target. These are not interchangeable commitments. A block height identifies the chain’s upgrade point; a clock estimate helps people plan around it but is not evidence that the transition has happened.
A repair to governance queries
The Gaia developers describe v29.1.0 as a state-breaking release that restores decoding of historical parameter-change proposals. The repair covers governance queries for proposal lists, individual proposals, status filters and tallies, as well as state export. It is a maintenance change to how the chain handles those records.
The release also updates two CosmWasm components, wasmd and wasmvm. Published on November 9, those release notes explain the software; they are not today’s new announcement. The fresh development for exchange customers is Bybit’s funding schedule for the November 18 upgrade.
Access to governance records matters beyond the voting screen. Someone checking a prior decision needs to retrieve the relevant proposal rather than infer it from a balance or a social post. The developers’ description identifies a query-decoding problem. It does not establish that historical votes were changed or that ATOM balances were compromised.
One upgrade, different service windows
Quicknode’s status page marked its Cosmos mainnet maintenance as in progress when checked on November 18 at 16:00 Israel time. It gives a 12:00 to 15:00 UTC maintenance window, an estimated upgrade around 12:50 UTC and possible brief interruptions to its RPC service. RPC is the interface applications use to request chain information and submit transactions.
The different estimates illustrate why an exchange notice and an infrastructure provider’s maintenance window should be read in context. Bybit’s cutoff applies to its funding service; Quicknode’s notice applies to its infrastructure. Neither promises that every wallet or exchange will behave identically during the transition.
What an ATOM holder can check
Before sending ATOM to an exchange, review its current deposit instructions and availability indicator. If a transfer is already underway, preserve the transaction identifier and distinguish the chain record from the exchange’s account-crediting status. A market continuing to trade is not a confirmation that incoming transfers are being credited normally.
Bybit says it will not issue a separate announcement when deposits and withdrawals resume. Its notice instead points customers to the alert function on the deposit or withdrawal page. Reopening therefore needs a service-specific check, not an assumption based on the passage of the estimated upgrade time.
Our Cosmos Hub profile explains ATOM’s role in the network, while the wallet guide distinguishes a self-custody wallet from an exchange account. This scheduled upgrade does not create a replacement asset that holders should buy or swap into. The practical task is to verify the intended transfer route and wait for clear service availability where maintenance applies.