Bybit published a June 29 announcement saying it will support the Nibiru v2.15.0 network upgrade, expected around June 30, 2026 at 02:00 UTC or block height 42,739,079.
For Radar, this is a protocol operations item because the announcement says NIBI deposits and withdrawals will be suspended from June 30, 2026 at 01:00 UTC.
What Happened
The exchange support notice gives both an expected upgrade time and a wallet-pause start time.
That makes the source-backed event date June 30, 2026, while the announcement date is June 29, 2026.
Why It Matters
Network upgrades become user-facing risk when exchange wallets pause before the chain event. A user planning transfers, bridging or exchange settlement needs the pause time before moving funds.
The owner-fit angle is chain operations: confirm official upgrade status, avoid last-minute transfers and document whether exchange routes are temporarily unavailable.
What To Watch Next
Watch Bybit status updates around June 30, 2026 at 01:00 UTC and the expected 02:00 UTC upgrade window.
Also check Nibiru ecosystem channels before assuming deposits or withdrawals have resumed.
Execution Notes
This update should be used as a decision-support note, not as a standalone instruction to bet, trade, bridge, claim or move funds. The source date, event date and published timestamp need to stay aligned because the useful window is tied to the official notice or schedule. If the source changes after publication, the next check should start from the official page rather than from a copied summary.
For Bybit Nibiru v2.15.0 Upgrade Support Sets June 30 Deposit Withdrawal Pause Window, the practical next step is to verify whether the reader's own route is actually affected. That means checking bookmaker rules and market availability for betting items, exchange balances and order templates for trading items, or wallet/deposit status for protocol operations. If the route is unaffected, the item remains context; if it is affected, the pass condition should be written before any new exposure is added.
Continue this cluster
Continue this cluster with related june 29 network upgrade ops items that keep the same event source-backed while separating owner intent.
