Threshold Review Examines 57 Addresses and 140 Checkpoints, Finds tBTC Balances Explained
Key Facts
In its post-incident report published on November 18, 2026, Threshold said its review found no unexplained outgoing bitcoin flows or unsupported new tBTC tokens after it precautionarily paused the bridge following unexpected wallet activity and a confidential report of a flaw. It said the on-chain data review covered October 25 to November 12 and included the bridge contracts and 57 registered tBTC wallet addresses. In a review conducted on November 16, the company found no unexplained balance within the scope of the examination. It said the finding meant the review found no evidence of an unexplained increase in the bridge’s liabilities or bitcoin leaving without a corresponding proof. The service had been in maintenance mode from October 30 to November 10 while the company addressed the flaw, which could have created a record for a fictitious deposit.
The events began at around 20:16 UTC on October 30, when an unknown address started a wallet-generation round, according to Threshold. The company said it was already dealing with a bridge flaw reported confidentially through its bug bounty program, and had therefore paused the service as a precaution. The following day, a 0.01 BTC deposit designed to exploit the flaw was disclosed to the bridge, along with fabricated additional data. Threshold said the deposit was not processed while bridge proofs were paused, then was settled after the fix at its actual value minus the usual fees. It said a security researcher at OtterSec sent the first report of the vulnerability through the Immunefi platform.
The flaw was in the deposit transaction parser, which accepted incomplete or malformed input and output lists, potentially allowing a record to be created for a deposit that had not actually taken place. The issue was therefore not limited to matching reserves against tokens in circulation; the risk was that a token liability could be recorded without a valid bitcoin deposit. Threshold said a comparison across 140 checkpoints showed that the difference between bitcoin at registered addresses and the bridge ledger’s liabilities remained unchanged, after accounting for the delay between bitcoin transactions and their proofs on Ethereum. It added that it found no tBTC minted without a deposit. In a snapshot dated October 31, tBTC wallets held 4,320.46 BTC, against 4,185.155 tBTC in circulation, figures the company presented in its explanation of reserves and liabilities on that date.
Regarding fund flows, Threshold said all 76 bitcoin transactions leaving tBTC wallets during the period reviewed matched bridge proofs. The activity included 45 deposits and 31 redemption payouts, according to the report. The company said it had thus linked each outgoing transaction it reviewed to a corresponding proof, alongside comparing reserves with the liabilities ledger across the checkpoints. These findings indicated that its review found no unexplained outflow in the data and addresses it examined. They apply to the defined audit scope and period, while the service pause had halted the processing of new transactions pending resolution of the flaw.
The fix covered two bridge libraries, and Threshold said it did not change the storage layout, ABI interface or events. After the change, deposit detection required about 4,500 to 33,000 additional gas units, depending on the size of the funding transaction, and the company warned relayers using fixed gas limits to recalculate them. Threshold resumed authorization to submit bitcoin proofs on November 7, then reopened the application at around 03:00 UTC on November 10. It said the bridge is now fully operational, following the maintenance period that ran from October 30 to November 10. The service’s resumption thus combined the flaw fix with the restart of proof submission, while raising the gas cost needed to detect deposits.
The tBTC reserve on Aave’s Ethereum Core network remained frozen after Threshold said Aave imposed the freeze on October 31. The network said each partner decides independently whether to lift restrictions, meaning that reopening the bridge application does not automatically lift restrictions imposed by other platforms. The report also addressed the possibility of a Linux kernel vulnerability being exploited, but said Threshold had not confirmed its exploitation against any tBTC node. It added that node operators stopped their nodes and began patching them as of October 31. In a separate development track, the company identified a transition to FROST Schnorr signing as a priority for the fourth quarter of 2026, while keeping the signer quorum at 51 of 100; it said the change is expected to make failed signing rounds easier to track and speed up minting and redemption.