Skip to content

SafeKeepVault v1.46

Choose a tag to compare

@github-actions github-actions released this 17 Oct 20:08
· 289 commits to main since this release
a24a498

Replaced by v1.47.

Release Date: October 17, 2026

Build: v1.46 · build 272 · a24a498 · 2026-10-17

v1.46 lets the PSBT Signer check every transaction against the wallets you own and show exactly what it spends, and a mistyped passphrase can no longer slip through. Earlier changes are in the v1.45 release notes.

👛 Saved wallets
In the Output Descriptor tool, give a wallet a name and click Save Wallet. Single-sig and multisig work, and so does a watch-only wallet imported from another app. The vault keeps your saved wallets in its encrypted partition, and lists them at the top of the tool, each with a Remove button.
The PSBT Signer then names the saved wallet a transaction spends from. It warns you if an input matches none of your saved wallets.
Change that you no longer have to check by hand: if a change output is one of your saved wallet's own addresses, it is marked verified, even when the PSBT leaves out the multisig details.
🔍 PSBT Signer: what the transaction does
Summary: how much you are sending, the mining fee, the total leaving your wallet, and the change coming back.
Spending N inputs: each input's amount, address and saved wallet, and for multisig, how many signatures it has so far.
Lock time and replace-by-fee: whether the transaction can't be mined before a certain block or date, and whether its fee can be raised later. A time-locked input, such as an inheritance or recovery path, gets a warning.
Compare with the address you were given: on each destination card, paste or scan the address the recipient gave you. SafeKeep compares every character and shows Identical, or "Different address. Don't sign" with the differences highlighted. It never ticks the verification box for you.
Fees for older addresses: when a transaction spends from legacy 1… addresses, the vault checks that the previous transaction included in the PSBT is really the one being spent, and then shows the fee. A forged previous transaction could hide a much higher fee, so signing 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. Otherwise a typo would open a different, empty wallet, or hand your cosigners the wrong key.
In multisig, Key 1 stays hidden until the passphrase is confirmed.
A passphrase loaded from the Passphrase Library doesn'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). A 60-second warning comes first.
It also applies at the password prompt.
🧩 Shamir recovery shows both readings
Recovering SLIP-39 shares now shows two readings, each with its fingerprint and first address: one for shares made with SafeKeep, and one for shares made on a Trezor or another SLIP-39 wallet.
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
On the Output Descriptor Verify tab, Check Descriptor also accepts:
BlueWallet and Coldcard multisig setup files;
BSMS records;
Sparrow and Bitcoin Core descriptor files;
single keys.
It 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.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.46.zip):

Download SafeKeep-Release-v1.46.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: fd85dabd3a073165e8b6785ccb156625ccd277a27eb51fcef04f6a932ce4a3ac SafeKeep-Release-v1.46.img
The app on its own (boot.html; its checksum file is SHA256SUMS, without .txt):

sha256sum -c SHA256SUMS
gh attestation verify boot.html -R Pasalon0404/SafeKeepVault
gpg --verify SHA256SUMS.asc SHA256SUMS
Expected: 6538d8ea5b11651851737ca69770e85026d47f86822040f2df3402ba10f3071e boot.html

The boot.html inside the USB image is byte-for-byte the same file as this release's boot.html. See VERIFYING.md for every check.