Cc9f267dcClaimOn October 31, 2026, an Ethereum block reorganization triggered THORChain solvency checks after 10 ETH were refunded, leading operators to suspend trading on 10 of 13 connected blockchains on November 1, 2026AgreeDisagree
Cc9f267dcClaimThe multi-chain withdrawals during the October 29 Binance hack compromised Binance's internal transaction signing infrastructure rather than leaking the underlying private keysAgreeDisagree
Cc9f267dcClaimBinance's initial public investigation into its October 29, 2026 hack stated that a compromised DevOps engineer's laptop allowed an attacker to access a service container and execute unauthorized withdrawal transactionsAgreeDisagree
Cc9f267dcClaimOn the Saturday following the October 29, 2026 Binance hack, THORChain node operators halted trading across multiple chains after an Ethereum block reorg caused THORChain to pay out 10 Ether that its vault had not receivedAgreeDisagree
Cc9f267dcClaimArbitrageurs who rebalance THORChain's Asgard vaults after large North Korean asset swaps frequently use Binance as their source of trading liquidityAgreeDisagree
Cc9f267dcClaimBinance publicly stated that its investigation into the October 29 hack found no evidence of any hot wallet private key leaksAgreeDisagree
Cc9f267dcClaimIndividuals cannot deploy a THORChain node without first receiving approval through the protocol's whitelisting processAgreeDisagree
Cc9f267dcClaimTHORChain's emergency halt mechanism required only three node operator votes to suspend signing across Cosmos, Bitcoin Cash, BNB Smart Chain, Bitcoin, Dogecoin, Litecoin, Solana, Tron, and ZcashAgreeDisagree
Cc9f267dcClaimFollowing Binance's initial statement attributing the October 29 breach to a single laptop, Binance issued an update stating that investigators had uncovered additional points of breachAgreeDisagree
Cc9f267dcClaimA March 17, 2021 firmware migration error caused Coinkite Coldcard devices to run seed generation on a software generator instead of hardware, producing weak recovery phrasesAgreeDisagree
Cc9f267dcClaimUsing a 128-character passphrase on a Trezor device requires both the latest Trezor Suite app and updated device firmware, while older Trezor firmware retains a 50-character limitAgreeDisagree
Cc9f267dcClaimAttackers reconstructed weak Coldcard recovery phrases to access wallets, but users with strong, unique passphrases were protected from the Coldcard attacksAgreeDisagree
Cc9f267dcClaimGalaxy Digital's Alex Thorn estimated that the Coldcard seed vulnerability resulted in over 1,596 BTC stolen across roughly 7,300 addresses, totaling over $100 million in lossesAgreeDisagree
Cc9f267dcClaimTrezor stated that increasing Trezor's passphrase length was prompted by user inquiries following the July 2026 Coldcard seed generation flawAgreeDisagree
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
Cc9f267dcClaimTrezor warned in August 2026 that length alone does not guarantee entropy because automated cracking tools systematically test dictionary words, leaked passwords, and common patternsAgreeDisagree
Cc9f267dcClaimTrezor designated Trezor's passphrase feature as an advanced feature and warned users that a mistyped or forgotten passphrase can result in lost fundsAgreeDisagree
Cc9f267dcClaimOn August 2, 2026, X account BTC Sessions reported the first confirmed loss from the July 2026 Coldcard seed flaw thefts involving a device using a weak two-word passphraseAgreeDisagree
Cc9f267dcClaimCoinkite advised that Coldcard wallets were vulnerable unless created with 50 independent dice rolls or protected by a strong, unique passphraseAgreeDisagree
Cc9f267dcClaimTrezor stated in August 2026 that its own hardware wallets were unaffected by the July 2026 Coldcard seed generation flaw, but advised users to move wallets created on a Coldcard and restored on a TrezorAgreeDisagree