Release Notes

v1.60 — November 4, 2026

A new way to make a seed where every bit of randomness is your own: draw the words by hand, flip a coin, and SafeKeep works out the last word.

• Draw Your Own Words — a third mode in the Entropy Generator (under Advanced), next to Mixed and Verifiable Dice. Put the 2048 BIP-39 words on slips, mix them in a bag and draw 11 words (23 for a 24-word seed), putting each slip back. Flip a fair coin 7 times (3 for 24 words): Heads = 1, Tails = 0. SafeKeep works out the last word, and nothing else is mixed in. See Draw Your Own Words in the guide.
• Check it on SeedSigner — it’s the same calculation as SeedSigner’s Tools → Calc 12th/24th word → Coin flip entropy, so the same words and flips give the same last word there.
• Draw the words; never choose them — words you pick or remember follow patterns an attacker can guess. SafeKeep refuses a draw that looks made up: the same word three times, four neighboring words from the word list in a row, or words in alphabetical order. It also asks you to confirm that you drew the words and flipped a real coin.
• License — the MIT license is now included as a LICENSE file in the source code.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.60.tar onto the Transfer Drive, unlock, and install it from Device Options → Update SafeKeep → Check for update, then Install update and Restart now.

v1.59 — November 3, 2026

QR settings that apply while the code is running, a Silent Payment address in Show an address, and a tidier Dashboard.

• QR sliders that apply right away — in the Courier (Transfer files) and the PSBT Signer, Density and Speed now take effect while the QR code is running. A new Speed applies on the next frame; a new Density re-cuts the file and starts again from the first piece. If the sender changes Density part-way through, the receiver says “The sender changed its settings, so receiving starts over”, and it never joins pieces from two settings into one file. The online Courier Tool has the same change. Flash drives on v1.58 or older don’t have this check, so update them before changing Density during a transfer.
• Show an address — this seed’s Silent Payment address (sp1q…) is now in the list: one reusable address, so it has no New address button. The address number box updates the address as you type, with no Show button.
• Seed Management — after Download JSON, SafeKeep offers Send with the Courier.
• Dashboard — Health is filled in as soon as the Dashboard opens (it could be blank before). The wallet card’s three words are shown in quotes and labelled “seed nickname”, with a note that they aren’t part of your recovery words. The wallet card and Health are the same width, the task tiles read Sign a transaction, Show an address, Connect a wallet app, Transfer files, Back up, the title is a little larger, and the wallet card has the same border as the other cards.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.59.tar onto the Transfer Drive, unlock, and install it from Device Options → Update SafeKeep → Check for update, then Install update and Restart now.

v1.58 — November 2, 2026

A vault that doesn’t have to keep your seed, a clearer wallet card for passphrase wallets, and simpler ways to connect Specter and import a multisig.

• Seed storage — in Device Options → Seed storage you can stop keeping your master seed on the flash drive. The vault still opens with your Master Passphrase, with your passphrases, saved wallets, notes and settings; at each start you scan your SeedQR or type your words, and the seed stays in memory until you lock or shut down. Before the seed is deleted, your SeedQR or words must match it. Someone with the flash drive and its Master Passphrase still can’t spend without your SeedQR or words.
• Passphrase wallets — with a passphrase on, the wallet card is titled with that wallet’s name from your Passphrase Library, and the three-word nickname shows as the seed’s. Picking a passphrase from the Library on the Dashboard applies it straight away.
• Import a wallet — Output Descriptor’s Import tab reads a wallet made in Sparrow, Specter, Nunchuk or another coordinator in one scan, checks it against your seed, and saves it there and then.
• Specter by QR — Connect a wallet app → Specter shows a QR code for Specter’s Add new device → Other → Scan QR code, and Output Descriptor’s QR has a For Specter option for importing a whole wallet.
• Back from a Temporary Session — Unlock my vault instead returns to the unlock screen without restarting.
• Smaller fixes — a Show words / Hide words button on seed displays, Seed Management back on the Dashboard, and saved wallets kept in Output Descriptor.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.58.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep.

v1.57 — November 1, 2026

A new look for SafeKeepVault, with two new guided tasks: show a receive address, and connect a wallet app.

• A new Dashboard — a wallet card with the loaded seed’s LifeHash, fingerprint and nickname; a Health list with the last backup, the Transfer Drive and the version; tiles for Sign, Show an address, Back up, Connect a wallet app and Transfer; then your saved wallets and all the tools. Health remembers when this flash drive last made a backup, even after the .7z is moved off it.
• One status badge — the status lights are now a single “Offline · Protected” badge. Click it to see each light.
• A clearer welcome — a new flash drive offers Create a new wallet or I already have a backup, which lists each way to restore.
• Show an address — the next receive address of this seed’s wallets, or of a saved wallet, as a large QR code. New address moves to the next one, and the vault remembers where each wallet is up to, even after a restart.
• Connect a wallet app — step-by-step setup for Blue Wallet, Electrum, Nunchuk, Sparrow, Specter and any other wallet. SafeKeep opens Seed Management with the right export for your app and tells you what to tap.
• Tool screens — shorter headers with “More about this tool”, numbered PSBT signing steps, rounded corners and a tidier Device Options.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.57.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep.

v1.56 — October 28, 2026

Opening a saved wallet in the Output Descriptor tool now sets the form to that wallet.

• Multisig — opening a saved 2-of-3 (or any M-of-N) switches the form to Multisig with the wallet’s threshold and address type, and fills in the other cosigners’ keys and fingerprints, so Generate Descriptor rebuilds the same wallet. Before, the cosigner keys stayed empty and Generate Descriptor gave an error.
• Single-sig — opening a single-sig wallet switches the form to Single-Sig with its address type.
• No leftovers — cosigner keys from a wallet you opened before are cleared. If the form can’t rebuild a wallet (for example it uses a passphrase you haven’t entered), the message says why.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.56.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep.

v1.55 — October 28, 2026

Backups no longer need an online computer: send one to your phone, check that it opens, and restore a new flash drive from it.

• Restore a new flash drive with the Courier — on the welcome screen, choose Unlock .7z Backup, then Receive a Backup with the Courier, and play your .7z backup from the Courier Tool on a phone or another computer. SafeKeep saves it to the Transfer Drive and selects it, ready for its password, so a new flash drive never has to be plugged into another computer. No camera? Copying the backup onto the flash drive’s TRANSFER drive works as before.
• Send a new backup to your phone — after Export Backup, Send with the Courier plays the new backup as a Courier loop, so your phone can keep a copy.
• Check a Backup — open a backup with its password (typed or scanned from its QR code) and see what it holds: whether its Master Seed is the one loaded now, how many notes and saved passphrases it has, and whether settings are included. Nothing is restored or changed, so you can find out a backup works before you need it.
• Less left in memory — a backup unlocked for a restore that is never finished is deleted from memory after two minutes, instead of staying until you shut down.
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.55.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Everything in this release reaches updated flash drives.

v1.54 — October 27, 2026

Most PCs now start SafeKeepVault with Secure Boot left on.

• Secure Boot can stay on — the flash drive’s boot loader is now Ubuntu’s signed one (a shim signed by Microsoft, then GRUB and the kernel signed by Canonical), so a PC with Secure Boot on starts it without changing settings. On Windows PCs with BitLocker, that also avoids the recovery-key prompt that turning Secure Boot off can cause. Secure Boot checks the boot loader and kernel, not the rest of the flash drive: verify your download as always.
• Flash a new flash drive to get it — the boot loader lives on the flash drive’s boot partition, which updating in place never changes. Flash SafeKeep-Release-v1.54.zip onto a flash drive (back up your vault first). A flash drive you update keeps working as now, with Secure Boot off.
• Still needs Secure Boot off — newer PCs that trust only Microsoft’s 2023 certificates, “Secured-core” PCs with the Microsoft third-party certificate switched off, and Intel Macs with the T2 chip (Startup Security Utility → No Security).
• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.54.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault is not touched.

v1.53 — October 27, 2026

Add SafeKeep to Nunchuk or Sparrow by scanning its screen, with animated QR codes for anything dense.

• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.53.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault is not touched.
• Add SafeKeep to your wallet by scanning — no more saving a file and carrying it over with the Courier. For Nunchuk, choose Hardware Wallet JSON in Seed Management, press Show QR, then Play as animated QR, and add a key as a Passport in Nunchuk. For Sparrow, choose BC-UR Account and add an Airgapped Hardware Wallet keystore by scanning. See Nunchuk and Sparrow.
• Animated QR codes — a QR code dense enough to trouble a camera, such as a Hardware Wallet JSON export or a larger multisig descriptor, now offers Play as animated QR: the same text in a loop of much simpler codes, which Sparrow, Nunchuk, Keystone, BlueWallet and other wallets read.
• Seed Management — a passphrase you type must be typed twice: a typo used to show, and export, a different empty wallet without warning. The BIP-380 key format now gives the full output descriptor, exactly as the Output Descriptor tool makes it.
• BIP-85 Child Seeds — the passphrase fills in from the Dashboard, and one you type must be typed twice: a typo used to make child seeds your backup could never rebuild.
• Check Shares I Already Have — can now show the seed words the shares rebuild, labelled as your vault seed or clearly as a different one, and checks shares of either length.
• Things come into view — QR codes, camera scan windows and the welcome screen’s restore panels scroll onto the screen by themselves.
• “SafeKeep” in the Mac boot menu — holding Option on a Mac shows the flash drive as SafeKeep instead of “EFI Boot”, on flash drives flashed from this release.
• Smaller fixes — messages no longer use names from early builds (“codex”, “cipher”), and the browser is pinned to one checked version.

v1.52 — October 23, 2026

Seed XOR and Shamir Backup, rebuilt: one share at a time, each one checked against your paper before you move on.

• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.52.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault is not touched.
• One share at a time — Seed XOR Splitter and Shamir Backup now work the same way. Choose how many shares (“all 3 needed”, or “any 2 of 3”), then SafeKeep shows each share on its own screen, with Print and Show QR. Write it down, then type it back with word suggestions, or scan its QR code. A wrong word is pointed out by its position. At the end SafeKeep checks that the shares you typed rebuild your seed exactly.
• Check Shares I Already Have — in both tools. Type in or scan shares you made earlier, and SafeKeep tells you whether they rebuild your vault seed, without ever showing the seed.
• Easier recovery — on the welcome screen, Restore via Seed XOR and Recover Shamir Backup use the same word boxes with suggestions. Shamir recovery checks each share as you add it, says how many more you need, and now accepts more shares than the minimum.
• Removed — the Copy buttons, Seed XOR’s Merge tab (combine shares from the welcome screen, or check them with Check Shares) and the long pages showing every share at once.
• Shamir prints — a printed Shamir share no longer shows your seed’s last word, which gave away a little of the seed. The fingerprint still identifies it. And a BIP-39 passphrase on the Dashboard is no longer used as the shares’ passphrase without asking.
• Quieter start — the brief “Download started” message and the flash of a Mount Transfer Drive box after unlocking are gone. Nothing was ever downloaded: that is how the app passes requests to the system.

v1.51 — October 22, 2026

A stronger vault password: SafeKeep refuses one that is easy to guess, can generate a strong one for you, and lets you change it without resetting the flash drive.

• Update in place — on a v1.47 or later flash drive, copy SafeKeep-Update-v1.51.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault and your vault password are not touched.
• Weak passwords refused — when you set up a vault, SafeKeep rates the password. One that is easy to guess, such as a common password, a name and a year, or a few words, is refused. One that is only fair asks you to confirm. A long random password from a password manager goes straight through, as before.
• Generate One for Me — no password manager? At setup, SafeKeep makes a strong password of 6 random words and shows it as a QR code and as words. Save it one way or both: scan the QR code into your phone’s password manager, or write the words down. Then check your copy by scanning it back from your phone or typing the words, before the vault is locked with it.
• Change Master Passphrase — in Device Options. SafeKeep locks, asks for your current password and a new one on the same screens as setup, and changes it without touching what is in your vault. Then you unlock with the new one.
• Weak password warning — if your vault was set up with an easy-to-guess password, the Dashboard says so and offers to change it.
• Backup password strength — the Encrypted Backup screen shows how strong the backup password is, and refuses a weak one: a backup can be copied to a computer and guessed far faster than the vault.
• Setup fixes — Cancel during setup now goes back a step (or offers to shut down) instead of ending at a black screen, and every setup screen fits a 1080p display.

v1.50 — October 21, 2026

Safer seed generation: SafeKeep now checks its randomness before every seed and refuses dice rolls that could be guessed.

• Update in place — on a v1.47, v1.48 or v1.49 flash drive, copy SafeKeep-Update-v1.50.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault is not touched. Updating from v1.48 can still end with a screen of scrolling errors on Restart now: the update is already complete, so holding the power button is safe.
• Random number check — before making any seed, SafeKeep tests the computer’s random number generator. If its output looks broken (for example lopsided, repeating or counting up), no seed is made and you see why.
• Patterned dice refused — in Verifiable Dice mode the rolls are the whole seed, so SafeKeep now refuses rolls that follow a pattern, such as 123456 over and over or long runs of one face. Rolls that only look unusual need you to tick a box confirming they came from real dice.
• Stronger mixing — in Mixed mode your dice, cards, mouse and camera input is now combined with a fresh draw from the computer’s random number generator using SHA-256, so the seed is at least as strong as the better of the two.
• Mouse counts for less — mouse movement now adds 0.25 bits a sample and can fill at most half the meter, so the rest has to come from dice, cards or camera noise. After a seed is made, everything you added is cleared, so the next seed starts fresh.

v1.49 — October 20, 2026

A cleaner start and finish: a new boot logo, a shutdown screen you can actually see, and no more stuck restarts after an update.

• Update in place — on a v1.47 or v1.48 flash drive, copy SafeKeep-Update-v1.49.tar onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault is not touched.
• Restart after an update — clicking Restart now after installing an update could end with a screen of scrolling errors, and the computer had to be switched off with the power button. The update itself was always complete and safe. SafeKeep no longer ejects its own USB flash drive while shutting down, which caused it. Updating from v1.48 can still show those errors once, because v1.48 does that restart: holding the power button is safe.
• New boot logo — SAFEKEEP VAULT in bold Bitcoin-orange blocks on the start-up and shutdown screens.
• Shutdown screen — “Session ended. Powering off…” now actually appears when you power off or restart.
• Factory Reset — the description in Device Options now says what a reset does: it erases everything in the encrypted vault, restarts, destroys the vault’s keys and starts setup for a new vault, leaving the Transfer Drive alone.

v1.48 — October 20, 2026

The first version you can install without reflashing, plus a quicker first start and smoother backups.

• Update from v1.47 in place — this release comes with the first signed update file, SafeKeep-Update-v1.48.tar. On a v1.47 flash drive, copy it onto the Transfer Drive and install it from Device Options → Update SafeKeep. Your vault and Transfer Drive are not touched. Flash drives set up with v1.46 or earlier still need the one last reflash described in the update guide.
• No restart after setting up the vault — once the encrypted vault is created, choose Continue now to go straight to the unlock prompt and start SafeKeep. If you’re restoring from a .7z backup that isn’t on the flash drive yet, choose Shut down to copy a backup onto the flash drive instead.
• Setting the vault password — a typed password is shown as you type it and asked for twice, so a typo can’t lock you out of a new vault. If the QR scan doesn’t read a code within 30 seconds, you’re taken back to choose scanning or typing again. Setup also shows the size of the vault it creates.
• Factory reset restarts once — after the vault is destroyed, setting up a new one starts straight away instead of after a second restart.
• Interrupted setup recovers — if the computer lost power while the vault was being created, the next start says so, removes the unfinished (empty) vault and runs setup again.
• Encrypted Backup — a backup from a brand-new vault no longer fails with “7z exited with code 1” when Application Settings is ticked before any setting has been saved. Scanning the backup password from a QR code now fills both password fields, so you scan it once.

v1.47 — October 19, 2026

SafeKeep can now update itself from a signed file, without reflashing and without touching your vault. Getting there takes one last reflash, onto a flash drive of 8 GB or more.

• Update SafeKeep — a new section in Device Options. Copy a signed update file onto the Transfer Drive, click Check for update, then Install and Restart now. SafeKeep installs it only if it carries the maintainer’s signature, checked against the key built into the flash drive, and only if it is newer than what you’re running. Before installing it shows the version, the build stamp and the app’s SHA-256, to compare with the release on GitHub. The first update file will come with v1.48.
• Two copies of the system — the flash drive now holds two copies of SafeKeep’s operating system. An update is written into the spare copy and checked before it is switched on, so a power cut or a bad file never leaves a flash drive that won’t start. The version you updated from stays available as previous version in the start-up menu.
• 8 GB flash drives — the two copies and a Transfer Drive big enough for an update file (now 2.5 GB) need a flash drive of 8 GB or more. The download is still about 1.3 GB.
• One last reflash — flash drives set up with v1.46 or earlier can’t update in place. Back up, flash v1.47 and restore once, as the update guide explains. If your flash drive is smaller than 8 GB, flash v1.47 onto a new one.
• A sound for each QR code read — every scanner in the app plays the soft tick of the hover sound when it reads a QR code, and again for each new frame of an animated QR, so you can hear a transaction coming in. It follows the sound settings in Device Options.
• Check Verifiable Dice on Ian Coleman’s tool — the Verifiable Dice panel explains how: choose entropy type Base 10 (its Dice type counts a 6 as 0 and gives different words) and the same word count. Do this only with practice rolls, or with the tool’s offline copy on a computer that never goes online again.

v1.46 — October 17, 2026

The PSBT Signer now checks every transaction against the wallets you own and shows exactly what it spends, and a mistyped passphrase can no longer slip through.

• Saved wallets — in the Output Descriptor tool, Save to Vault keeps a wallet’s watch-only descriptor in the encrypted vault, with a name you choose. The PSBT Signer then says which of your wallets a transaction spends from, and warns when an input matches none of them. It works this out itself from the descriptor and never takes the PSBT’s word for it.
• Change you no longer have to check by hand — when a change output is one of your saved wallet’s own addresses, it is verified, even in PSBTs that leave out the multisig details (for example BlueWallet’s compact QR exports). A payment to another of your own wallets still needs its checkbox.
• What the transaction does — the review starts with a summary: how much you are sending, the mining fee, the total leaving your wallet, and the change coming back. Below it, the inputs being spent, with each one’s amount, address, saved wallet and, for multisig, how many signatures it has so far.
• Lock time and replace-by-fee — the review shows whether the transaction can’t be mined before a block or date, and whether its fee can be raised later. An input that is time-locked (for example an inheritance or recovery path) gets a warning.
• Compare with the address you were given — each payment card has a box to paste or scan the address the recipient gave you. SafeKeep compares every character: “Identical”, or “Different address. Don’t sign” with the differences highlighted. You still tick the box yourself.
• Fees for older addresses — spending from legacy 1… addresses now shows the mining fee and fee rate instead of “unknown”. SafeKeep checks that the previous transaction a PSBT includes really is the one being spent. A PSBT that fails this check could hide part of the fee, so signing it is blocked.
• Type your passphrase twice — a typed BIP-39 passphrase must be typed again before the Dashboard applies it or the Output Descriptor tool uses it. A typo would open a different, empty wallet or hand your cosigners the wrong key. In multisig, Key 1 stays hidden until it’s confirmed. Passphrases loaded from the Passphrase Library don’t need retyping.
• Auto-Off — a third idle timer in Device Options powers SafeKeep off after a set number of idle minutes (default 30, 0 = stay on), with a 60-second warning. It also applies at the password prompt.
• Shamir recovery shows both readings — recovering SLIP-39 shares shows the wallet as made with SafeKeep and as made on a Trezor, each with its fingerprint and first address. Only Restore This Wallet (made with SafeKeep) saves anything, so a Trezor share set is never saved as the wrong wallet.
• Verify reads wallet exports — Check Descriptor also takes BlueWallet and Coldcard multisig setup files, BSMS records, Sparrow and Bitcoin Core descriptor files and single keys, converts them to a descriptor on the vault and shows the result before the check. A new Load File button reads them from the Transfer Drive.

v1.45 — October 15, 2026

Bring a wallet from another app into the Output Descriptor tool as a watch-only wallet, and a much tighter lock-down of SafeKeep OS itself.

• Import a watch-only wallet — paste or scan the output descriptor from another app (Sparrow, BlueWallet, Bitcoin Core), single-sig or multisig, including nested SegWit multisig sh(wsh(…)). On the Verify tab, Check Descriptor checks the checksum, refuses private keys, and shows the first receive and change addresses worked out from the descriptor. No seed is needed: without one the result is WATCH-ONLY, and with one loaded it still says MATCH or MISMATCH.
• Use it like your own — Use This Descriptor (watch-only) loads it into the tool, so the Receive panel (show and check addresses), the address list (.csv), the Bitcoin Core export, the QR code and Print PDF all work for it. The PDF leaves out the seed and passphrase rows. A descriptor without the …/<0;1>/* ending gets a warning and can’t be loaded.
• No terminal, no file manager — release builds no longer include them. The session runs as the system administrator (root), so either one was a way into the whole system.
• No network drivers — every network, Wi-Fi, Bluetooth, NFC, USB-network (including phone tethering) and USB-gadget driver is deleted from the image, and the build fails if one is left. Compilers, kernel headers and DKMS are removed after the build, so a new driver can’t be compiled on the flash drive.
• A network watchdog — if a network interface ever appears, SafeKeep switches it off and shows a red warning across the top of the app. It also warns if the firewall isn’t loaded.
• Preparing the computer — the flash drive controls the operating system, not the computer’s firmware, so unplug network cables and turn off Intel AMT/vPro and the wireless radios in the BIOS/UEFI. See Preparing the computer.

v1.44 — October 15, 2026

The multisig builder in the Output Descriptor tool can read a cosigner’s key straight from a Coldcard or Trezor One plugged into the vault by USB.

• Coldcard (USB) and Trezor (USB) — new buttons on each cosigner. With the device plugged into the offline SafeKeep computer, SafeKeep reads its master fingerprint and its BIP-48 multisig key for the chosen address type (m/48'/0'/0'/2' Native SegWit, /1' Nested SegWit, /0' Legacy) and fills in the cosigner. The key never passes through an online computer, which is especially useful for the Trezor One: it has no SD card or QR code output.
• Safe by design — a locked Trezor shows the same PIN grid as signing (only grid positions are sent, never the PIN). The import only reads: nothing is paired or saved, and the device isn’t asked to sign. Only the three multisig key paths can be read, and only mainnet keys are accepted.
• Tested so far — reading from a Coldcard has been tested. Reading from a Trezor One hasn’t been tried on a real device yet.
• Mix-ups caught early — a device already used for another key is flagged, and a cosigner key for a different address type than the one selected is refused, whether it was read by USB, pasted or scanned.
• Fix — with Multi-Sig selected, Seed Management’s address note now points to the Output Descriptor tool (it used the old name “The Script”).

v1.43 — October 13, 2026

The PSBT Signer now takes and gives files sent with The Courier, both ways. This is for wallets that only work with files, such as Trezor Suite: no Transfer Drive and no saving files on the vault.

• In — Scan Unsigned PSBT also accepts an unsigned .psbt file sent with The Courier, either from a computer’s screen or relayed by a phone. Frames are collected in any order, from any point in the loop. Each chunk is checksum-checked, and progress shows as “chunk 5 / 12”. The file is put back together in memory without being saved, and loads exactly like a file from the Transfer Drive. Binary .psbt, base64 and hex text files are accepted; any other file is refused with a clear message.
• Out — A new File (Courier) export format plays the signed PSBT as a Courier file loop named <name>-signed.psbt. The Courier on your online computer receives it and saves the file for your wallet to open. It’s chosen automatically when the PSBT arrived through The Courier. Wallets that scan QR codes, such as Sparrow, can still use UR or Standard.

v1.42 — October 12, 2026

A new Receive panel in the Output Descriptor tool. It works the address out from your descriptor on the offline flash drive, so malware on an online computer can’t swap it. The vault has no network access and can’t see which addresses have been used, so the intended workflow is: let your watch-only wallet (for example Sparrow on your own node) pick the next unused address, and use SafeKeep to check it.

• Show a receive address — pick an address by number with ← and →, starting at 0. The address is shown in groups of four so you can compare every character, with a QR code, a Copy button, and a label giving its number, path, wallet type and key fingerprints. It works for single-signature, Taproot and multisig wallets; a Silent Payment wallet shows its one fixed address.
• Check an address — paste or scan an address, and SafeKeep searches the wallet’s first 1,000 receive and change addresses. If it’s found, you see “✔ receive address #N” (a change address is flagged as one). If it isn’t, you get a warning not to send to it. It accepts bitcoin: links and uppercase addresses, and refuses addresses with a typo and testnet addresses.

v1.41 — October 12, 2026

• Export Addresses (.csv) — the Output Descriptor tool can save your wallet’s addresses as a list. Choose how many, from 1 to 10,000, always starting at the first address (index 0), and optionally the same number of change addresses. Each row has the index, chain, path and address, and no keys. Before saving, the first addresses are checked against the ones shown on screen. It works for single-signature, Taproot and multisig wallets, but not Silent Payments, which have one fixed address.
• Exports go to the Transfer Drive — the Output Descriptor tool’s exports (descriptor .txt, Bitcoin Core .json and the address .csv) now save to the Transfer Drive, ready to send from the Transfer Hub. Before, they were saved inside the encrypted vault, where the Transfer Hub couldn’t reach them. If the Transfer Drive isn’t available, the vault says so and saves nothing, and an earlier export is never overwritten.
• Multisig builder: no duplicate keys — the same key entered twice is now refused, and the message names the keys. This happens when one cosigner QR code is scanned for two keys, or a cosigner uses the same seed as Key 1. Before, the build reported success, but every verification address showed “error” and wallets like Sparrow read the descriptor as having fewer keys. If you built a multisig descriptor whose addresses showed “error”, build it again.
• Multisig builder: other improvements — a build whose addresses can’t be worked out now reports an error. Cosigner keys ending in /<0;1>/* or /0/* are accepted. Key 1 (this device) now shows its key origin and xpub, with a Copy button, and updates with the passphrase and address type.
• Transfer Hub — .csv files on the Transfer Drive are listed and can be sent.

v1.40 — October 11, 2026

• Courier Tool transmit controls — the controls for sending a file or text by QR now look and work like the online Courier Tool. Choose File (animated QR loop) or Text / password (single static QR) with two cards; the selected one is highlighted in orange. The file picker is a drop zone: click it to pick a file or drop one onto it, and it shows the file’s name and size, with an amber warning only for large files. Density and Speed are sliders that show their current value and what each end means.
• Nothing else changed — QR transfers work exactly as in v1.39, including between the vault and the online Courier Tool.

v1.39 — October 8, 2026

Better seed generation, a Wallet Record built from your descriptor, and an easier Passphrase Library.

v1.37 and v1.38 came out earlier the same day and are replaced by v1.39. If you installed either, update to v1.39.

• Verifiable Dice — a new Entropy Generator mode that uses physical dice only. The seed is the SHA-256 of your rolls (exactly 50 rolls for 12 words, 99 for 24), the same method SeedSigner and COLDCARD use, so the same rolls give the same words on either device and you can check one against the other. Mixed mode stays the default.
• Playing Cards — a new entropy source: shuffle a 52-card deck and enter it from the top. A full deck adds about 225 bits.
• An honest entropy meter — the meter now counts only the randomness you add: 0.5 bits per mouse sample, and 4 bits per camera frame taken only from the sensor-noise bits. Digital Dice are gone; they came from the same generator that is always mixed in, so they added no security.
• Wallet Record starts from the descriptor — use the wallet you just built in the Output Descriptor tool, or paste or scan the descriptor from any wallet app (animated QR codes work, such as Sparrow’s wallet export). The vault checks the descriptor’s checksum, refuses private keys, and works out the wallet type, M-of-N, script and first receiving address. If a key is missing its …/<0;1>/* path, it warns you instead of showing an address. You name each key (“Dave’s Coldcard — home safe”) and mark which ones need a passphrase. On the printout, keys appear by name only: for a key with a passphrase, the descriptor’s fingerprint belongs to the seed words plus the passphrase, so it isn’t printed as the key’s identity. You can add the seed’s own fingerprint to the name. The printed layout is otherwise unchanged.
• Wallet Record fixes — nested SegWit and legacy multisig wallets were recorded as single-signature. If you printed a record for one of these, print it again. Passphrases are also no longer saved in the browser.
• Passphrase Library — the generator opens right under the passphrase field. A generated passphrase no longer has to be re-typed: instead you check your written copy before saving. Changing the separator or capitalization keeps the same words, and a new Use this wallet now button switches to the passphrase wallet straight away.
• Passphrase backup fix — Print PDF could show the fingerprint of a different, active wallet. It now always matches the passphrase being printed. If you printed a passphrase backup while another passphrase wallet was active, print it again.
• Seed XOR — merging now shows the recovered fingerprint to compare with your share cards, and rejects a share entered twice or shares that cancel out to an empty seed. The recovery drill also works in preview mode.
• SeedQR — Standard SeedQR is now offered alongside Compact, with a note on which wallets can scan each.
• If you used v1.37 — a Wallet Record made by scanning a wallet QR code (for example a Sparrow multisig export) showed the wrong first receiving address. Discard any record printed that way and print a new one.

v1.36 — October 6, 2026

A release about verification: checking the computer, the dice, the transaction and the release itself.

• Start-up self-check — before you can enter anything, the vault runs published Bitcoin test vectors (seed words, key derivation, addresses for every wallet type, signatures) through its own code. If this computer gives a single wrong answer, the vault stops with a plain error screen instead of risking a wrong key or address.
• Safer signing — the vault now refuses any signature type that doesn’t cover the whole transaction (anything other than SIGHASH_ALL), including for Silent Payment inputs. Such signatures could let someone change where the funds go. The review screen explains the block, and Force Sign cannot override it.
• LifeHash icons — a small colored pattern drawn from the master fingerprint, on the Dashboard, the tool sidebar and the PSBT Signer. It matches the picture Sparrow Wallet shows for the same wallet.
• Dice fairness check — the Entropy Generator scores your physical dice rolls and, after 30 rolls, tells you whether the die looks fair, possibly biased or likely biased. It’s advice only and never blocks you.
• Bitcoin Core export — the Output Descriptor tool exports a watch-only import file for your own Bitcoin Core node, with the commands to load it.
• Verifiable releases — each app release now comes with a checksum, the maintainer’s signature, a GitHub build attestation and a Bitcoin timestamp, and the app is a reproducible build: rebuilding the release’s source gives byte-for-byte the same file. See how to verify.

v1.35 — October 5, 2026

• Fee rate on the review screen — the PSBT Signer used to show “? sat/vB” before signing. It now estimates the size the transaction will have once signed and shows a real fee rate. The high-fee guard is unchanged.

v1.34 — October 5, 2026

The largest update so far.

• Co-sign with a Coldcard or Trezor — pair a Coldcard or Trezor One in Device Options, and the PSBT Signer can ask it for a signature over USB. In a Temporary Session, Sign with Hardware Wallet reviews and signs a multisig transaction with hardware wallets alone, with no seed loaded.
• A real Lock — locking now closes the app, clears your keys from memory and closes the encrypted partition, returning to the password prompt. It can never power the machine off. Temporary Sessions gained Return to Master Vault.
• Settings survive a reboot — theme, display scale, sound and the idle timers are saved in your encrypted vault and restored at the next boot. Temporary Sessions never save them.
• Sound on more laptops — at boot the system unmutes the sound card and sends audio to a USB sound device if one is plugged in, otherwise to the built-in speakers instead of HDMI. Nothing network-related was added.
• Automatic Transfer Drive — the Transfer Drive mounts by itself, with no buttons or permission prompts.
• Change-hijack protection — a full review of the wallet’s cryptography against official test vectors found and closed ways a malicious coordinator could disguise a payment as change.
• Build it yourself — anyone with an x86-64 Linux machine can build the USB image from a fresh clone. See Build It Yourself.
• A refreshed look — new fonts and icons, tools grouped by purpose, and seed words blurred until you hover over them.