
If you want a Bitcoin hardware wallet that is cheap, open source, air-gapped and easy to build yourself, SeedSigner is one of my favourite tools. But I have always thought it gets even better when you add a secure element for seed storage. That is where SeedKeeper comes in.
In this guide, I will walk through how to use the SeedSigner + Smartcard Kit with a custom SEC1210-based Raspberry Pi smartcard hat. You can load BIP39 seeds and passphrases from a SeedKeeper or compatible JavaCard, flash applets to cards, assemble the hardware without getting stuck on fake modules, and use some extra features in my SeedSigner fork such as Krux encrypted seed QR codes and GPG signature verification.
Watch the video if you want to see the full demo. This article is a standalone written version so you can follow along later, search for specific steps, or keep it as a reference while building your own device.
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.
Why combine SeedSigner with a smartcard?
SeedSigner is already a strong self-custody tool because it is open source, air-gapped and QR-based. You do not need to connect it directly to the internet in normal operation. But one common request I get is: “Can I store my BIP39 seed on a secure element instead of paper?”
That is where SeedKeeper fits nicely. A SeedKeeper card can hold seeds, passphrases and multi-seed descriptors. With the smartcard hat, your SeedSigner can talk to that card through a contact reader. You can load a seed from the card into SeedSigner when you want to use it, or back up a seed onto the card from SeedSigner.
The practical benefit is that you get an air-gapped transaction signer with secure-element seed storage. The card becomes your offline seed vault, while SeedSigner remains the device you use to review and sign transactions via QR codes.
Loading seeds and passphrases from SeedKeeper
The core workflow is simple: insert a compatible smartcard into the reader, open Seeds in SeedSigner, choose Load A Seed, then select From SeedKeeper. You enter the card PIN if needed, and you can load a seed from the card.

You are not limited to loading only a seed. You can also load a BIP39 passphrase from the card. In my demo, I used one card for the seed and another card for the passphrase, but you can also store both on the same card if that is how you want to organise your setup. If you do not want to use a passphrase, you can continue without one.
The reverse direction works too. From the Seeds menu, choose Backup Seed, then select SeedKeeper. You give the seed a label and the device writes it to the card after confirming that it can talk to the smartcard. You can also load multi-seed descriptors in a similar way.
One important security note: this does not replace your normal backup discipline. A secure element is useful, but you should still understand exactly which seeds are on which cards, how they are labelled, and what PINs or passphrases apply to them. If you use multiple cards, keep clear notes for yourself in a safe location.
Flashing applets to JavaCards
If you do not want to buy retail SeedKeeper or Satochip cards, the smartcard hat can also flash compatible JavaCards with applets. In my fork, you can go into DIY tools and choose Install Applets. The device lists bundled .cap files that you can install onto a compatible card.

The applets included in the fork include:
- Satochip / SatoDime for Satochip-based use cases.
- SeedKeeper for storing BIP39 seeds and passphrases on a JavaCard.
- SmartPGP for GPG-related smartcard functionality.
- Specter-DIY for flashing the smartcard needed by Specter-DIY setups.
- VivoTOTP / vivokey-otp for Yubico-compatible one-time password generation on a smartcard.
This makes the hat useful beyond Bitcoin seed storage. It becomes a general-purpose JavaCard programming tool, as long as the card is compatible and you understand what each applet does before flashing it.
Smartcard hat variants: SIM-size, full-size and dual-slot
The main hardware piece is the smartcard hat for Raspberry Pi. I made it because people kept trying to build SeedSigner + SeedKeeper setups themselves and running into problems with fake or unreliable NFC modules. This design gives you a cleaner, more reproducible path.
You can buy the Smartcard Hat for Raspberry Pi with USB-C Input power from my store, order it turnkey fabricated from PCBWay, or build one yourself using the open design files.

There are three main variants:
1. SIM-sized single reader
This version uses a SIM-sized smartcard slot. It is small and compact. If you solder it directly to the Raspberry Pi pins, you can fit the whole thing into the same case as an OpenPill Mini while adding smartcard functionality without increasing the size much.
The tradeoff is that SIM-sized cards are usually contact-only. They typically do not support NFC. That is fine for SeedSigner use because the hat uses a contact reader, but it matters if you want NFC features elsewhere.
2. Full-size single reader
This version uses a full-size smartcard slot. It does not have room for a SIM-sized reader. Full-size cards often support NFC, especially retail Satochip cards. If you specifically want a retail Satochip card with artwork and branding, that is the form factor to use.
3. Dual-slot variant
This version has both a full-size slot on top and a SIM-sized socket below. The important thing to understand is that it still uses one reader path: you cannot have cards in both slots at the same time. You can only use one card at a time, either in the top or bottom slot.
Size, form factor and USB-C power
The hats are designed with quality of life in mind. They include a side USB-C power input, so you can power the device from USB-C or from the micro-USB ports on the Raspberry Pi when available. That gives you more flexibility for how you want to carry and use the device.
One caveat: if you use one of these hats with larger Raspberry Pis such as a Raspberry Pi 4 or Raspberry Pi 2, the side USB-C power input may be obscured by the Pi’s own ports. The connection can still work in some cases, but for now it is not the most practical option on those boards.
For a compact build, I would usually start with a Raspberry Pi Zero 1.3. If you want a larger screen and a more comfortable user interface, the full-size reader can also be used with the new SeedSigner Plus large-screen display hat. The SeedSigner+ (Plus) Display Hat & USB-C Power + MicroSD Extender works nicely with a full-size card reader using stacking headers, though the device is slightly thicker than a standard SeedSigner Plus because of that extra layer.
Linux CCID driver support
Another important point: these hats are not locked into one project. They use the standard Linux CCID smartcard driver stack. That means they can be used for normal Linux smartcard tasks, similar to a USB smartcard reader.
This matters if you want a device that is useful beyond SeedSigner. You are not building a single-purpose gadget; you are adding a contact smartcard interface to a small computer. The same hardware can support JavaCard operations, GPG-related tools and other smartcard workflows depending on the software you run.
Assembling the soldered smartcard hat variant
If you want the smallest possible build, the soldered SIM-size hat is the one to use. You are essentially adding a compact reader directly onto the Raspberry Pi GPIO pins.
Soldered assembly steps
- Start with a Raspberry Pi Zero. If it already has pin headers soldered on, you can place the hat over them.
- If your Pi does not have soldered pin headers, mount the no-pinheader smartcard hat directly onto the GPIO pins.
- Use small 3D-printed spacers if needed so the board sits flush and stable.
- Solder the first five connectors on one side and the last four on the other side to secure the hat.
- Add the display module on top, just like a normal SeedSigner build.
Once assembled, the device should behave like a normal SeedSigner with an added smartcard reader. If you solder it in place and later want to remove it, I found that gently rocking it backwards and forwards is usually the best way to release it without stressing the pins.
Assembling the stacking-header variant without soldering
If you do not want to solder anything, the stacking-header version is easier. This is also useful if you already have a SeedSigner-style build and just want to add smartcard functionality with minimal risk.
Stacking-header assembly steps
- Insert the smartcard reader into the case or housing.
- Align the ribbon cable first so it seats correctly in the slot. It can be snug, but it should fit.
- Use a small screwdriver if needed to help guide the reader into place.
- Make sure the reader is flat against the edge and that all holes are engaged.
- Insert the stacking header through the alignment holes. Check pin alignment carefully; you can look through the holes to confirm it is straight.
- Push the stacking header down until it seats properly.
- Add the retaining piece where needed.
- Align the display with the pins and press it down firmly.

The current design uses a press-fit arrangement to hold the display in place. I may revise this later, and if you are good at 3D printing, a better retaining mechanism would be welcome. For now, it works as long as everything is aligned properly before you push the screen down.
If you want a cleaner finished build, the 3D Printed Case for SeedSigner + Smartcard Hat gives you a more enclosed and portable form factor.
Installing the SeedSigner smartcard fork
Before testing the reader, make sure your microSD card has the correct SeedSigner fork flashed to it. The stock SeedSigner project does not include all of these smartcard features by default, so using my fork is important for this setup.
Software setup steps
- Flash the custom SeedSigner smartcard fork image to a microSD card.
- Insert the microSD card into your Raspberry Pi build.
- Power on the device and wait for it to boot fully.
- Do not remove or reinsert the SD card until the system has finished writing, if prompted.
After boot, you should be able to access the normal SeedSigner interface plus the extra smartcard tools in my fork.
Testing the SEC1210 reader and smartcard connection
Before loading seeds or flashing applets, I always test the hardware first. This saves a lot of confusion later.
Card reader testing steps
- Open Settings on the SeedSigner device.
- Choose List Card Readers.
- Confirm that it detects the SEC1210 smartcard controller.
- If it also reports an NFC reader, do not worry about that; that is normal in some setups.
- Go to Settings and choose Test Smartcard.
- Insert a compatible smartcard into the slot.
- Confirm that the device detects the card.

This test works whether the card is a retail card or one you have flashed yourself. Once it passes, you can move on to loading seeds, backing up seeds or installing applets with much more confidence.
Extra features: Krux encrypted seed QR codes and passphrase scanning
My fork also includes some useful additions from other SeedSigner work, including support for Krux-compatible encrypted seed QR codes. This means you can load an encrypted seed QR code into the device using a known encryption key, just like any other seed source.

You can also export seeds in this same format so they can be read by either this fork or Krux. That gives you another way to move encrypted seed data around without exposing the raw BIP39 words on screen.
There is also a simpler passphrase feature: you can scan a plain-text BIP39 passphrase from a standard QR code. There is no special format required. It just needs to be normal text encoded as a QR code. In my demo, I generated a simple test passphrase QR code and scanned it into the device using Scan Passphrase.
If you do not have another phone or app handy, you can also use the tools menu inside SeedSigner to encode text into a QR code. That is useful when you want to generate a passphrase QR on one air-gapped device and scan it with another, or even transcribe it by hand if that fits your workflow better.
GPG signature verification in the fork
One of my favourite additions is built-in GPG verification. This lets you verify signed release files without needing a full desktop environment on the same machine.
The basic idea is:
- Put the file you want to verify onto the
microsd-imagesfolder of the SeedSigner microSD card. - Also put the project’s manifest file and its OpenPGP signature file in the same place.
- Boot SeedSigner with that SD card inserted.
- Go to Tools, then GPG tools.
- Verify the manifest signature first.
- Then check the SHA-256 sum of the actual release file against the signed manifest.

In my video example, I used a Sparrow installer along with its manifest and signature. The device confirmed that the manifest was correctly signed by the project author and that the installer matched the SHA-256 value in that signed manifest. That gives you much more confidence before installing software from an untrusted download environment.
The fork bundles public keys for various projects, but if a key you need is missing, you can import your own. If you maintain a project and want your public key included in future builds, you can open a pull request with the relevant details. The goal is to make it easier for people to cross-check software against known-good publisher keys.
Choosing cards: SeedKeeper, Satochip and J3H145
For this setup, you have several card options. A retail Satochip card is usually full-size and often supports NFC, which makes it a good choice if you want that capability outside of the contact reader. If you only care about using the card with SeedSigner through the hat, contact-only cards are fine.
You can also use blank JavaCards such as the J3H145 Javacard and flash them yourself. This is more advanced because you need to be careful with applet selection, PIN handling and card compatibility. But it gives you a lot of flexibility if you want to build your own secure-element workflow from scratch.
I have tried cutting J3H145 cards down to SIM size before. It can work, but it is fiddly and hit-or-miss. If you are not comfortable with that, I would recommend buying the card form factor you need rather than modifying a full-size card yourself.
Future work: transaction signing on Satochip
The next big piece of work I want to explore is making SeedSigner review transactions via QR code while keeping the private keys entirely on a Satochip smartcard. In that model, the secure element would handle transaction signing directly, which would significantly reduce how much trust you place in the Raspberry Pi and SeedSigner software itself.
That would be a meaningful security improvement for people who want an air-gapped workflow with as little exposure as possible. I also plan to expand the GPG functionality by making more use of SmartPGP on smartcards, so key operations can happen off the main device where appropriate.
Conclusion: a practical path to secure-element SeedSigner builds
The SeedSigner + SeedKeeper smartcard hat is one of those projects that feels very natural once it is working. You get an air-gapped Bitcoin signer with secure-element seed storage, applet flashing, QR-based encrypted seed support and useful GPG verification tools. It is also far easier to build now that there are proper hats instead of relying on random NFC modules from unclear sources.
If you want the easiest route, start with a complete kit and a compatible card. If you want more control, use blank JavaCards and flash them yourself. Either way, test the reader first, label your cards clearly, keep your PINs and passphrases organised, and remember that secure elements are one layer of protection, not a magic replacement for good operational security.
This is an exciting area because it combines open-source hardware, secure elements and Bitcoin self-custody in a way that remains practical for advanced users. If you have questions about the smartcard fork or your own build, leave them in the comments. I try to answer as many as I can, especially when people are working through assembly issues or trying to decide which card form factor makes sense for their setup.
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.







