For builders working with Liquid, the key distinction in the Federation’s November 3, 2026 update is between reserve backing and withdrawal access. The Federation said its bitcoin reserves had been restored to 1:1 backing for all LBTC following a September 6 exploit. It did not say whether all restrictions on direct Federation peg-outs—withdrawals of bitcoin from Liquid—had been lifted.
About 4,000 BTC, valued in the original report at approximately $320 million, was withdrawn from the Federation wallet in the exploit. Liquid’s incident report traced the issue to a bug involving cached range-proof verifications in Elements, the software underlying Liquid. According to that report, the attacker created approximately 4,000 unbacked LBTC and used them to withdraw bitcoin through SideSwap, a Liquid wallet and trading platform with a peg-out authorization key. Liquid said network operators were not hacked and no keys were compromised.
The attacker returned roughly 3,400 BTC the next day, after Blockstream patched the affected bridge nodes, but retained about 600 BTC. Blockstream later rejected the attacker’s demand for a 10% bug bounty in exchange for the remaining coins. Elements v23.3.4 was released on September 9 to address the vulnerability; Liquid resumed producing blocks that day, and user transactions returned on September 10.

Federation board member Samson Mow reported a 50 BTC deposit on October 28, followed by deposits of 300 BTC and 250 BTC on November 2. He identified Blockstream as the source of those funds. The Federation said on November 3 that reserves were fully restored. It publishes reserve balances at liquid.network, where Liquid node operators can verify the backing.
Users had already been able to swap BTC and LBTC through participating providers for several weeks. Some semi-automated peg-outs had also resumed, but the Federation’s update left the status of the remaining direct peg-out restrictions unclear. It said further governance, oversight, technical and operational changes were in preparation.
Source: theblock.co (originally published 2026-11-03 19:48 UTC+8)
