tBTC Bridge Resumes, but Aave's $120M Reserve Stays Frozen10 min read2,087 words

tBTC Bridge Resumes, but Aave's $120M Reserve Stays Frozen

The tBTC bridge is restarting after a security pause, but Aave's $120M reserve remains restricted. See what resumed, what did not, and what users should watch.

tBTC bridgeAave tBTC reserveThreshold NetworkBitcoin DeFicrypto bridge security
tBTC Bridge Resumes, but Aave's $120M Reserve Stays Frozen

The tBTC Bridge Is Restarting. Why Is Aave Still Frozen?

The tBTC bridge has started restarting after a nine-day security pause, but not everything is back to normal. Threshold Network says patched node operators are reconnecting and that the underlying network is restarting. Even so, the app is still not accepting new deposits, minting, or redemptions until enough operators are online. Requests submitted before the shutdown are expected to be processed as operators come back.

Aave, meanwhile, took a separate and more cautious step. Its tBTC reserve on Ethereum Core remains frozen to new deposits and to adding borrowing power. Existing users can still withdraw and repay loans, though. The reserve holds about $120 million in tBTC, which is why the difference between a bridge restart and a lending-market reopening matters to users and integrators.

In other words: the bridge is moving again, but you shouldn't treat every user-facing action as "restored" yet.

What has resumed - and what remains paused

It's easy to read "the network is restarting" and assume "the bridge is open again." Threshold itself is pointing to why that's not the same thing.

Threshold says patched node operators are reconnecting. Those operators collectively authorize Bitcoin movements and handle tBTC deposits and redemptions. Their return is an important step - but it doesn't automatically mean every part of the bridge service is available to users right away.

The project also says requests submitted before the shutdown are expected to be processed as more operators come back online. But until enough nodes are running, the app won't accept new deposits, minting, or redemptions. So if you're deciding whether to submit a transaction, the network restarting is not enough by itself - you still need to check the service status.

A bridge isn't a single on/off switch. It's a set of moving parts - software, operator availability, and authorization processes - that need to line up. You can see partial recovery where some functions return while user-facing actions stay blocked. In this case, the restart is progress, but the limits on deposits, minting, and redemptions are still explicitly in place.

For users, the practical status is:

  • Previously submitted requests: Threshold expects them to be processed as more operators reconnect.
  • New deposits and minting: Not available through the app until enough nodes are online.
  • Redemptions: Also remain unavailable through the app during the staged restart.
  • Full restoration: No restart date has been announced.

After a security incident, pausing parts of the workflow while operators reconnect is a fairly common "wait until it's safe" approach. The downside is that some users and integrations may have to sit tight longer than they'd like - especially if their plans depend on deposits or redemptions.

So the better question isn't "is tBTC back?" It's: which specific actions work right now, which ones are still blocked, and what the project has actually said about each status. That's a more reliable read than treating an announcement like a full reopening.

Why the Linux vulnerability triggered a bridge shutdown

Threshold halted the bridge on Oct. 30 while operators addressed a critical Linux kernel vulnerability. The concern was that remote attackers could run code on servers that hadn't been patched. Threshold says it found no evidence the flaw had been exploited against tBTC nodes.

Even if a bridge's smart contracts aren't the problem, a vulnerability in infrastructure used by node operators can still become a bridge-level concern. Operators run the systems involved in processing and authorizing Bitcoin movements. If a server involved in that pipeline is exposed, the risk isn't limited to whether specific transactions were already compromised. Operators - and the project - also have to consider whether an attacker could compromise the systems needed to keep the bridge operating safely.

Pausing activity while operators patch is a risk-control measure: it limits activity while the supporting infrastructure's security posture gets addressed. The immediate cost is disruption. Users can't rely on ordinary deposit and redemption flows, and connected applications may need to restrict related actions. In a cross-chain setup that connects Bitcoin to DeFi, that kind of careful pause can be less damaging than continuing to process activity with critical infrastructure unresolved.

There's also a difference worth keeping in mind: "no evidence of exploitation" isn't the same as "no risk existed." Threshold's statement is reassuring about what it had detected - but the shutdown still reflects the possibility that an unpatched server could have created unacceptable risk even if no attack has been confirmed.

Operationally, the restart depends on dependencies beyond a calendar date. Node operators have to apply patches, reconnect, and provide enough participation for the bridge to support the functions users care about. So the right time to treat the system as restored is when those components are clearly in place - not just when the pause has been running long enough.

For teams building on tBTC, the incident is a reminder to separate protocol assumptions from infrastructure assumptions. A token can exist on Ethereum even while the bridge paths needed to move between Bitcoin and tBTC are constrained. Applications should plan for that state, including clear user messaging and limits that don't assume bridge liquidity and redemption access will always be there.

Why Aave kept its $120 million tBTC reserve frozen

Aave froze its tBTC reserve on Ethereum Core on Oct. 31 after the bridge pause made redemptions unavailable. The stated goal was to prevent additional exposure while users couldn't redeem tBTC through the bridge. The restriction blocks new tBTC deposits and prevents the token from adding borrowing power. Existing users can still withdraw and repay loans.

This is targeted risk management, not the same as wiping out access to existing positions. By blocking new deposits, Aave limits how much additional tBTC can enter the reserve during the interruption. By stopping tBTC from adding borrowing power, it avoids expanding borrowing capacity based on tBTC collateral while the redemption route is constrained. Letting withdrawals and repayments continue preserves some day-to-day position management for existing users.

That distinction matters for borrowers and suppliers. A frozen reserve doesn't mean every user action is blocked. But it does change what you can do with tBTC in the market, including strategies that depend on supplying the token or using it to increase borrowing capacity. If you have a position, you still need to separate what Aave currently allows from what Threshold has paused on the bridge side.

The reserve size - about $120 million in tBTC - also helps explain why risk providers wouldn't automatically treat a partial bridge restart as a green light to reopen the lending market. Lending-market settings and bridge operations are different systems. The bridge can start reconnecting operators while Aave waits for confidence that its asset assumptions and exit paths are back to normal.

Aave risk provider LlamaRisk said it would propose restoring the reserve after Threshold's operations return to normal. That's a condition to watch, not a published reopening date. So the sequence isn't simply "bridge restarts, reserve opens." Threshold's operational recovery and Aave's internal decision-making both matter, and the latter may lag while the risk provider assesses what's actually live.

For users, the practical takeaway is to avoid assuming that holding tBTC in an Aave market automatically means every normal supply and borrowing action is available. Check Aave's reserve restrictions and the bridge's redemption status separately. If you're making decisions, confirm which actions you can do today - especially if you're counting on immediate conversion or new borrowing capacity.

What users and DeFi teams should watch next

The next milestone isn't just someone announcing that the bridge restarted. It's proof that enough patched operators are back online for Threshold to restore the user-facing functions that are still paused. Threshold hasn't given a date, so you should treat recovery as conditional rather than scheduled.

If you want to track this without guessing, split it into three checks:

  1. Bridge operations: Do you have enough node operators online, and has Threshold explicitly reopened new deposits, minting, and redemptions?
  2. Existing requests: Are requests submitted before the shutdown being processed as expected? Threshold says they should be handled as operators return.
  3. Aave market status: Has LlamaRisk proposed restoring the reserve, and has the relevant Aave restriction actually changed?

These are separate because one update doesn't automatically mean the others are done. The bridge could restore its functions before Aave reopens supply and borrowing. And changes in lending-market parameters shouldn't be treated as proof that every bridge operation is working - unless Threshold has confirmed that independently.

Threshold reported about 4,320 BTC in bridge wallets against approximately 4,185 tBTC in circulation. On its face, that suggests the Bitcoin held in bridge wallets was higher than the reported tBTC supply at the time (roughly a 103% ratio). Still, that math isn't a complete audit and it doesn't guarantee that every asset is immediately available for redemption. It doesn't replace confirmation of operational status, operator participation, or the project's own accounting and security checks.

Threshold also said it detected no unauthorized Bitcoin transfers or tBTC minting. That matters, but it should be read alongside the recovery status. The lack of detected unauthorized activity doesn't, by itself, reopen paused functionality - or remove the reason Aave restricted its reserve.

For applications and treasury teams, the right move is to make state clear. If your integration depends on tBTC deposits, redemptions, or Aave borrowing capacity, don't blur "paused vs. available" in your product messaging. Don't present a partial restart as full liquidity. In practice, build around what's actually usable right now, not whatever status label looks most reassuring.

Key takeaways

  • The tBTC network is restarting as patched operators reconnect, but new deposits, minting, and redemptions are still paused until enough nodes are online.
  • Threshold reported no evidence of exploitation, unauthorized Bitcoin transfers, or unauthorized tBTC minting.
  • Aave's tBTC reserve remains restricted to new deposits and to borrowing-power increases; existing users can still withdraw and repay.
  • No full restart or Aave reopening date has been announced. Treat both as separate operational milestones.

Conclusion

The tBTC bridge's restart is a real step forward, but it isn't a full return to service. Threshold is reconnecting patched operators while keeping deposits, minting, and redemptions paused until enough nodes are online. Aave is still restricting new deposits and borrowing-power increases against its tBTC reserve.

For users and DeFi teams, the safest approach is to track bridge functionality and Aave market status independently. Wait for clear confirmation that the exact action you need is available, and don't treat a partial restart as restored liquidity. In a cross-chain system, what you can do depends on the operational details - not a single status label.

Frequently Asked Questions

No. Threshold said the underlying network is restarting as patched operators reconnect, but its app is not accepting new deposits, minting or redemptions until enough nodes are online. The project did not announce a date for full resumption, so the restart should be treated as partial.
Threshold halted the bridge on Oct. 30 while operators addressed a critical Linux kernel vulnerability that could allow remote code execution on unpatched servers. The project said it found no evidence that the vulnerability had been exploited against tBTC nodes.
The restriction prevents new tBTC deposits and stops tBTC from adding borrowing power in Aave’s Ethereum Core market. Existing users can still withdraw and repay loans. Aave introduced the freeze while bridge redemptions were unavailable, limiting additional exposure during the interruption.
No reopening date has been announced. LlamaRisk said it would propose restoring the reserve after Threshold’s operations return to normal. A proposal and a completed change are distinct steps, so users should check the reserve’s status rather than assume it will reopen as soon as operators reconnect.

Related articles