Download¶
The fastest way to run PiWalletSV is to flash the prebuilt SD-card image onto a microSD and boot. The image is a sealed appliance: it boots straight into the bonnet UI, has no SSH or Wi-Fi, and runs PiWalletSV as the only foreground task on the device.
Canonical host: signed firmware, checksums, and release notes live on GitHub Releases — that is the single source of truth. piwalletsv.com and dev.piwalletsv.com only link here; they do not republish version numbers or hashes.
Get the latest image
Open GitHub Releases,
pick the newest release that matches your board, and download the assets
listed there (.img.xz, .asc, SHA256SUMS). Software is beta —
fully functional with no currently known issues; bug fixes and notices
are posted on @PiWalletSV.
Which image file?¶
Each release filename includes a board slug for the Raspberry Pi model (processor tier — not Wi‑Fi vs non‑W):
| Board slug | Raspberry Pi hardware |
|---|---|
| pi0 | Pi Zero v1.3, Pi Zero W, Pi Zero WH |
| pi02w | Pi Zero 2 W, Pi 3 Model B (future) |
| pi2 | Pi 2 Model B (future) |
| pi4 | Pi 4 Model B, Pi 400 (future) |
For round‑1 kits use pi0. Exact filenames and tags are on the
GitHub release page for that version.
Machine-readable history (optional):
releases/releases.json
in the source repo.
Verify before you flash¶
The signing device's whole security claim is “keys never leave the device.” That claim collapses if the firmware running on the device is not the one we built. Verify the signature before you flash.
# One-time: import the release key (fingerprint in docs/security.md).
gpg --keyserver hkps://keys.openpgp.org --recv-keys 9E048B6E7F54C49DE2D5AEB5DA261F4F2B0CA281
# Verify the image (use the filenames from the GitHub release assets).
gpg --verify piwalletsv-<VERSION>-<BOARD>[-maturity].img.xz.asc \
piwalletsv-<VERSION>-<BOARD>[-maturity].img.xz
# Cross-check the SHA-256 against SHA256SUMS from that same release.
shasum -a 256 piwalletsv-<VERSION>-<BOARD>[-maturity].img.xz
A successful verification ends with “Good signature” against the
release-key fingerprint in docs/security.md.
Do not flash an unverified image.
Flash the image¶
Step-by-step flashing
Flash and first run § Flash the image
covers Windows, macOS, and Linux (Raspberry Pi Imager or dd).
You need a USB microSD reader/writer on your computer. PiWalletSV kits include a microSD and SD adapter when a full kit is offered; they do not include a USB reader.
Next steps¶
Once the image is verified and flashed:
- Full kit with factory-flashed card? The assembled kit was booted for factory diagnostics, so its card will not byte-match the pristine image checksum. Before you fund, strongly recommend re-flashing a signed, checksum-verified release from GitHub Releases — User manual § Verify your SD card.
- Follow Flash and first run for disclaimer, vault PIN, wallet creation, airgap check, and a TESTNET smoke test.
- Routine use: User manual (USB backup, Upgrade your device, Airgap status).
Building from source¶
Need a custom tree or no GitHub asset yet? Flash Raspberry Pi OS Lite
32-bit, run
deploy/provision-pi.sh,
and capture your own image — see
Build & deploy and the operator notes in
docs/includes/image-release-operator.md.