Don't want to trade it yourself?
Our desk runs DEX portfolios on profit share.
- BTC-USD
-
Nearly 4,000 BTC left Liquid’s federation reserves even though Liquid said the relevant peg-out authorization key was not compromised.
-
The federation’s normal signing process approved the withdrawal after apparently invalid L-BTC reached an authorized peg-out service.
-
The incident shows how <a href="https://xpertsstudio.com/bitcoin-faces-key-support-test-at-78-3k-as-us-crude-oil-hits-three/” title=”Bitcoin faces key support test at $78.3K as US crude oil hits three”>Bitcoin bridge security depends on software validation as well as custody keys.
-
The self-described white hats have since returned 3,400 BTC, while roughly 598.5 BTC remains with them.
Nearly $320 million in Bitcoin left the Liquid Network without attackers stealing the cryptographic keys protecting its federation wallet.
That detail may be more important than the size of the withdrawal.
On Sept. 6, roughly 4,000 L-BTC was submitted to SideSwap’s peg-out service. The tokens passed through a valid authorization process and were burned, after which Liquid’s federation released approximately 3,996 BTC to the recipient.
Liquid said the SideSwap Peg-out Authorization Key used in the transaction was not compromised.
Instead, SideSwap said Blockstream later determined that the L-BTC involved had been created through a bug in Elements, the software underlying Liquid.
That means the system appears to have authorized the release of real Bitcoin against L-BTC that should not have existed.
Liquid’s Keys Worked as Designed
Liquid does not rely on a single custodian to control its Bitcoin reserves.
Its federation uses a multisignature system in which 11 of 15 functionaries can authorize Bitcoin movements. Onchain analysis of the incident found that the withdrawal carried the required 11 valid signatures.
In other words, the attackers did not need to steal enough private keys to overpower the federation.
The signing infrastructure appears to have processed what it believed was a legitimate peg-out.
That exposes a different bridge risk: secure private keys cannot protect reserves if the software feeding transactions into the signing process incorrectly determines that a withdrawal is valid.
Liquid’s model depends on L-BTC remaining backed 1:1 by Bitcoin held by the federation.
If unbacked L-BTC can reach a legitimate redemption route, the problem moves upstream of key custody.
$270 Million Returned After Blockstream Patch
The incident has since taken an unusual turn.
The actors identified themselves through an onchain message as “whitehats” and told Blockstream they would return most of the Bitcoin once the vulnerability was fixed.
Blockstream later sent a PGP-signed message stating that its bridge nodes had been patched and that the funds could safely be returned.
Source: finance.yahoo.com