Osmosis (OSMO) - Delayed Sends and Receives
- Published
- Updated
Coinbase flagged delayed sends and receives on the Osmosis network on Nov. 12 and said buys, sells, and fiat withdrawals and deposits were not affected. Upbit then suspended Osmosis deposits and withdrawals after a network failure, while OSMO trading stayed open, and block production later resumed after a roughly four-hour interruption.
Key claims & sources
What it means
Osmosis is the leading decentralized exchange built on the Cosmos SDK, using CometBFT consensus and the Inter-Blockchain Communication protocol to let assets move natively between Cosmos app-chains. Its OSMO token funds liquidity pools and pays gas for interchain swaps. Exchanges like Coinbase and Upbit list OSMO and process onchain sends and receives separately from their internal matching engines, which is why trading and transfers can diverge during a chain-level fault.
During the roughly four-hour halt, Coinbase users could still buy, sell, and move fiat, but any onchain send or receive of OSMO sat delayed until block production resumed. Upbit went further and froze both deposits and withdrawals outright, leaving traders able to buy and sell OSMO on its order book but unable to move the asset onto or off the exchange. Arbitrageurs who shift OSMO between Upbit, Coinbase, and onchain wallets were locked out until the network recovered.
A consensus chain stopping block production for four hours is a liveness failure, not a trading failure, and the two get conflated when exchanges separate 'markets open' from 'transfers frozen.' That split lets venues keep order books running during an outage, which protects their volumes but can mask how fragile the underlying settlement layer is. For a chain marketed as interchain infrastructure for Cosmos, a validator-level halt is a reminder that IBC transfers are only as reliable as the weakest chain in the route. (per thedefiant.io)
Market reaction i
Osmosis rose 7.5% in the 4 hours after the first headline.
12 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | Rujira AMM Strategies · Swap Logic Flaw incident | $200k |
| 3 days ago | Initia · Private key leak incident | $615k |
| 4 days ago | Arcus · Accounting bug incident | $2.2M |
| 4 days ago | Ankr Bridge · Cross-Chain Message Spoofing incident | $304.5k |
| 5 days ago | LNbits · Unknown incident | no figure in dollars |
4302 incidents stored