Seedsigner Raspberry Pi DIY Bitcoin Hardware Wallet Guide

If you want a Bitcoin signer that does not ship as a sealed retail device, SeedSigner is worth looking at. It is built from generally available Raspberry Pi parts, runs on the Raspberry Pi software stack, and uses an air-gapped workflow for signing transactions. You can build it with a Raspberry Pi Zero, an older Pi B or A, or even a newer Pi such as a Pi 4, depending on what you have lying around.

Watch the video for the full demonstration. This article is the written version: parts, verification, flashing, bench testing, assembly, and basic use with BlueWallet.

SeedSigner build laid out before casing
A Raspberry Pi Zero SeedSigner build with camera, display hat, buttons, and USB-C power

Build your own hardware wallet

Kits, smartcard hats, cases and parts for SeedSigner, ShieldSigner, Specter DIY and Satochip builds, tested with the firmware shown in these videos and shipped from Canada.

What SeedSigner is good for

SeedSigner is not a normal “plug it in and forget it” hardware wallet. It is a DIY air-gapped signing device. That means you are building the hardware yourself from off-the-shelf components, then using it to sign Bitcoin transactions without keeping your private keys connected to an online machine.

It is especially useful if:

  • You do not want the privacy risks that can come with ordering a retail hardware wallet.
  • You want more control over the software image you flash.
  • You are comfortable with Raspberry Pi projects.
  • You want a stateless signer, meaning it does not retain seeds or private keys after reset.

That last point is important. SeedSigner is stateless. It does not keep your seed or private keys stored on the device between sessions. If you power it off and restart it, it expects you to re-enter or rescan the seed material you want to use for that session. That makes it attractive for long-term storage workflows, but it also means you need a good backup strategy.

Hardware options and kit parts

You can gather the parts yourself, 3D print your own case, run without a case, or order a kit if one is available in your region. In the video, the kit included most of the components plus an OpenPill-style case, instructions, and a SeedSigner sticker. You still need to provide your own microSD card; anything over 4 GB will do.

Common hardware choices include:

If you are using a Raspberry Pi Zero, make sure it has GPIO headers attached. Some Raspberry Pi Zero 1.3 boards come with headers pre-soldered, which saves time. If yours does not, you can solder them yourself or use a suitable header jig if that is more comfortable for you.

For the case, I used a 3D printed enclosure in the video. You can also look at the 3D Printed Case for Stock SeedSigner if you want a ready-made option that matches the stock-style build.

Modifying the Waveshare hat for older Pi GPIO layouts

If you use an older Raspberry Pi, the GPIO header layout may not match what the display hat expects for the buttons. The screen pins may be fine, but the button pins may need to be remapped.

In the video, I soldered thin wires onto the side of the hat to relocate the button pins. This is a small modification, but it needs care. You also need an adjusted version of the SeedSigner software for that wiring change. The presenter mentioned pushing the adjustment to GitHub and bringing a pull request into the main SeedSigner repository.

Soldering wires to remap display hat buttons
Thin jumper wires soldered to re-route button pins on an older Pi-compatible display setup

If you are using a standard Raspberry Pi with the standard 40-pin GPIO header and standard SeedSigner software, this step may not apply. The important thing is that your hardware wiring matches the software pin mapping before you seal everything into a case.

Downloading the SeedSigner image and tools

Before building anything physical, get the software onto the microSD card. You need:

  1. A computer with a working microSD reader.
  2. Balena Etcher or another reliable flashing tool.
  3. The SeedSigner image file for your target hardware.
  4. The verification files from the release page.
  5. The developer GPG public key.

The SeedSigner software page gives you download options, but I would not rely only on a browser-based verification if security matters to you. If your system is compromised or you land on a malicious version of the website, a simple web-page check can be faked. You want to verify against the developer’s GPG signature and checksums as properly as you reasonably can.

SeedSigner software download page
Browser view of the SeedSigner software download area

Verifying the image with GPG and SHA-256

This is one of the most important parts of the build. You are flashing a full operating system onto a microSD card, so you want confidence that the file has not been tampered with.

The basic verification flow is:

  1. Download the SeedSigner image from the official release page.
  2. Download the related signature and checksum files.
  3. Download the SeedSigner developer GPG public key.
  4. Install a GPG tool on your computer, such as Gpg4win on Windows.
  5. Import the developer public key.
  6. Check that the imported key matches the published fingerprint.
  7. Verify the signature file against the image or checksum material.
  8. Generate or compare the SHA-256 checksum of the image file.
  9. Confirm your local checksum matches the developer-provided checksum.

In the video, this was done on Windows using GpgEX options and a checksum tool. The point is not the exact menu clicks; the point is that you are comparing locally computed values against published developer values.

Comparing SHA-256 checksum with signed message
File Explorer checksum workflow next to Notepad++ showing the signed SHA-256 value

If this feels like more work than flashing an Electrum image or a retail wallet firmware, that is expected. You are building your own device from components, so you should take the extra step of verifying what you are installing.

Flashing the microSD card with Balena Etcher

Once the image is verified, flash it to the microSD card.

  1. Insert the microSD card into a USB reader.
  2. Open Balena Etcher.
  3. Choose “Flash from file.”
  4. Select the SeedSigner image file.
  5. Select the correct target device.
  6. Flash the image.
  7. Wait for completion before removing the card.

Be careful with the target selection. If you have other USB drives, SD cards, or memory sticks plugged in, unplug them if possible. You do not want to accidentally wipe something important because a reader is showing up as a similar-sized removable device.

Balena Etcher selecting the microSD target
Selecting the USB mass storage device containing the microSD card

If flashing fails on Windows, it can be worth rebooting and trying again. Flashing tools and SD readers can behave oddly, especially with cheap generic readers or cards that have been used before.

Connecting the camera and debugging the display

After flashing, insert the microSD card into the Raspberry Pi and connect the camera to the CSI port. The exact location depends on your Pi model. On a Pi Zero, it is near the edge of the board. On larger Pis, look for the CSI port, often near the Ethernet connector or another similar-looking socket.

To fit the camera:

  1. Release the retainer clip.
  2. Insert the ribbon cable with the contacts facing the correct direction.
  3. Slide it in fully.
  4. Secure the side clips.
  5. Make sure nothing is pinched.

Do not skip bench testing. In the video, one camera module from the kit failed, so I swapped it for another compatible camera. The form factor and connector were the same, but the replacement worked. That is exactly why you test before putting everything into a case.

For bench testing, connect:

  • A monitor or screen using the appropriate HDMI adapter.
  • A keyboard or wireless receiver in a USB data port.
  • Power to the correct power port.

On a Pi Zero, use the middle micro USB port for data and the edge port for power. If you plug data into the wrong port, things will not work as expected.

Camera test command on Raspberry Pi terminal
Terminal showing raspistill camera test with physical Pi and camera attached

Pi login, keyboard layout, and camera test

When the Pi boots, you should see a standard Linux boot sequence. SeedSigner runs on top of a full Raspberry Pi OS environment. You can log in using the default username and password shown in the SeedSigner installation documentation.

One common gotcha is keyboard layout. Raspberry Pi systems often ship with a UK layout by default, while many users have US keyboards. This can make special characters appear wrong. In the video, typing the password on a US keyboard produced unexpected characters because of the layout mismatch. The fix was to enter the intended password using the correct physical keys for the active layout.

After logging in, test the camera with raspistill -v. If the command reports that the camera is detected and running, your camera connection is likely good. Then test the SeedSigner IO screen so you can confirm:

  • The display works.
  • The buttons work.
  • The camera captures images.
  • The system behaves before you assemble it into a case.

This step saves time later. If something is loose, miswired, or faulty, it is much easier to fix on the bench than inside an enclosure.

Assembling SeedSigner in the OpenPill case

Once everything works on the bench, power off properly and wait for the status light to stop before unplugging. Then assemble the device into its case.

  1. Seat the camera module under its retaining clips.
  2. Tuck excess ribbon cable carefully without crushing it.
  3. Keep the microSD slot clear.
  4. Align the Raspberry Pi with the display hat pins.
  5. Press down firmly until the board seats and retains.
  6. Reinsert the microSD card.
  7. Test the assembled unit before finalizing.

The case helps align the parts, but you still need to make sure the ribbon cable is not blocking the SD slot or pinched in a way that could damage it. In the video, I tested the device again after reinserting the SD card into the enclosure and confirmed the camera still worked.

Pressing the Raspberry Pi into the 3D printed case
Hands pressing the Pi board into its retaining clips in a dark blue case

After that, attach the display hat or top section so the unit is fully assembled. Once it is closed up, you should have a compact device with a small screen, buttons, and camera access.

Generating a seed and verifying backup

With the hardware working, SeedSigner can create or import seeds. You can:

  • Scan a SeedQR.
  • Enter a 12 or 24 word mnemonic.
  • Create a new seed using entropy from the camera or dice rolls.

In the video, I created a new seed using the camera method and chose a 12-word seed for speed. For real long-term storage, many people prefer 24 words because of the stronger checksum and larger key space. The exact choice is yours, but do not skip backup verification.

When SeedSigner gives you an option to verify the generated seed, use it. Your seed is your wallet. If the backup does not match, you need to know before you send funds into that address.

After generating the seed, write down the mnemonic properly and store it safely. You should also note the seed fingerprint if useful. The fingerprint helps you identify which seed is loaded in future sessions, but it is not a replacement for the full backup.

Using SeedSigner with BlueWallet xpub

SeedSigner works well with external wallets such as BlueWallet. The workflow uses an extended public key, or xpub, so your phone wallet can watch addresses without knowing your private keys.

  1. Open BlueWallet on iOS or Android.
  2. Add a new wallet and choose import.
  3. On SeedSigner, export the xpub for single-sig native SegWit.
  4. Select the destination app option if prompted.
  5. Scan the xpub QR code into BlueWallet.
  6. Confirm that BlueWallet shows it as a watch-only wallet.
BlueWallet importing xpub from SeedSigner
BlueWallet watch-only import next to SeedSigner displaying an xpub QR

From there, you can receive Bitcoin normally in BlueWallet. But before sending funds to a new address, verify the receive address on SeedSigner. Scan the receive address QR code from BlueWallet into SeedSigner and confirm that it belongs to your seed. This gives you an extra layer of trust: you are not relying only on the phone app’s display.

Sending funds via PSBT signing

To send Bitcoin, use a partially signed Bitcoin transaction, or PSBT. The idea is simple: BlueWallet creates the unsigned transaction, SeedSigner signs it offline, then BlueWallet broadcasts the signed transaction.

  1. In BlueWallet, start a transaction to the destination address.
  2. Enable offline signing if prompted.
  3. Scan the destination address from your trusted source.
  4. Review the amount and fees.
  5. Generate the unsigned PSBT QR code in BlueWallet.
  6. On SeedSigner, scan that animated QR code.
  7. Select the seed you want to sign with.
  8. Review the transaction details on SeedSigner.
  9. Approve the PSBT.
  10. Scan the signed PSBT back into BlueWallet.
  11. Send or broadcast from BlueWallet.
SeedSigner showing change verification for a PSBT
Verification screen showing sats going to your change address

The review screens matter. You want to confirm the destination, amount, fees, and change before approving anything. If something looks wrong, do not sign it. Cancel, recheck the address, and start again if needed.

Creating and restoring SeedQR backups

Because SeedSigner is stateless, you may want a convenient way to reload your seed without typing words every time. SeedQR lets you export the seed as a QR-style backup that can be transcribed onto paper and rescanned later.

The process is:

  1. Load or create the seed in SeedSigner.
  2. Export it as a SeedQR.
  3. Use the official template from the SeedSigner GitHub repository.
  4. Mark the required dots on the printed sheet.
  5. Scan the completed SeedQR back into SeedSigner to confirm it works.
Printing and filling in a SeedQR backup
SeedQR display next to a paper template with corner finder patterns

In the video, the hand-drawn dots were not perfect, but the redundancy still allowed it to scan correctly. That is useful for quick reloading, especially if you transact more often and do not want to type a long mnemonic every time.

However, SeedQR should not replace your written 12 or 24 word backup. A printed SeedQR can be convenient, but your primary recovery material should still be the standard mnemonic phrase stored safely offline. If you lose both, you are in trouble.

Final thoughts

SeedSigner is not the easiest Bitcoin wallet to pick up and use. It asks for more technical comfort: verifying images, flashing SD cards, testing cameras, checking keyboard layouts, and assembling hardware before sealing it into a case. But that extra work gives you a lot of control.

It is a good fit if you want an air-gapped signer built from Raspberry Pi components, or if you simply enjoy building something useful with open hardware. Combined with a watch-only wallet such as BlueWallet, address verification, PSBT signing, and proper seed backups, it can be a practical tool for people who care about privacy and self-custody.

The biggest advice is this: test everything before you put it in the case, verify your backup before you fund the wallet, and never rely on one backup method alone.

Questions from viewers

Common questions from the comments on this video, with my answers.

Can I use a Raspberry Pi Zero 2W for SeedSigner, and do I need to physically remove the Wi-Fi and Bluetooth chips?

You can use a Pi Zero 2W. While the official recommendation is to remove the wireless components for maximum security, they are disabled in the software. Depending on your specific situation, you may not need to mess with the hardware. If you do choose to remove them, there are community instructions available online showing which parts to take out.

I am having trouble verifying the SeedSigner image with Kleopatra; it says the certificate could not be certified. How do I fix this?

This error occurs because you haven't imported and certified the SeedSigner GPG key. You need to import the correct certificate into your keyring and then certify it so that Kleopatra recognizes the signature as valid.

Is it possible to save my SeedQR backup to an encrypted USB stick instead of printing it?

Storing digital backups is generally considered a bad idea due to the risk of malware or theft. However, nothing stops you from taking a photo of the QR code and encrypting that image file if you prefer a digital format over paper.

If I have lost some words from my seed phrase (for example, two out of twelve), can I recover the wallet?

Yes, if you have a known address from the wallet, missing a few words is often solvable. You can use a tool like BTCRecover with default settings to brute-force the missing words. You don't need to download the entire blockchain; just having the address or an address database is sufficient for the tool to work.

Where can I find affordable Raspberry Pi hardware if the Zero models are out of stock?

When the Pi Zero or Zero 2 is unavailable, it often makes more sense to purchase a Raspberry Pi 4, which is widely supported by SeedSigner. You can check sites like rpilocator.com to find reasonable pricing options for these boards. (Apps and tools change, so check the current version if something looks different.)

Build your own hardware wallet

Kits, smartcard hats, cases and parts for SeedSigner, ShieldSigner, Specter DIY and Satochip builds, tested with the firmware shown in these videos and shipped from Canada.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides