Repository navigation
SafeKeepVault v1.45
Replaced by v1.46.
Release Date: October 15, 2026
Build: v1.45 · build 245 · 7018604 · 2026-10-15
v1.45 lets you use a wallet built in another app as a watch-only wallet, and locks the SafeKeep operating system down further. Earlier changes are in the v1.44 release notes.
👁️ Output Descriptor: import a wallet from another app
Use a descriptor from Sparrow, BlueWallet or Bitcoin Core as a watch-only wallet. Single-sig and multisig both work, including nested SegWit multisig (sh(wsh(…))).
Paste or scan the descriptor on the Verify tab and press Check Descriptor. SafeKeep checks the checksum, refuses private keys, and shows the first receive and change addresses, worked out from the descriptor itself.
No seed needed. Without a seed loaded, the result is WATCH-ONLY. With one loaded, it still says MATCH or MISMATCH, depending on whether that seed can sign for the wallet.
Use This Descriptor (watch-only) loads it into the tool. The Receive panel (show and check addresses), the address CSV export, the Bitcoin Core export, the QR code and Print PDF then work for it. The printed PDF leaves out the seed and passphrase rows.
A descriptor without the …/<0;1>/* ending gets a warning and can't be loaded, because its addresses can't be worked out.
🔒 SafeKeep OS: tighter lock-down
No terminal and no file manager. Ctrl+Alt+T and the Terminal and File Explorer menu items are gone. The session runs as root, so either one was a root shell from which the network lock-down could be undone by hand. The app's Transfer Hub lists the Transfer Drive.
No network drivers at all. Every network, Wi-Fi, Bluetooth, NFC, USB-network and USB-gadget driver is now deleted from the image, including iPhone and Android USB tethering. Before, only the common chips were removed by name. The build stops if a network driver is left, or if a driver the stick needs is missing.
No compilers. gcc, binutils, kernel headers and DKMS are removed once the camera driver is built, so a new driver can't be compiled on the stick.
Network watchdog. If a network interface ever appears, SafeKeep switches it off within a few seconds and shows a red warning across the top of every screen. The same warning appears if the firewall isn't loaded.
Preparing the computer: the README now recommends unplugging any network cable, and turning off Intel AMT/vPro and the wireless radios in the BIOS/UEFI. AMT runs in the computer's management chip, outside any operating system.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.45.zip):
Download SafeKeep-Release-v1.45.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: 643e44634e10f9c0c5f9d35d6e3a4408e11567a6aef6ba42fb57ccedad825364 SafeKeep-Release-v1.45.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: 9eab8eee5809d205096abbfcd542157a07bc9808d98775d35a394acae62e5a64 boot.html
The boot.html inside the USB image is byte-for-byte this release's boot.html. See VERIFYING.md for every check.