Cc9f267dcClaimBitfinex Securities hosts tokenized shares of public companies that hold Bitcoin treasuries, including MicroStrategyAgreeDisagree
Cc9f267dcClaimBlockstream CEO Adam Back stated that Liquid Network refreshed peg-out authorization keys, moved them to cold hardware wallets, and completed third-party security auditsAgreeDisagree
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
Cc9f267dcClaimThe Liquid Network public dashboard on November 3, 2026 showed 4,270.54 BTC held in reserve matching 4,270.54 BTC pegged into LBTCAgreeDisagree
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
Cc9f267dcClaimZcash's underlying privacy design originated from the Zerocash protocol, which was originally proposed for deployment on BitcoinAgreeDisagree
Cc9f267dcClaimMastercoin, launched in 2013, was an early Bitcoin meta-protocol that later became known as Omni LayerAgreeDisagree
Cc9f267dcClaimCoinbase Chief Security Officer Jeff Longhofer conducted an exercise deploying sixteen artificial intelligence models against the Bitcoin Core codebase, identifying two minor bugs that were patchedAgreeDisagree
Cc9f267dcClaimShielded Bitcoin transfers use a note and nullifier cryptographic data structureAgreeDisagree
Cc9f267dcClaimBitcoin PIPEs enables binary covenants and pessimistic zero-knowledge proof verification on Bitcoin without changes to Bitcoin's consensus rulesAgreeDisagree
Cc9f267dcClaimImplementing post-quantum zero-knowledge proof systems in Shielded Bitcoin increases the required transaction sizeAgreeDisagree
Cc9f267dcClaimShielded Bitcoin allows users to generate selective disclosure data to share transaction records with accountants and authoritiesAgreeDisagree
Cc9f267dcClaimA Shielded Bitcoin transfer publishes a ciphertext containing wallet state data alongside a zero-knowledge proof verifying the ciphertext's correctnessAgreeDisagree
Cc9f267dcClaimShielded Bitcoin enables transferring Bitcoin without publicly revealing the transaction sender, receiver, or transfer amountAgreeDisagree
Cc9f267dcClaimShielded Bitcoin provides institutional participants transaction privacy to prevent front-running on large Bitcoin purchases or balance-sheet disclosuresAgreeDisagree