a223e1c1-d
Threshold reopens tBTC redemptions after 11-day freeze
Threshold reported that its tBTC app reopened around 03:00 UTC on Nov. 10 after an 11-day freeze caused by deposit-accounting and signer-security issues, not insufficient Bitcoin reserves.

Outputs
Threshold said its tBTC app reopened around 03:00 UTC on Nov. 10 after an 11-day redemption freeze.
On Oct. 31, bridge wallets held 4,320.46 BTC against 4,185.155 tBTC in circulation.
The reported reserve position left about 135 BTC more Bitcoin than the outstanding tBTC supply.
The protocol Council restored permission to submit Bitcoin proofs on Nov. 7, before the app reopened.
A review of 57 wallet addresses matched 31 BTC redemption payouts to bridge proofs and found no unexplained outflows in the wallets examined.
Nathan Brooks
Threshold reported that its tBTC app reopened around 03:00 UTC on Nov. 10, ending an 11-day freeze that prevented holders from accessing the Bitcoin backing their tBTC through the bridge.
Threshold said the disruption did not stem from insufficient Bitcoin reserves. As of Oct. 31, the protocol reported 4,320.46 BTC in its bridge wallets against 4,185.155 tBTC in circulation. The difference left approximately 135 BTC more Bitcoin than the outstanding token supply.
The reserve position separated the protocol’s solvency from its ability to process redemptions in real time. That distinction became central because the stoppage arose from control failures inside the bridge rather than a shortfall in collateral.
Two failures stopped the bridge
Threshold identified separate technical and security issues. One involved a problem in how the bridge accounted for Bitcoin deposits before the suspension. A second security issue forced some node operators responsible for signing Bitcoin transactions to take their systems offline while they applied patches.
Under Threshold’s design, a bridge wallet requires signatures from more than half its designated signers to authorize a Bitcoin transaction. Threshold said withdrawals could not proceed until enough operators returned online for the wallet to clear that threshold.
Threshold also needed to restore Bitcoin transaction proof submissions. The protocol uses those proofs to verify deposits and redemption payouts, making their restoration another operational requirement rather than an administrative step.
The restoration sequence
Threshold said it fixed the deposit-accounting issue and upgraded the bridge before the protocol’s Council restored permission to submit Bitcoin proofs on Nov. 7. The app then reopened around 03:00 UTC on Nov. 10, allowing holders to initiate redemptions again.
The order shows what the reopening represented. Restoring the app without correcting deposit records, resuming proof submission and securing enough signer participation would not have restored the full redemption path.
Wallet and contract review
Between Oct. 25 and Nov. 12, Threshold reviewed 57 registered tBTC wallet addresses and the bridge contracts for activity. The team matched 31 BTC redemption payouts to their corresponding bridge proofs.
Threshold reported no unexplained Bitcoin outflows in the wallets examined. Its findings indicated that the interruption was an operational failure rather than depletion of Bitcoin reserves.
What does this change for tBTC holders?
For holders, the episode shows that sufficient reserves do not guarantee timely access to the underlying asset. On Oct. 31, Threshold held more Bitcoin than the amount of tBTC in circulation, yet the accounting problem, unavailable signers and interrupted proof submission kept redemptions from clearing. Reserve adequacy and redemption liveness were separate conditions.
That distinction matters for Bitcoin-backed assets used in DeFi, where users can treat reserve reports as evidence that a token is redeemable on demand. Threshold’s case shows that bridge accounting, transaction proofs and threshold signing stand between reported reserves and actual access to Bitcoin. A failure at any of those layers can suspend withdrawals without creating a reserve shortfall.
The Nov. 7 proof restoration and Nov. 10 reopening were therefore operational milestones, not merely software-maintenance events. They reopened a settlement path that Threshold’s own controls had closed while the team repaired its accounting fault and patched affected systems.
Going forward, the relevant test for BTC-backed DeFi assets is not only whether reserves cover token liabilities, but whether their bridges can maintain redemption, proof and signing systems together through routine security maintenance.
For the broader market, bridge resilience will form part of the redemption product: reported Bitcoin backing becomes economically useful only when accounting, proof and signing systems operate together.
via cryptonews.net (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,651 articles