🧩 One Incident Can Create Two Different Recovery Problems
Blockstream reported that an attacker exploited a rangeproof-verification cache bug on September 6. Federation signers released approximately 3,996 BTC on Bitcoin mainnet before the Liquid network was paused.
The attacker later returned around 3,400 BTC, leaving approximately 600 BTC subject to continuing recovery and accounting efforts at the time of the later assessment.
The chain problem and reserve problem are related, but they are not identical.
Replaying the chain without the faulty cache allowed invalid transactions and their descendants to be identified deterministically. That helps restore confidence in chain history. It does not automatically replace every reserve asset or settle every outstanding accounting question.
Sidechain security should be measured across code correctness, federation controls, peg accounting, monitoring and recovery procedures.
Reopening operations should depend on independently verified chain history and reserve reconciliation—not only the amount already recovered.
Disclaimer: Protocol-security commentary only. Recovery totals and incident status may change as technical and financial reviews continue.
$BTC
Liquid Network • Blockstream • Bitcoin Infrastructure
#Bitcoin #Sidechains #BlockchainSecurity
Blockstream reported that an attacker exploited a rangeproof-verification cache bug on September 6. Federation signers released approximately 3,996 BTC on Bitcoin mainnet before the Liquid network was paused.
The attacker later returned around 3,400 BTC, leaving approximately 600 BTC subject to continuing recovery and accounting efforts at the time of the later assessment.
The chain problem and reserve problem are related, but they are not identical.
Replaying the chain without the faulty cache allowed invalid transactions and their descendants to be identified deterministically. That helps restore confidence in chain history. It does not automatically replace every reserve asset or settle every outstanding accounting question.
Sidechain security should be measured across code correctness, federation controls, peg accounting, monitoring and recovery procedures.
Reopening operations should depend on independently verified chain history and reserve reconciliation—not only the amount already recovered.
Disclaimer: Protocol-security commentary only. Recovery totals and incident status may change as technical and financial reviews continue.
$BTC
Liquid Network • Blockstream • Bitcoin Infrastructure
#Bitcoin #Sidechains #BlockchainSecurity
