Repository navigation
SafeKeepVault v1.63
Release Date: November 7, 2026
Build: v1.63 · build 501 · 620fea9 · 2026-11-07
Get your SeedQR onto paper or steel without a computer you don't trust: trace it through the template on the screen, copy it square by square, or print it on a laser printer connected by USB. Plus a Screen Brightness setting that works on any screen. Earlier changes are in the v1.62 release notes.
✏️ Draw or Print my SeedQR
After you generate a SeedQR, the SeedQR tool offers three ways to copy it:
- Trace It on the Screen: the code fills a white screen at the real size of the blank templates from Print QR at safekeepbitcoin.com (85.68 mm for 21×21, 87.88 mm for 25×25). Lay the printed template on the screen and fill in every square that shows dark through the paper. Fine-tune the Size with the slider, the number box, or the arrow and + / − keys (hold Shift for bigger steps), then press Remember as Default so it opens at that size next time. It opens at full brightness, and the ☀ slider dims it.
- Copy It Square by Square: one 7×7 block at a time, numbered as the template is, with the dark squares of each row listed. It also suits punching steel or placing tiles.
- Print It on a USB Printer: see below.
Each ends with Scan to Verify, which checks your copy with the camera.
🖨️ Print a SeedQR on a USB laser printer
SafeKeep still has no print system and no printer drivers. It draws the page itself in PCL, the printer language most laser printers understand, and sends it straight to the printer over USB. It never prints over a network. Only the printer part of a device is used, so a multifunction printer's scanner stays off.
- Any size from 10 to 150 mm, with a Template size button. Small codes scan fine: on a Samsung Xpress M2070, a 14 mm code was read by a laptop camera.
- The seed fingerprint under the code, if you want it.
- A preview of the page, and the printer's name before you print.
- Safety notes: use your own printer by USB, turn its Wi-Fi or network off, take the page, and switch the printer off afterwards, because it keeps the page in its memory until then.
- If the vault shouldn't hold this seed (a vault set not to keep the seed, or a SeedQR that isn't your vault's seed), SafeKeep explains that printing briefly saves it in the encrypted vault, and suggests printing from a Temporary Session instead.
🔆 Screen Brightness
Device Options → Screen Brightness dims the picture from 30% to 100% on any screen: laptop, desktop monitor, Mac or PC. 100% is the screen's own brightness. The setting is saved in your vault. On many laptops the keyboard's brightness keys now work too.
⌨️ Typing a seed into the SeedQR tool
Clear & Enter Different Seed now uses the same word boxes as the rest of SafeKeep: suggestions as you type, Enter or Tab to take one, and pasting a whole phrase fills every box.
🔄 Update in place from v1.47 or later
- Copy
SafeKeep-Update-v1.63.taronto your flash drive'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.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.63.zip):
- Download
SafeKeep-Release-v1.63.zip,SHA256SUMS.txtandSHA256SUMS.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:6d749b7c0e5a511492dbc7e82483fe7b6971c96387da25baad2890a963d43f8e SafeKeep-Release-v1.63.img
The update file (SafeKeep-Update-v1.63.tar) carries its own signature, which the flash drive 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: 4d4a68c1a58d789aca5bf08512e72744099d2fc4ab24cd476feb458797cf66c5 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.