Jade is unaffected
jade-not-affected
https://blog.blockstream.com/jade-unaffected-coldcard-vulnerability/
Latest reviewed change
source content difference between and
Blockstream rewrote Step 4 of its migration guidance: the heading changed from "Retire the Old Recovery Phrase Safely" to "Hold Onto Your Old Device and Recovery Phrase", and the instructions to verify the old wallet is empty and then destroy the old backup were removed. The post now tells readers to keep the old phrase in case funds become recoverable later.
Step 3: Send a Test Transaction, Then the Rest
Send a small amount to the new address first. Wait for it to confirm, then check that the balance actually appears in the new wallet and that you can see it from a fresh session, not just the screen you were already looking at.
Once the test lands and you've confirmed you can see it, proceed calmly, and move the full balance.
-Step 4: Retire the Old Recovery Phrase Safely
Step 4: Hold Onto Your Old Device and Recovery Phrase
Do not reuse your old recovery phrase.
However, keep it handy. In the event that your funds become recoverable in the future, it may be necessary to prove ownership.
-Keep the old backup until the migration is completely confirmed. Destroying it early, while any balance remains, makes that balance unrecoverable.
First lines only. The complete diff is in the timeline below.
- Organisation
- Blockstream
- Evidence role
- Vendor statement
- Published
- 2026-07-31
- Source changes
- 1
- Detected differences
- 1
- Unreviewed
- 0
- Copies held
- 2
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
-
Blockstream rewrote Step 4 of its migration guidance: the heading changed from "Retire the Old Recovery Phrase Safely" to "Hold Onto Your Old Device and Recovery Phrase", and the instructions to verify the old wallet is empty and then destroy the old backup were removed. The post now tells readers to keep the old phrase in case funds become recoverable later.
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 7 lines
Step 3: Send a Test Transaction, Then the Rest Send a small amount to the new address first. Wait for it to confirm, then check that the balance actually appears in the new wallet and that you can see it from a fresh session, not just the screen you were already looking at. Once the test lands and you've confirmed you can see it, proceed calmly, and move the full balance. -Step 4: Retire the Old Recovery Phrase Safely Step 4: Hold Onto Your Old Device and Recovery Phrase Do not reuse your old recovery phrase. However, keep it handy. In the event that your funds become recoverable in the future, it may be necessary to prove ownership. -Keep the old backup until the migration is completely confirmed. Destroying it early, while any balance remains, makes that balance unrecoverable. -Look for small leftover amounts, unconfirmed transactions, and any additional accounts or asset types you may have used on that device. -Once the old wallet is confirmed empty and the new one is verified working: -Destroy the old backup. Shred or burn paper; for a metal backup, physically destroy or restamp it. -Treat that phrase as permanently retired. Never import it into another wallet, never reuse it as a passphrase, and never enter it into a website, form, or phishing tool offering to check whether it's affected. -If you can't destroy the backup immediately, store it somewhere separate from your new backup so you never confuse the two. How Jade Builds Its Randomness Your recovery phrase is only as strong as the randomness behind it, so Jade never relies on a single source. Every Jade hashes together: Timing from user interactionExtracted text as captured
Products CONSUMERS Blockstream App A multi-platform, feature-rich Bitcoin and Liquid Wallet Blockstream Jade A fully-open source hardware wallet for Bitcoin and Liquid ENTERPRISE Blockstream Enterprise Enterprise-grade custody and treasury management tool AMP An API to issue and manage digital assets on the Liquid Network DEVELOPERS TOOLS Blockstream Explorer API Search data from the Bitcoin and Liquid blockchains Greenlight Lightning node management for payments Cryptocurrency Data Feed Real-time and historical cryptocurrency trade data COMMUNITY PROJECTS Core Lightning Implementation of the Lightning Protocol Liquid Network Bitcoin layer-2 for digital asset issuance Elements An open-source, sidechain-capable blockchain platform Simplicity High-assurance smart contracts Newsroom Blog In The News Press Releases Quantum Developers Engineering Blog Liquid Documentation Core Lightning DocumentationExcerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
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
Products CONSUMERS Blockstream App A multi-platform, feature-rich Bitcoin and Liquid Wallet Blockstream Jade A fully-open source hardware wallet for Bitcoin and Liquid ENTERPRISE Blockstream Enterprise Enterprise-grade custody and treasury management tool AMP An API to issue and manage digital assets on the Liquid Network DEVELOPERS TOOLS Blockstream Explorer API Search data from the Bitcoin and Liquid blockchains Greenlight Lightning node management for payments Cryptocurrency Data Feed Real-time and historical cryptocurrency trade data COMMUNITY PROJECTS Core Lightning Implementation of the Lightning Protocol Liquid Network Bitcoin layer-2 for digital asset issuance Elements An open-source, sidechain-capable blockchain platform Simplicity High-assurance smart contracts Newsroom Blog In The News Press Releases Quantum Developers Engineering Blog Liquid Documentation Core Lightning DocumentationExcerpt 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.