A total of 22.65 BTC now sits frozen on Osmosis. Yet even in the best case, where governance claws back every last satoshi, the community pool would still be on the hook for roughly 17.19 BTC to restore the asset in full.
That remaining gap is what matters here. A defect in Nomic’s bespoke forwarding system opened the door to a double-spend, and the nBTC that came out of it landed in the basket backing allBTC as though it were genuine.
The numbers don’t reconcile
allBTC is minted against a basket of Bitcoin variants custodied on Osmosis, with nBTC from the Nomic bridge counted among them. As of the reporting cutoff, the official allBTC dashboard listed 110.57 allBTC in circulation set against 39.84 nBTC sitting in that basket.
According to Osmosis, that nBTC traced back to false vouchers. Do the division and the result matches the figure Osmosis itself published: 36.03% of allBTC’s backing is now in doubt, which leaves roughly 70.73 BTC-equivalent of legitimate collateral supporting the token.
In other words, claims against the basket now outstrip the valid BTC-equivalent assets actually inside it. Every allBTC holder shares exposure to that shortfall until sufficient valid backing is put back.
The chain wasn’t the problem
The disclosure deserves some credit for precision about the blast radius. Osmosis stated that neither its own chain nor the Inter-Blockchain Communication protocol had been compromised, and pinned the flaw on Nomic’s forwarding logic.
SlowMist’s incident database characterizes the episode identically, logging it as a Nomic bridge double-spend.
For anyone holding other assets on Osmosis, that boundary is the important part. There was no consensus failure and no hole in IBC. What happened was a single bridge’s custom code issuing vouchers it had no business issuing.
Two months of silence
The timeline is where things get awkward. More than two months elapsed between the apparent exploit activity and the public disclosure.
On-chain researcher Rarma dated the principal minting to June 25 and reported that 22.65060846 allBTC generated during activity on July 17 had not moved as of the trace’s publication. The figure should ring a bell: it is precisely the balance Osmosis went on to freeze.
Frozen isn’t recovered
Inflows and outflows for both Nomic and allBTC have been halted, while allBTC minting and redemption sit paused. Those measures seal off the affected functions at both ends for as long as the backing gap goes unaddressed.
Freezing the BTC, however, is not the same as seizing it or returning it to the basket. Osmosis has said it intends to put a proposal to governance to confiscate the 22.65 BTC and draw on Bitcoin built up in the community pool to make up the difference.
Measured against the 39.84 BTC impairment, recovering the frozen amount in full would still leave roughly 17.19 BTC to be replaced. And as of Sept. 9, none of the 20 most recent on-chain proposals contained a corresponding seizure or recapitalization measure.
Who actually holds the levers
The allBTC contract is administered by Osmosis governance. A 3-of-6 moderator subDAO holds the power to pause the pool or flag a constituent asset as corrupted — and that is exactly the mechanism currently in use.
Over at Nomic, the custody documentation states that reserve disbursals need signatures amounting to more than 90% of the voting power in its signatory set. The threshold is deliberately steep, and it’s worth keeping in mind before assuming the frozen coins are going anywhere in a hurry.
None of the above amounts to a realized haircut for any single holder. Whether redemption happens at full parity comes down to how governance votes and how much Bitcoin the community pool ultimately commits.
Bitcoin is down 1.63% over the past 24 hours, a rounding error compared with the question allBTC holders are currently sitting on. For anyone holding the token, the proposal feed — not the price chart — is what to keep an eye on. Until a recapitalization measure surfaces there, that 17.19 BTC gap remains nothing more than a number on a dashboard.