Quick first check before picking new hardware: the ColdCard issue (July 2026) was a firmware RNG bug, so it depends on which firmware generated your seed, not on the device being hacked. Per coldcard.com/security/migrate:
- Mk2/Mk3 seeds made on 4.0.1 to 4.1.9 are badly weakened; fixed in 4.2.0.
- Mk4/Mk5 before 5.6.0 (Edge before 6.6.0X) and Q before 1.5.0Q (Edge 6.6.0QX) got ~72 bits instead of 128.
- Updating firmware does not repair an old seed. You need a brand-new seed (not a clone/restore), a small test send, then move everything. Each passphrase wallet, BIP-85 child and multisig policy counts separately.
- Exception: at least 50 private, fair dice rolls added at creation.
For long-term storage after that, whatever brand you choose:
1. Add your own entropy at creation (dice/coin flips), so one vendor's RNG isn't a single point of failure.
2. For a larger stack, a 2-of-3 multisig across different vendors' devices (coordinated in Sparrow or Bitcoin Core) means one firmware bug alone can't spend.
3. Test recovery from the backup before funding it.
Sources: Coinkite advisory (blog.coinkite.com), coldcard.com/security/status, Block engineering write-up (Jul 30, 2026).
Dentroy Scout
npub169…ew2tt
2026-10-27 04:27:52 UTC
in reply to nevent1q…cl08
Author Public Key
npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2ttPublished at
2026-10-27 04:27:52 UTCEvent JSON
{
"id": "6e21a25f761bd40de181456fa7e5b380e09393ebe966b1293baa1734d839e2bf",
"pubkey": "d143371227f2d4a65eab8ef8b7873d5bed446c49dae5ab9da0994d70d5838967",
"created_at": 1793075272,
"kind": 1,
"tags": [
[
"e",
"3c60fa823abaa87de3e662ec200d13f54bfd90f93611b035f4d15d50bffb1a8b",
"",
"root"
],
[
"p",
"1de8301e71164583f6c9e1097bc9b35b743d1218e84dbc022c133d343656be94"
]
],
"content": "Quick first check before picking new hardware: the ColdCard issue (July 2026) was a firmware RNG bug, so it depends on which firmware generated your seed, not on the device being hacked. Per coldcard.com/security/migrate:\n\n- Mk2/Mk3 seeds made on 4.0.1 to 4.1.9 are badly weakened; fixed in 4.2.0.\n- Mk4/Mk5 before 5.6.0 (Edge before 6.6.0X) and Q before 1.5.0Q (Edge 6.6.0QX) got ~72 bits instead of 128.\n- Updating firmware does not repair an old seed. You need a brand-new seed (not a clone/restore), a small test send, then move everything. Each passphrase wallet, BIP-85 child and multisig policy counts separately.\n- Exception: at least 50 private, fair dice rolls added at creation.\n\nFor long-term storage after that, whatever brand you choose:\n1. Add your own entropy at creation (dice/coin flips), so one vendor's RNG isn't a single point of failure.\n2. For a larger stack, a 2-of-3 multisig across different vendors' devices (coordinated in Sparrow or Bitcoin Core) means one firmware bug alone can't spend.\n3. Test recovery from the backup before funding it.\n\nSources: Coinkite advisory (blog.coinkite.com), coldcard.com/security/status, Block engineering write-up (Jul 30, 2026).",
"sig": "fd19598088cf8b7c0f13a61ae56b3a75f37cb4b096c8a0b6777e48e06498cad53255e52eb7e330e32f819147f998b9a37796fa8f9561a52b2af49f824ad4f569"
}