# Liquid Enables BTC-LBTC Swaps as Direct Peg-Outs Stay Suspended

Published 2026-10-20 · Crypto.world Team · Crypto.world

> Liquid is enabling semi-automated BTC-LBTC swaps with participating providers as the network enters the final stages of recovery, the Liquid Federation says. Direct Federation peg-outs remain restricted while Liquid works to restore full 1:1 bitcoin backing.

The [Liquid Federation](https://blog.liquid.net/liquid-network-staged-recovery-update/) said on October 20 that it is enabling semi-automated swaps between bitcoin and Liquid bitcoin (LBTC), giving users a route between the assets through participating providers while direct Federation redemptions remain restricted. The announcement marks a step in recovery from the September 6 incident, when a vulnerability in Elements, the software behind Liquid, let an attacker create roughly 4,000 unbacked LBTC and withdraw bitcoin from the Federation reserve.

## Swaps return before direct redemptions

The service is being enabled in coordination with participating swap providers. The Federation describes the swaps as “semi-automated” and says there are no protocol-imposed volume limits on the service. That statement concerns limits imposed by Liquid’s protocol; it does not establish that every provider will accept every order size.

“For most users accessing Liquid through supported swap providers, this will restore a practical means of converting LBTC to BTC, even while direct Federation peg-outs remain restricted,” the Federation said in its [recovery update](https://blog.liquid.net/liquid-network-staged-recovery-update/). The distinction matters: a provider-mediated swap is not the same as a direct Federation peg-out, the process that releases reserve bitcoin against burned LBTC. The update does not name participating providers or set out a firm start time for each service.

## Reserve software updated, safeguards remain

Updated software for managing its bitcoin reserves has been deployed to a sufficient number of functionaries, the Federation says. The software accommodates Liquid’s post-incident accounting state and supports continued management of Federation funds. Multiple safeguards remain in place to block premature or unauthorized peg-outs while the remaining restoration work continues.

Direct Federation redemptions are still part of a later recovery phase. The Federation first needs to reestablish full 1:1 bitcoin backing for LBTC, then reactivate peg-outs for authorized holders of Peg-out Authorization Keys, or PAKs. It also plans to make reserve information transparently monitorable through block explorers, subject to outstanding security and operational requirements.

## The September exploit left about 602 BTC outstanding

[Blockstream](https://crypto.world/companies/blockstream)’s [incident assessment](https://blog.liquid.net/liquid-network-security-incident-assessment/) says the September 6 exploit used a flaw in Elements’ rangeproof verification cache. The attacker’s transaction passed validation despite creating value not backed by its inputs, and the resulting LBTC was used in a peg-out through SideSwap. Blockstream’s report says approximately 3,996 BTC left the Federation in the main withdrawal.

The attacker returned 3,400 BTC the next day, according to the assessment, leaving approximately 602 BTC outstanding. Blockstream says the network’s recovery included a software fix and a reorganization that removed invalid transactions and their descendants from the canonical chain. The October 20 update does not say the missing bitcoin has been recovered or give a date for restoring direct peg-outs.

## Swaps do not complete the peg recovery

The new route expands the ways users may exchange LBTC for BTC, but it does not amount to a declaration that the reserve is fully backed or that direct withdrawals are safe to resume. The Federation’s final restoration phase depends on full 1:1 backing, followed by controlled reactivation of peg-outs and completion of remaining checks. For now, direct Federation peg-outs remain restricted, and approximately 602 BTC from the September incident remains outstanding.

## Sources

1. Original source · Blog post [Liquid Federation](https://blog.liquid.net/liquid-network-staged-recovery-update/) blog.liquid.net

Other pages read

2. [Blockstream](https://blog.liquid.net/liquid-network-security-incident-assessment/) blog.liquid.net

## Related stories

- [Next Technology Authorizes Sale or Pledge of 5,833 BTC](https://crypto.world/news/next-technology-authorizes-sale-pledge-5833-btc)
- [Researchers Model How Capital Costs Delay Bitcoin Mining Gaps](https://crypto.world/news/researchers-model-capital-costs-bitcoin-mining-gaps)
- [Aave Labs Backs Babylon’s Native Bitcoin Collateral Plan](https://crypto.world/news/aave-backs-babylon-native-bitcoin-collateral-plan)
- [Bitcoin Core Releases 31.2 With a 10,000-Entry Queue Limit](https://crypto.world/news/bitcoin-core-31-2-release-private-broadcast-queue-limit)
- [German Sparkassen Start Phased Crypto Trading Rollout](https://crypto.world/news/german-sparkassen-phased-crypto-trading-rollout)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/liquid-enables-btc-lbtc-swaps-peg-outs-suspended
