Osmosis has frozen 22.65 BTC. Even if governance recovers every satoshi of it, the community pool still owes roughly 17.19 BTC to make the asset whole again.
That gap is the story. A flaw in Nomic’s custom forwarding system allowed a double-spend, and the nBTC it produced went into the basket that backs allBTC as if it were real.
The numbers don’t reconcile
allBTC is issued against a basket of Bitcoin variants held on Osmosis, and nBTC from the Nomic bridge is one of them. When I checked the official allBTC dashboard at the reporting cutoff, it showed 110.57 allBTC in circulation against 39.84 nBTC in the basket.
Osmosis said that nBTC was created from false vouchers. Run the division and you get the figure Osmosis published: 36.03% of allBTC’s backing is in question, leaving about 70.73 BTC-equivalent of other backing behind the token.
So the claims on the basket exceed the valid BTC-equivalent assets sitting in it. Until enough valid backing is restored, allBTC holders are collectively exposed to that shortfall.
The chain wasn’t the problem
Credit where it’s due on the disclosure: Osmosis was specific about the blast radius. Neither its chain nor the Inter-Blockchain Communication protocol was compromised, it said, and the bug was in Nomic’s forwarding logic.
SlowMist’s incident database describes the event the same way, as a Nomic bridge double-spend.
That distinction matters if you hold anything else on Osmosis. This isn’t a consensus failure or an IBC hole. It’s one bridge’s custom code minting vouchers it shouldn’t have.
Two months of silence
The uncomfortable part is the timeline. The public disclosure came more than two months after the apparent exploit activity.
On-chain researcher Rarma traced the principal minting to June 25 and said 22.65060846 allBTC created during July 17 activity remained unmoved when the trace was published. That number should look familiar. It’s the balance Osmosis froze.
Frozen isn’t recovered
Nomic and allBTC inflows and outflows have been frozen, and allBTC minting and redemption are paused. Those restrictions block entry and exit through the affected functions while the backing gap sits unresolved.
But the frozen BTC hasn’t been seized or returned to the basket. Osmosis said it plans to ask governance to confiscate the 22.65 BTC and use Bitcoin accumulated in the community pool to cover the remainder.
Full recovery of the frozen amount still leaves about 17.19 BTC to replace against the 39.84 BTC impairment. And as of Sept. 9, no matching seizure or recapitalization measure appeared among the latest 20 on-chain proposals.
Who actually holds the levers
Osmosis governance administers the allBTC contract. A 3-of-6 moderator subDAO can pause the pool or mark a constituent asset as corrupted, which is the mechanism doing the work right now.
On the Nomic side, the custody documentation says reserve disbursals require signatures representing more than 90% of its signatory set’s voting power. That’s a high bar by design, and it’s worth understanding before anyone assumes the frozen coins move quickly.
None of this establishes a realized haircut for any individual holder. Redemption at full parity now depends on how governance votes and how much Bitcoin the community pool actually puts in.
Bitcoin is down 1.63% over the past 24 hours, which is noise next to the question allBTC holders are sitting with. If you’re holding it, the proposal feed is the thing to watch, not the price chart. The recapitalization measure has to show up there before the 17.19 BTC gap becomes anything other than a number on a dashboard.
