The resumption of the bridge was announced on Sunday, when Threshold confirmed that the underlying network architecture was coming back online. This phased restart is occurring as security-patched node operators steadily reconnect to the decentralized network. These independent operators play a critical role in the protocol’s trust-minimized design, collectively authorizing Bitcoin movements and processing user deposits and redemptions between the Bitcoin blockchain and decentralized finance networks.
According to project communications, pending requests that were submitted prior to the emergency shutdown are expected to be processed sequentially as more independent operators bring their nodes back online. However, the decentralized application’s interface will not immediately accept new deposits, token minting, or redemption requests. Normal operations will only fully resume once a sufficient threshold of nodes is safely back online, though the project team has not yet announced a definitive date for the complete restoration of all application features.
The security crisis began on October 30, when Threshold abruptly halted the tBTC bridge. The emergency measure was taken so that operators could patch a critical Linux kernel vulnerability that had recently come to light. Cybersecurity experts warned that the flaw possessed the potential to allow remote attackers to execute arbitrary code on unpatched servers, posing a severe threat to server infrastructure across the internet. In the wake of the shutdown, Threshold conducted extensive internal reviews and audits, subsequently reporting that it had found no forensic evidence or indications that the critical vulnerability was successfully exploited against any active tBTC nodes or infrastructure.
The ripple effects of the bridge’s sudden offline status quickly spread to the wider decentralized finance ecosystem, particularly affecting lending protocols integrated with the asset. On October 31, the Aave community and risk managers moved swiftly to protect protocol solvency by freezing its tBTC reserve on Ethereum Core. This protective restriction was designed to prevent any additional protocol exposure while direct redemptions through the bridge were temporarily unavailable. The active restrictions effectively halted any new tBTC deposits and stripped the token of its borrowing power within the market, though existing users retained the ability to withdraw their funds and repay existing loans.
Data provided by Threshold indicates that the underlying collateral backing the system remained secure throughout the ordeal. Roughly 4,320 Bitcoin remains securely locked within the bridge wallets, backing approximately 4,185 tBTC currently in circulation across various decentralized finance applications. Project monitors confirmed that no unauthorized Bitcoin transfers or unauthorized token minting events were detected during the entire duration of the security pause. Meanwhile, Aave risk provider LlamaRisk has indicated that it will formally propose restoring the tBTC reserve once Threshold’s network operations and bridge mechanics fully return to normal parameters.
