However, the disruption did not appear to stem from insufficient Bitcoin reserves.
Threshold reported that its bridge wallets held 4,320.46 $BTC against 4,185.155 tBTC in circulation on Oct. 31, leaving approximately 135 $BTC more than the outstanding token supply.
What caused the tBTC redemption freeze?
Threshold attributed the interruption to separate technical and security issues that affected its ability to process Bitcoin transactions.
The team had identified a problem with how the bridge accounted for Bitcoin deposits before the suspension. Meanwhile, another security issue forced some node operators responsible for signing Bitcoin transactions to take their systems offline for patches.
Under Threshold's design, a bridge wallet requires signatures from more than half its designated signers to authorize a Bitcoin transaction. This meant withdrawals could not proceed until enough operators returned online.
The protocol also needed to restore Bitcoin transaction proof submissions, which allow the bridge to verify deposits and redemption payouts.
Threshold said it fixed the deposit-accounting issue and upgraded the bridge before its Council restored permission to submit Bitcoin proofs on Nov. 7.
The app subsequently reopened around 03:00 UTC on Nov. 10, allowing holders to initiate redemptions again.
The team also reviewed 57 registered tBTC wallet addresses and the bridge contracts for activity between Oct. 25 and Nov. 12.
It matched 31 $BTC redemption payouts to their corresponding bridge proofs and reported finding no unexplained Bitcoin outflows in the wallets examined.
Essentially, the findings indicate the interruption was an operational failure rather than a depletion of $BTC reserves.
However, the incident exposed a broader vulnerability for Bitcoin-backed assets used in DeFi: even when reserves are sufficient, technical failures can temporarily prevent holders from accessing their underlying $BTC.