Threshold restores tBTC redemptions after 11-day freeze despite full Bitcoin reserves
Threshold froze tBTC redemptions for 11 days even though its reserves covered every token
The Threshold Network stopped users from redeeming its Bitcoin-backed token tBTC for 11 days. The freeze ran from Oct. 30 until Nov. 10, when the service reopened around 03:00 UTC, according to a post-mortem the protocol published on Nov. 18.
tBTC is a token that represents Bitcoin and is used in decentralized finance (DeFi), a set of financial applications built on blockchains. During the pause, holders could not convert tBTC back into native Bitcoin through Threshold's app, though they could still transfer and trade the tokens.
The freeze did not happen because reserves were short. Threshold reported that its bridge wallets held 4,320.46 BTC against 4,185.155 tBTC in circulation on Oct. 31, leaving roughly 135 BTC more than the outstanding token supply.
Key points
- Threshold's app stopped accepting tBTC deposits and redemption requests on Oct. 30 and reopened around 03:00 UTC on Nov. 10.
- The bridge held 4,320.46 BTC against 4,185.155 tBTC in circulation on Oct. 31, about 135 BTC more than the token supply.
- Two separate problems were involved: a deposit-accounting issue and a security issue that pushed some signing nodes offline for patches.
- Threshold's Council reauthorized Bitcoin proof submissions on Nov. 7, and the app reopened on Nov. 10.
- A review of 57 wallet addresses found no unexplained Bitcoin outflows between Oct. 25 and Nov. 12.
What the Nov. 18 post-mortem says went wrong
Threshold said its team had already identified a problem with how the bridge accounted for Bitcoin deposits before the suspension. At the same time, a separate security issue forced some node operators, the parties responsible for signing Bitcoin transactions, to take their systems offline for patches.
Under the bridge's design, a wallet needs signatures from more than half of its designated signers to authorize a Bitcoin transaction. Withdrawals could not move until enough operators returned online. The protocol also had to restore Bitcoin proof submissions, the process that lets the bridge verify deposits and redemption payouts.
Threshold said it fixed the deposit-accounting problem and upgraded the bridge before its Council reauthorized proof submissions on Nov. 7. The app reopened to new redemption requests on Nov. 10.
What the review of wallets found
The team reviewed 57 registered tBTC wallet addresses and the bridge contracts for activity between Oct. 25 and Nov. 12. It matched 31 Bitcoin redemption payouts to their corresponding bridge proofs and reported finding no unexplained Bitcoin outflows in the wallets examined.
These findings point to an operational failure rather than a loss of reserves, according to the protocol's account.
Why a fully backed token can still be hard to access
The incident shows that holding enough reserves does not guarantee users can always reach their Bitcoin. Even when the bridge held more Bitcoin than tokens in circulation, technical and security failures temporarily blocked redemptions.
The disruption also touched lending activity. The lending platform Aave restricted activity in its tBTC market during the pause. CryptoSlate notes the incident exposes a broader vulnerability for Bitcoin-backed assets used in DeFi: technical failures can prevent holders from accessing the underlying Bitcoin even when backing is sufficient.
What remains uncertain
Threshold's written account describes the signer requirement but does not separately state when enough signing operators returned online to restore signing. The published timeline is accurate only to calendar-day precision.