Repository navigation
SafeKeepVault v1.44
Replaced by v1.45.
Release Date: October 15, 2026
Build: v1.44 · build 239 · 89c278e · 2026-10-15
v1.44 lets the Output Descriptor tool read a multisig cosigner's key straight from a Coldcard or Trezor plugged into the SafeKeep computer. Earlier changes are in the v1.43 release notes.
🔐 Output Descriptor: cosigner keys from a hardware wallet
Coldcard (USB) and Trezor (USB) buttons on each cosigner in the multisig builder.
The device is plugged into the offline SafeKeep computer. SafeKeep reads its master fingerprint and its multisig key for the chosen address type (m/48'/0'/0'/2' for Native SegWit, /1' for Nested SegWit, /0' for Legacy) and fills in the cosigner.
The key never passes through an online computer. That's especially useful for the Trezor One, which has no SD card or QR code output.
A locked Trezor shows the same PIN grid as signing; only grid positions are sent, never your PIN.
Read-only: nothing is paired or saved, and the device isn't asked to sign anything.
Only the three multisig key paths can be read, and only mainnet keys are accepted. A Coldcard set to Testnet gets a clear message.
Tested with a Coldcard over USB. Trezor One support uses the same tested request path as Trezor signing, but hasn't yet been tried with this new request on a real device.
Mix-ups caught early:
If a device's fingerprint is already used by Key 1 or another cosigner, you're told straight away.
Building now refuses a cosigner key from a different address type than the one selected, for example a Native SegWit key (…/2') in a Nested SegWit wallet. This applies to pasted and scanned keys too. Before, such a key was accepted and gave addresses no other wallet would match.
🛠️ Fixes
Seed Management: with Multi-Sig selected, the address note pointed to "The Script tool", the old name of the Output Descriptor tool. It now names the Output Descriptor tool.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.44.zip):
Download SafeKeep-Release-v1.44.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: eddf822f6172b14c5124c0209fe5c59786c0ece103f21662916215bca27feb00 SafeKeep-Release-v1.44.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: 71a4b333eee15cfb1dcc8cfb02fa212c73a054067e48a73d6a9395c6c4b39985 boot.html
The boot.html inside the USB image is byte-for-byte this release's boot.html. See VERIFYING.md for every check.