Repository navigation
SafeKeepVault v1.41
Replaced by v1.42.
Release Date: October 12, 2026
Build: v1.41 · build 223 · a1431b9 · 2026-10-12
v1.41 adds an address export to the Output Descriptor tool and fixes how its exports are saved and how multisig wallets are built. Earlier changes are in the v1.40 and v1.38 release notes.
🧾 Output Descriptor
Export Addresses (.csv): a new button next to the other exports saves the wallet's addresses as a spreadsheet-ready list.
Choose how many, from 1 to 10,000. The list always starts at the wallet's first address (index 0).
Optionally add the same number of change addresses.
Each row has the index, chain, path and address. The file holds addresses only, with no keys or descriptor.
Before saving, the first addresses are checked against the ones shown on screen. If any differ, nothing is saved.
Works for single-sig, Taproot and multisig wallets. It isn't offered for Silent Payments, which have one fixed address.
Exports go to the Transfer Drive: Export Descriptor (.txt), Export for Bitcoin Core (.json) and the new address export 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 mounted, the app asks you to mount it rather than saving anywhere else.
An earlier export with the same name is kept; the new one gets a -1, -2… suffix.
🔐 Multisig builder
Duplicate keys are refused: if the same key is entered twice, the app now stops and names the keys involved. This happens when one cosigner's QR code is scanned for two keys, or when a cosigner uses the same seed as Key 1.
Before, it reported success, but the descriptor repeated a key, every verification address showed "error", and wallets such as Sparrow read it as fewer keys.
If you built a multisig descriptor whose addresses showed "error", don't use it. Build it again.
No success without addresses: if an address can't be worked out from the keys, the build reports an error instead of success.
More cosigner formats: keys that end in /<0;1>/* or /0/*, as some wallets export them, are now accepted.
Key 1 shows your key: Key 1 (this device) now shows its key origin and xpub, for example [73c5da0a/48'/0'/0'/2']xpub…, with a Copy button, so you can give it to the other cosigners' wallets.
It updates when you change the passphrase or address type.
It's exactly the key used in the descriptor.
📡 Transfer Hub
.csv files on the Transfer Drive are now listed and can be sent.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.41.zip):
Download SafeKeep-Release-v1.41.zip, SHA256SUMS.txt and SHA256SUMS.txt.asc.
Verify the signature:
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
Expect a good signature from Anton anton@safekeepbitcoin.com, key fingerprint A333 EB82 6F70 A79A 736F 0994 8EA7 DD8C EDBA 86C2.
Unzip, then check the image hash:
shasum -a 256 -c SHA256SUMS.txt
Expected: c30c42bf6df5754f83b13f556550629db7bbfa6511796e5fe4b0aa1c11fd322a SafeKeep-Release-v1.41.img
The app on its own (boot.html, which uses SHA256SUMS without .txt):
sha256sum -c SHA256SUMS
gh attestation verify boot.html -R Pasalon0404/SafeKeepVault
gpg --verify SHA256SUMS.asc SHA256SUMS
Expected: 995e5e2d4d2976ad615fb430b2b1556aef6c4018905d7e5d9d4b6dc2911fed8b boot.html
The boot.html inside the USB image is byte-for-byte this release's boot.html. See VERIFYING.md for every check.