r/coldcard: whether pre-window seeds with a passphrase are safe
reddit-pre-window-passphrase-safety
https://www.reddit.com/r/coldcard/comments/1vct25y/seeds_created_before_the_march_2021_and_using_a/
- Organisation
- Evidence role
- Community discussion
- Published
- not established
- Source changes
- 0
- Detected differences
- 0
- Unreviewed
- 0
- Copies held
- 1
Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
post: 1vct25y author: Sammytheseaotter created_utc: 1785604733 title: Seeds created before the March 2021 and using a passphrase are safe? body: Hi Everyone, I'm shocked as everyone else about this colossal fuck up! I'm curious if your seed was created before this shitty code was introduced in March 2021. Your seed should be secure correct? comment: p13yafh parent: t3_1vct25y author: daphonzy created_utc: 1785607200 edited: false body: If your seed was generated on MK3 prior to 2021, then my understanding is you’re not affected by this particular vulnerability (passphrase or not). You’re as safe as you were before this vulnerability was identified. comment: p13zr2f parent: t3_1vct25y author: blurred_rabbit created_utc: 1785607622 edited: false body: I wouldn’t take the risk at all. If you still want to use your device and aren’t done with them as a company you should do the following: Temporarily transfer your coin to another wallet. Update your cold card to the latest firmware fix they just released. Set it up again, generate a new seed (add a complex passphrase and do the 100+ dice rolls to be safe anyway). Do a full wallet restore test after taking note of your seed and passphrase to make sure everything you noted is correct. Then do a simple receive and send test with a small amount of coin. Then once good, send all of your coin back. But to answer your question if the passphrase is complex enough / long enough and not just a simple single word it should cover you. But more importantly did you set it up with manual dice rolls 100+? That would save you even more. comment: p14bn9v parent: t1_p13zr2f author: Sammytheseaotter created_utc: 1785611045 edited: false body: I can't trust Coinkite with any firmware update after March 2021. Also this was a rushed update. I'll be transferring my Bitcoin to another HW wallet. Just wanted to make sure my Bitcoin is safe for now. comment: p14tnxkExcerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
Compare the screenshot or a quotation against the original while it is available.