SeedSigner + Satochip Stateless Bitcoin Signing

I have been working on a fork of SeedSigner that adds smartcard-based functionality, and the newest feature I want to show you is fully stateless operation using a Satochip secure element card. In plain English: your private keys can live on the Satochip JavaCard, while SeedSigner acts as the human interface for reviewing transactions and signing them without ever holding the seed locally.

If you prefer the demo, Watch the video.

Why this matters

The main security benefit is that the private keys do not need to be loaded onto the SeedSigner device when you are signing transactions. The seed can remain on the Satochip card, and SeedSigner can still let you review transaction details, verify change addresses, and approve a PSBT before the card signs it.

That means your normal SeedSigner workflow can stay mostly the same, but with an extra layer: even if something malicious were present on the micro SD card or in the device environment, the private keys are not sitting there for it to touch during signing.

This is especially useful for people who want a DIY air-gapped setup with secure-element-backed storage and signing, without relying on a proprietary hardware wallet.

SeedSigner next to a SeedKeeper smartcard
SeedSigner and SeedKeeper card

What you need

For the demo in the video, I used:

  • A SeedSigner device
  • A Satochip JavaCard for signing
  • A SeedKeeper card for seed backup
  • Sparrow Wallet on a computer
  • A smartcard reader interface compatible with your SeedSigner setup

If you are building this from scratch, the SeedSigner + Smartcard Kit is a good starting point. If you want a plug-and-play GPIO option for Raspberry Pi, the Smartcard Hat for Raspberry Pi with USB-C Input power is what I use in many of my smartcard demos. You can also use a generic contact smartcard reader where supported, but the GPIO hats are convenient because they stack directly onto the Pi and keep the whole thing compact.

If you are using a standard smartcard rather than a Satochip-branded card, make sure it is compatible with your setup. The J3H145 Javacard is one of the cards I have used for DIY JavaCard work.

Important distinction: Satochip is not a backup

This is the part people get wrong most often.

A Satochip card can store your seed and sign transactions, but it cannot give you back your BIP39 mnemonic words in a way that lets you restore them into another device as normal recovery words. In other words: Satochip is not a backup.

A SeedKeeper card can store your seed for backup purposes, but it does not sign transactions by itself in the same way. So these two cards serve different roles:

  • SeedKeeper: offline seed storage and backup
  • Satochip: secure-element signing and on-card key use

You should still back up your recovery seed properly before moving into a Satochip-based workflow. If you lose access to both your SeedKeeper backup and any other valid recovery material, the Satochip card alone is not going to replace that backup.

SeedSigner connecting to a smartcard
Connecting SeedSigner to a Satochip card

Step-by-step: create seed, back it up, then initialize Satochip

Here is the workflow I used in the video.

1. Create a new recovery seed in SeedSigner

Start by creating a new seed in SeedSigner as you normally would. In the demo, I skipped some of the slower verification steps for speed, but in real life you should do your backup verification properly.

Do not rush this part. This is where mistakes happen.

2. Back up the seed to SeedKeeper

Next, back up the seed to a SeedKeeper card. Give it a label if that helps you, and make sure the write completes successfully.

After this step, your seed exists on the SeedKeeper card as an offline backup. That is the recovery layer.

3. Initialize the Satochip card with the seed

Now insert the Satochip JavaCard into the smartcard reader connected to SeedSigner.

Go into:

Tools → Smart Card Tools → Satochip → Initialize with seed

You will be asked to set a PIN for the Satochip card. This is the PIN you will need when using the card for signing, whether through SeedSigner or directly through Sparrow.

Choose a strong PIN and remember it. Do not use something weak just because it is convenient. If someone can guess your card PIN, they can use the card to sign transactions.

After setting the PIN, select the seed you want to import onto the Satochip card and complete the initialization.

4. Remember: BIP39 passphrase must be included at import time

If you are using a BIP39 passphrase with your seed, this is important:

You cannot simply re-enter the passphrase every time you use the Satochip card. The seed plus passphrase combination needs to be initialized onto the card when you set it up.

So if your recovery setup uses a passphrase, make sure you initialize the correct derived result onto the Satochip card during setup.

SeedSigner showing in-memory seeds with smartcards nearby
In-memory seed menu and smartcards

Pairing Sparrow from a blank SeedSigner

Now for the stateless part.

Power down the SeedSigner so that no seed is loaded into it. Boot it back up as a completely blank device. There should be no seeds in memory.

Insert the Satochip card and go to:

Tools → Smart Card Tools → Satochip → Export xpub

Choose the script type you want. In the demo, I used native SegWit. You will then export the xpub into Sparrow.

In Sparrow:

  1. Create a new wallet
  2. Choose that you have an air-gapped hardware wallet
  3. Select SeedSigner as the device type
  4. Scan the QR code shown by SeedSigner

SeedSigner may show a privacy warning during this process. That is expected when exporting details from the card to pair with Sparrow. Confirm it, enter your Satochip PIN if prompted, and complete the export.

Once Sparrow has the xpub, you can apply it and finish wallet setup.

Sparrow receive screen next to SeedSigner export confirmation
Pairing Sparrow with a stateless SeedSigner

Address verification after pairing

One useful addition in my fork is address verification after you pair with Sparrow. This helps reduce the chance that something went wrong during setup or xpub import.

In the demo, I scanned the receive QR code shown by Sparrow into SeedSigner. SeedSigner then checked whether that address matched what it expected from the wallet associated with the Satochip card.

This is a small thing on screen, but it is a big practical benefit: you get extra confidence that your wallet software and your signing device are talking about the same addresses before you send funds to them.

Sparrow addresses cross-checked against SeedSigner
Cross-verifying receive addresses in Sparrow and SeedSigner

Signing a PSBT on the Satochip card

Once the wallet is paired, sending funds follows a familiar flow.

In Sparrow:

  1. Enter your destination address
  2. Choose an amount or send max
  3. Create the transaction
  4. Finalize for signing
  5. Show the QR code

On SeedSigner:

  1. Scan the PSBT QR code
  2. Select the Satochip card option
  3. Make sure the card is inserted
  4. Enter the card PIN
  5. Review the transaction details on screen
  6. Approve the PSBT

SeedSigner will query the xpub from the Satochip card as needed, verify the change address against that wallet, and let you review the outputs before signing. The actual signature happens on the smartcard, then the signed transaction is returned to Sparrow for broadcast.

This is where the stateless model becomes very practical: you get human-readable verification on SeedSigner while keeping the private keys inside the secure element.

Signed transaction in Sparrow with SeedSigner showing QR
Signing a PSBT using Satochip

What this does not do for you

I want to be clear about what this setup is and is not.

It does not replace your backup

Again, the Satochip card is not a recovery backup in the normal BIP39 sense. You cannot pull your mnemonic words back off it and restore them like a standard seed phrase.

Your SeedKeeper card, paper backup, or other valid recovery material still matters. If you lose all of that, having only a Satochip card is not the same as having full recovery access.

It does not remove all risk from blind signing

If you use the Satochip card directly with Sparrow through a USB smartcard reader without SeedSigner, you can sign transactions in a more direct way. But that workflow can involve blind signing, meaning Sparrow passes the transaction to the card and the card signs it with less human review on a separate air-gapped device.

That may be acceptable if you understand the risk and are comfortable with it, but it is not the same level of review as using SeedSigner to inspect the PSBT first.

Satochip 2FA should stay disabled for SeedSigner use

If you enable Satochip 2FA, that flow works with certain Electrum-based blind signing setups, but it does not work properly with the SeedSigner integration. If you want to use Satochip with SeedSigner, leave 2FA off on the card.

Address explorer also works with Satochip

Another useful feature is the address explorer. You can load wallet details from the Satochip card and browse receive addresses directly in SeedSigner.

This is handy when you want to verify a long list of addresses against Sparrow or another wallet interface. In the demo, I compared the addresses shown on SeedSigner with the addresses tab in Sparrow, which made it easy to confirm that both sides were aligned.

For people who receive funds from multiple sources or manage multiple addresses, this is one of those small workflow improvements that saves a lot of manual checking.

SIM-sized JavaCard options and DIY form factor

One reason I like the smartcard approach is how flexible it can be. You can use standard cards with readers, but you can also build more compact setups using SIM-sized JavaCards and GPIO reader hats.

This lets you create a device that has roughly the same physical footprint as a normal SeedSigner while still adding secure-element-backed storage or signing depending on which applet is running on the card.

For most people, I would keep the backup and signing cards separate. That gives you clearer separation between recovery material and active signing use. But for advanced users, there are interesting possibilities, such as storing a multisig descriptor on one card while using another card for signing.

If you want to experiment with SIM-sized readers or hats, the Smartcard Hat for Raspberry Pi with USB-C Input power is a good option because it keeps the build simple and plug-and-play.

SIM-sized smartcard reader module
Compact SIM-sized smartcard reader

SLIP39 support for Trezor users who have lost their device

The fork also adds full SLIP39 support, which is useful if you are coming from a Trezor-style recovery setup. You need to enable SLIP39 seeds in the settings first.

Once enabled, you can work with SLIP39 shares and restore them onto compatible cards or other storage methods. If someone has lost access to their Trezor device but still has valid SLIP39 shares, this opens up a recovery path that does not require the original hardware wallet to be present.

You can reconstitute the recovery seed from those shares and then move into a more secure signing setup if needed. If you are in a complicated recovery situation, it is worth getting help rather than guessing. You can read more about my recovery services and consultations if you need guidance there.

Better smartcard performance on GPIO hats

If you have been using my fork with GPIO smartcard reader hats, one of the most noticeable improvements is speed. The smartcard interaction has been optimized under the hood, and operations such as storing and retrieving seeds from SeedKeeper are much faster than before.

This matters more than it sounds. A secure-element setup should not feel like a punishment to use. If every operation takes too long, people get sloppy or abandon the workflow. Faster card performance makes the whole system more usable in daily life.

What is coming next

There is still more on the way for this fork. One of the next major additions is expanded GPG functionality. Previously, the GPG tools were mostly about verifying file signatures and checking software integrity. The upcoming release will add much deeper capabilities, including generating keys on device using BIP85, loading keys from SeedKeeper, signing messages, signing files, initializing smartcards with those keys, and running smart GPG workflows.

If you care about encrypted messaging, file verification, or PGP-related tooling, that is worth watching for.

Practical security notes before you set this up

Before you build a Satochip-based SeedSigner setup, I would recommend the following:

  1. Back up your seed first. Do not assume the smartcard replaces your backup.
  2. Use a strong card PIN. The PIN is part of your signing security model.
  3. Keep backup and signing cards separate if you can. It reduces confusion and limits what one compromised or lost card can do.
  4. Verify addresses before sending funds. Use the address verification features whenever possible.
  5. Do not enable Satochip 2FA if you are using SeedSigner integration. Leave it off for this workflow.
  6. Understand blind signing limits. Direct Sparrow-to-Satochip signing without SeedSigner review is a different risk profile.

If you want to protect the physical cards when they are not in use, an RFID Blocking Sleeve can help reduce casual NFC exposure for contactless-capable cards. It is not a complete security solution by itself, but it is a sensible physical hygiene step.

Conclusion

The biggest takeaway from this video is that SeedSigner does not have to be limited to loading seeds into its memory just to sign transactions. With the Satochip fork feature, you can keep private keys on the secure element card and use SeedSigner as a stateless reviewer and signing interface.

That gives you a more robust DIY Bitcoin setup: air-gapped human verification, secure-element-backed signing, proper backup through SeedKeeper or other methods, and a workflow that still feels practical enough to use regularly.

If you have questions about this specific smartcard fork, the best place to ask is in the smartcard fork Telegram group rather than spamming the main SeedSigner group. I also try to answer comments on my videos, so feel free to leave a question there if something was unclear.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

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