Repository navigation
SafeKeepVault v1.57
Release Date: November 1, 2026
Build: v1.57 · build 429 · b8e931d · 2026-11-01
A new look for SafeKeepVault, with two new guided tasks: show a receive address, and connect a wallet app. Earlier changes are in the v1.56 release notes.
🏠 A new Dashboard
Your wallet at a glance: the wallet card shows the loaded seed's LifeHash, fingerprint and nickname.
Health: a short checklist: the last backup, whether the Transfer Drive is ready, and the SafeKeep version. It now remembers when this stick last made a backup, so the date stays even after you move the .7z off the stick.
Task tiles: Sign, Show an address, Back up, Connect a wallet app and Transfer. Below them are your Saved wallets, then All tools.
One status badge: the status lights are now a single "Offline · Protected" badge. Click it to see each light.
👋 A clearer welcome
A new stick offers Create a new wallet or I already have a backup. The second option lists each way to restore.
📥 Show an address
Show the next receive address of this seed's wallets, or of a saved wallet, as a large QR code. Press New address to move to the next one. SafeKeep remembers, on the stick, which address each wallet is up to, so after a reboot it picks up where you left off.
🔗 Connect a wallet app
Step-by-step setup for Blue Wallet, Electrum, Nunchuk, Sparrow and Specter, plus Another wallet for any other app. SafeKeep opens Seed Management with the right export format for your app (an animated QR for Nunchuk, a file for Specter), and tells you what to tap in the app.
🎨 Tool screens
Tool headers are shorter, with "More about this tool" for the full description.
PSBT signing steps are numbered.
Corners are rounded throughout, and Device Options has been tidied.
🔄 Update in place from v1.47 or later
Copy SafeKeep-Update-v1.57.tar onto your stick's TRANSFER drive.
Boot SafeKeep and unlock your vault.
Open Device Options → Update SafeKeep → Check for update, then Install and Restart now.
Your vault, your vault password and your Transfer Drive are not touched. Before installing, SafeKeep shows the app's SHA-256: it should match the boot.html line of this release's SHA256SUMS. Health shows a backup date only for backups made after updating, or for a dated .7z still on the drive.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.57.zip):
Download SafeKeep-Release-v1.57.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: 944ab67a67d30f2fb1f9992e10b284918a6285a8143b4fe39a7453aeaf18ec12 SafeKeep-Release-v1.57.img
The update file (SafeKeep-Update-v1.57.tar) carries its own signature, which the stick checks before installing.
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: 3677a914197e99ccc0f5962a8926ba58737c967b67bd861dee4648c36dd02114 boot.html
The boot.html inside the USB image and the update file is byte-for-byte this release's boot.html. See VERIFYING.md for every check.