Cc9f267dcClaimThe SP1 soundness flaw affected native Rust verification in sp1_hypercube, sp1_prover, and sp1_sdk versions 6.0.0 through 6.8.0AgreeDisagree
Cc9f267dcClaimA high-severity soundness bug in Succinct's SP1 zero-knowledge proving system exposed Succinct's mainnet Prover Network to invalid execution proofs from third-party proversAgreeDisagree
Cc9f267dcClaimSecurity firm Blockaid warned that the X100 governance takeover attack launched on October 24, 2026 on the Ethereum network was ongoingAgreeDisagree
Cc9f267dcClaimThe X100 protocol governance takeover attack on October 24, 2026 targeted assets held on the Ethereum blockchain, liquidating liquidity pools and treasury reservesAgreeDisagree
Cc9f267dcClaimSuccinct deployed the version 6.8.1 patch for SP1's soundness bug to the mainnet Prover Network, requiring no configuration changes from users requesting network proofsAgreeDisagree
Cc9f267dcClaimAn attacker could exploit SP1 by supplying proof data with mismatched size labels, causing the native Rust verifier to accept an invalid proofAgreeDisagree
Cc9f267dcClaimSuccinct stated in GitHub security advisory GHSA-p7v2-jjv3-8p8f that its mainnet Prover Network was the only known deployment affected by a high-severity soundness bug in SP1's proving systemAgreeDisagree
Cc9f267dcClaimSuccinct advised users running native Rust verifiers in SP1 who accept proofs from untrusted provers to upgrade their software to version 6.8.1AgreeDisagree
Cc9f267dcClaimSuccinct released version 6.8.1, which patched a high-severity soundness bug in SP1, on September 24, 2026, 17 days before publishing GitHub security advisory GHSA-p7v2-jjv3-8p8f on October 11, 2026AgreeDisagree
Cc9f267dcClaimThe conversion of stolen USDT into ether following the X100 exploit was carried out shortly after the X100 protocol treasury tokens were drained on October 24, 2026AgreeDisagree
Cc9f267dcClaimThe X100 protocol exploit on October 24, 2026 was executed in two transactions that converted X100 protocol treasury tokens and liquidity positions into USDTAgreeDisagree
Cc9f267dcClaimBlockchain security firm Blockaid reported that malicious activity targeting the X100 protocol continued following the initial treasury drain on October 24, 2026AgreeDisagree
Cc9f267dcClaimThe primary exploiter in the X100 protocol governance takeover attack on October 24, 2026 converted approximately 4.75 million USDT into etherAgreeDisagree
Cc9f267dcClaimThe proceeds from the X100 protocol exploit on October 24, 2026 were split across four wallets, with a distribution wallet retaining an additional 423 ETHAgreeDisagree
Cc9f267dcClaimAfter swapping USDT into ether, the X100 attacker in the October 24, 2026 governance takeover initiated wallet transfers to disperse the stolen funds across multiple Ethereum addressesAgreeDisagree
Cc9f267dcClaimThe intrusive Monero compliance emails sent by Kraken were triggered after a Kraken employee flagged a young client holding substantial wealth as a red-flag riskAgreeDisagree
Cc9f267dcClaimKraken co-CEO Arjun Sethi announced on October 24, 2026, that Kraken withdrew intrusive compliance questionnaires sent to Monero (XMR) buyers asking about their employers, sources of funds, and intended coin useAgreeDisagree
Cc9f267dcClaimHardware wallet manufacturer Trezor disclosed a customer data breach in August 2026 caused by unauthorized access at its third-party logistics provider, ShipMonkAgreeDisagree
Cc9f267dcClaimKraken's compliance policy, amended on October 1, 2026, allows the exchange to restrict deposits or trading for non-compliant accounts, though withdrawals remain unaffectedAgreeDisagree
Cc9f267dcClaimKraken discontinued Monero trading and deposits for clients in the European Economic Area and the United Kingdom, citing regulatory changesAgreeDisagree