Threshold Network paused tBTC minting and redemption as a precaution after identifying a Linux kernel vulnerability, without disclosing any confirmed exploit tied specifically to tBTC Because
When Threshold Network paused minting and redemption of tBTC, its bridged bitcoin token, after discovering a Linux kernel vulnerability affecting its infrastructure, the protocol had not disclosed any confirmed theft or exploit of tBTC itself. The pause was explicitly precautionary, a decision to halt new activity while the team investigated and hardened the system against a theoretical risk rather than responding to an attack already underway.
Despite the absence of a confirmed incident, the pause still triggered real consequences elsewhere in DeFi. Both Aave and Compound accept tBTC as collateral within their own lending markets, meaning both protocols had exposure to a token whose underlying minting and redemption mechanism had just been frozen by its issuer. In response, Compound moved toward an on-chain vote cutting tBTC’s supply caps and borrow collateral factors to zero across seven of its markets, effectively preventing any new borrowing or supplying of the token even though Compound itself had not been attacked.
This pattern reflects a structural feature of decentralized finance: lending protocols do not operate in isolation from the tokens they accept as collateral. When a bridge or wrapping protocol like Threshold Network pauses its core minting and redemption functions, the token it issues effectively becomes harder to create or redeem for the underlying asset, which can affect its price stability and liquidity even without any theft occurring. Lending protocols that treat the wrapped token as reliable collateral face a choice: tighten their own risk parameters defensively, or risk being caught holding devalued collateral if the underlying concern turns out to be more serious than initially understood.
The decision to zero out a parameter rather than simply reduce it reflects a conservative approach favored when the underlying risk is still being investigated and not yet fully understood, erring toward removing exposure entirely rather than guessing at an appropriate partial reduction.
Multi-protocol ripple effects like this one have become increasingly common as DeFi’s various lending markets, staking derivatives, and bridged assets have grown more interconnected, meaning a single precautionary action at one protocol can cascade into defensive responses across several others that share exposure to the same underlying token. The underlying Compound proposal is posted on the protocol’s own governance forum.
This post first appeared in Why One Bridge’s Precautionary Pause Can Still Freeze Markets on Two Other DeFi Protocols
