Cc9f267dcClaimNews eventAn attacker exploited a bug in Blockstream's Elements open-source software to mint approximately 4,000 unbacked LBTC tokensAgreeDisagree
Cc9f267dcClaimNews eventBlockstream released Elements v23.3.4, disabling proof validation caches and hardening consensus rules to fail closedAgreeDisagree
Cc9f267dcClaimBlockstream CEO Adam Back warned developers against trusting AI-suggested code fixes without verification following the September 6, 2026 Liquid Network exploitAgreeDisagree
Cc9f267dcClaimA September 6, 2026 exploit of the Liquid Network reduced the Liquid Federation's Bitcoin reserves from about 4,205 BTC to 197 BTCAgreeDisagree
Cc9f267dcClaimThe Liquid Federation did not disclose in its official announcement who supplied the bitcoin needed to close the 600 BTC reserve shortfall caused by the September 6, 2026 exploitAgreeDisagree
Cc9f267dcClaimThe Liquid Federation announced on November 3, 2026 that it fully restored 1:1 Bitcoin reserves to back all LBTC tokens following a September 6, 2026 exploit of the Liquid NetworkAgreeDisagree
Cc9f267dcClaimAn attacker who exploited the Liquid Network on September 6, 2026 routed unbacked LBTC tokens through SideSwap's peg-out service to withdraw actual bitcoin from the Liquid Federation's reserve walletAgreeDisagree
Cc9f267dcClaimAn attacker who exploited the Liquid Network on September 6, 2026 returned 3,400 BTC the following day but retained around 598 BTC, demanding a 10% bug bounty that Blockstream refusedAgreeDisagree
Cc9f267dcClaimLiquid Federation board member Samson Mow stated Blockstream supplied 600 BTC for a deficit from the September 6, 2026 Liquid Network exploit, tracking 50 BTC sent October 28, 2026, and 300 BTC and 250 BTC sent November 2, 2026AgreeDisagree
Cc9f267dcClaimA September 6, 2026 exploit of the Liquid Network occurred in Elements software because a cache key omitted the asset commitment and scriptPubKey, allowing invalid rangeproof checks to be reusedAgreeDisagree
Cc9f267dcClaimBlockchain investigator ZachXBT reported on November 3, 2026, that an unidentified Western European institution suffered a suspected crypto theft exceeding $133 millionAgreeDisagree
Cc9f267dcClaimKraken restricted accounts associated with the suspected $133 million European Union crypto theft and initiated cooperation with law enforcement to assist recovery effortsAgreeDisagree
Cc9f267dcClaimBlockchain investigator ZachXBT stated that the laundering patterns from the suspected $133 million European institution theft did not match the typical methods used by North Korea’s Lazarus GroupAgreeDisagree
Cc9f267dcClaimBlockchain investigator ZachXBT alleged on November 3, 2026, that a large financial institution in Western Europe was exploited in a $133 million theft and was actively covering up the incidentAgreeDisagree
Cc9f267dcClaimAnalytics firm Bitquery reported that the attacker linked to the $133 million theft converted approximately $62.98 million in stablecoins into 27,553 Ether within roughly four hoursAgreeDisagree
Cc9f267dcClaimTransparent public blockchains allow third parties to deduce user identities by analyzing on-chain transaction patternsAgreeDisagree
Cc9f267dcNews eventClaimBinance said it would deploy part of its SAFU fund and use corporate assets and its futures insurance fund to cover about $6.3 billion in hack-related lossesAgreeDisagree
Cc9f267dcClaimBinance reported total losses of approximately $6.3 billion following the October 30, 2026 exploit of its hot walletsAgreeDisagree
Cc9f267dcClaimThe Security Council temporarily modified Arbitrum's Inbox contract using a function called sendUnsignedTransactionOverride to process transactions as if sent by the Binance exploiter's address, before restoring the original contract codeAgreeDisagree