Weak-entropy wallet key migration

The source packet, bounded to the 2026-08-08 Roundtable replay, contains two wallet-generation reports: a Coldcard firmware RNG flaw allegedly exploited in a Bitcoin theft and a CryptoJS Ill Bloom weak RNG flaw exploited to steal $5.7M from wallets.

The crypto-fincrime discussion states that the urgent issue is whether private key material remains trustworthy, not which public loss estimate is correct.

Because software updates do not repair weak seed provenance, delay leaves funds under keys that the packet-supported analysis says should no longer be trusted when generated through the vulnerable path.

Affected wallet holders are those whose seeds were generated through weak random-number paths associated in the packet with Coldcard firmware RNG allegations or CryptoJS Ill Bloom weak RNG; their exposure is that the seed provenance, not merely the current software state, is untrustworthy.

Multisig participants are affected when one signer key was generated through the weak path; their exposure is continued reliance on compromised signer material until that signer is rotated.

Custodians and hot-wallet operators are affected when they hold funds under keys generated through those paths; their exposure is operational loss risk if they only patch software and leave old seeds in service.

Exchanges are affected when asked to restrict funds connected to the incident; their exposure is overblocking if they freeze broadly without direct taint evidence or legal process.

Wallets whose generation path is unknown are not automatically proven affected by this packet, but they require provenance review before being treated as safe.

The crypto-fincrime discussion directly supports the operational rule: for Coldcard and CryptoJS Ill Bloom wallets generated in the vulnerable path, the private key material should not be trusted, and patching firmware or an app does not repair an already weak seed.

The Coldcard handoff summary reports an alleged firmware random-number-generation flaw tied to a Bitcoin theft allegation, which supports treating Coldcard-generated wallet provenance as a sensitive trust-material issue when the generation path is credibly affected.

The CryptoJS Ill Bloom handoff summary reports weak random-number generation exploited to steal $5.7M from wallets, which supports the same migration logic for wallets generated through that weak path.

The final synthesis identifies hot-wallet infrastructure as delegated-trust infrastructure, which supports prioritizing key provenance over software-state alone.

The evidence review supports moving funds to freshly generated keys and rotating multisig material where applicable, while separately noting that affected-version boundaries still need enrichment.

The scout framed the decision as an operational trust-material question: whether wallet seeds generated through reported weak random-number paths should still hold funds.

The crypto-fincrime discussion shifted the focus away from disputed loss totals and toward seed provenance, stating that Coldcard and CryptoJS Ill Bloom wallets generated in the vulnerable path should not be trusted and that patching firmware or an app does not repair an already weak seed.

The evidence review supported the migration logic but flagged that the packet does not establish authoritative affected firmware or app-version boundaries.

The boundary review kept the public position limited to wallets known or credibly assessed to have been generated through weak entropy paths, avoiding broad theft, provenance, or exchange-freeze claims. The arbiter selected a new operational-action record on that scoped basis.