Skip to content
Shop Bitcoin Australia Buy a Bitaxe →

SeedSigner Plus Smartcard Edition: Set Up and Sign with a SeedKeeper

Load your keys from a PIN-protected SeedKeeper card instead of a visible SeedQR. The trade-off, how to verify the image, PIN and lockout rules, and the menu steps from the fork's docs.

Self-Custody intermediate 45 min read Reviewed Nov 2026 #seedsigner#smartcard#seedkeeper

The SeedSigner Plus Smartcard Edition is a SeedSigner Plus with a smartcard reader built in. Instead of showing a SeedQR to the camera every time you sign, you tap in a PIN and the device loads your seed from a SeedKeeper card. Like every SeedSigner, it keeps nothing when the power goes off.

This guide covers what you are trusting, how to check the software, and how to set up and use a card. Where a step comes from the fork’s documentation and not from our own testing, we say so.

Who it suits

It suits someone who signs often and does not want a SeedQR sitting on a desk or in a drawer. The shop listing describes it as a good daily driver: the card holds the backup, protected by a PIN, so you do not have to dig out a printed SeedQR each time.

It does not suit you if you want the most scrutinised software available. See the next section.

The trust trade-off

The device runs ShieldSigner, a fork of SeedSigner by YTCryptoGuide (the GitHub account is 3rdIteration). Our listing says plainly that this OS does not get the same level of scrutiny as the SeedSigner OS. Take that seriously.

What the maintainers publish, as of 1 November 2026:

  • The latest release is SeSi-0.8.7+ShSi-B13, dated 6 October 2026. It is built on SeedSigner 0.8.7.
  • The release notes say all production images were independently rebuilt from source and matched the published hashes byte for byte, and give the build command.
  • The release notes list PSBT verification fixes, including one for a crafted-transaction bypass. That is good to see published, and it also shows the code is still changing quickly.
  • The repository has a SECURITY.md with an email address and a GPG key for reporting bugs.
  • The README describes the smartcard support as “mostly feature complete” beta software.

Prefer the standard SeedSigner OS if you hold a large amount, you want the widest review, or you are happy with a SeedQR or paper. Our assembly guide and dice guide cover that route. The hardware is the same family, and the standard OS needs no card.

What you need

  • The SeedSigner Plus Smartcard Edition, AU$275 in the shop. The SD card is loaded with the latest ShieldSigner image.
  • A SeedKeeper card. We do not sell these. The simplest route is a ready-made card from Satochip, the maker. The fork’s docs also describe flashing the SeedKeeper applet onto a blank J3H145 JavaCard yourself (smartcard installation doc); a blank card does nothing until that is done.
  • A metal seed backup, and pen and paper.
  • Sparrow Wallet on a computer, for the watch-only side.

SeedKeeper or Satochip

Both are Satochip cards, and the fork supports both, but they do different jobs.

  • SeedKeeper stores secrets (seeds, passphrases, descriptors) behind a PIN. The SeedSigner still derives keys and signs. The fork’s docs call it a storage device. This is what the listing describes and what this guide uses.
  • Satochip is a wallet card: the fork can load a seed onto it and sign on the card.

Pick one and follow it. This guide does not cover Satochip signing.

Where the card goes

The listing’s first photo shows the orange case from the side. There is a wide slot along the long edge, next to the USB-C port, with a smaller microSD slot below it. From the photo, the wide slot is where the card goes. Insert the SeedKeeper into the card slot, contacts first. Do not force it.

Safety first

Read all of this before you touch a card.

A SeedKeeper holds the money. Whoever has the card and the PIN can load your seed. Anyone who sees your seed words can take your bitcoin. Words never touch a camera, a phone, a cloud service, a printer or a password manager.

  • The card is not your only backup. Keep a metal backup of the seed words. Cards can be lost, damaged or locked. The fork’s own quick start says the card may be your only copy if you rely on it.
  • Wrong PINs lock the card for good. The SeedKeeper applet’s README says it bricks itself after several wrong PINs, typically 5. In the fork the limit is set when a card is first set up (default 5, range 2 to 10). The unblock code is random and never shown, so there is no PIN recovery. The fork’s docs say the same: “there is no PIN recovery”.
  • Choose a PIN you can remember without writing it next to the card. The applet’s README says a PIN is 4 to 16 characters. Do not use a birthday or the last digits of your phone number. Store the PIN somewhere separate from the card.
  • Factory reset wipes the card. The fork’s screen warns that a reset without a working backup means unrecoverable loss of funds.
  • Test recovery before you trust it. Restore your metal backup on a spare device (or the same one) and check the fingerprint matches, before moving real money.
  • Start small. Send a small amount first and spend it back.
  • Make the seed in private. No people, webcams or smart speakers. Destroy any scrap paper once the metal backup is checked.

Step 1: Check the image

Do this before you put real money on the device. Your SD card arrives loaded, so you are checking that it matches what the maintainers published.

  1. On a computer, open the B13 release page. Check it is still the latest release. If your device has an older image, that is not an error, but read the newer release notes.
  2. Find the list of SHA256 checksums. For the Raspberry Pi Zero, the file is seedsigner_os.SeSi-0.8.7_ShSi-B13_.pi0-smartcard.img.
  3. The release body says you can confirm the checksums by verifying the Bitcoin message signature with the address 37hiiSB1Poj6Shs8WawPS2HjT2jzHkFSQi. Use any Bitcoin message verification tool, with the message set to the checksum block between the dashed lines.
  4. Look up that signing address in a second place that is not the same release page, such as an independent repository that records ShieldSigner releases, seedsigner-verify. If the two sources disagree, stop.
  5. To go further, the release notes give the command to rebuild the image yourself. The maintainers state that they did this and matched the hashes.

Flash the verified image yourself rather than relying on the SD card in the box (the fork’s docs suggest Balena Etcher), then confirm its checksum before use. SeedSigner is stateless, so reflashing does not touch your card.

Step 2: Start the device and insert the card

  1. Plug the USB-C cable into the power port. Wait for the home screen.
  2. Slide the SeedKeeper card into the card slot.

Smartcard support is on by default (Settings, Advanced, Smartcard support), per the fork’s SeedKeeper doc. The menu is Tools, then Smartcard Tools, then SeedKeeper Functions.

Step 3: Set the PIN on a blank card

  1. Open Tools, Smartcard Tools, SeedKeeper Functions.
  2. On a blank card the first SeedKeeper action shows a Card Uninitialised warning and asks for a New Card PIN, entered twice. This is from the fork’s docs.
  3. Choose a PIN as per the safety section. Enter it, then enter it again.

Before you choose, open Settings and check Smartcard PIN Attempts. The source shows this value is applied when a card is first set up. The default is 5.

Keep Cache Smartcard Pin off if you can. By default it is off. When on, the fork’s docs say the PIN is remembered for the session and cleared on restart or when the card changes.

Step 4: Create or import a seed onto the card

You need a seed first. You have two choices.

  • Create a new one on the device using Tools, New seed. Camera or dice entropy. Our dice guide covers the dice route.
  • Type in an existing seed using the Enter 12-word seed or Enter 24-word seed options on the load screen. Typing a seed in means the words exist on paper or in your head already. Do it in private.

Whichever you choose, write the words on paper and make a metal backup now, before saving to the card.

Then save it to the card. This is from the fork’s SeedKeeper quick start:

  1. On the seed’s options screen choose Backup seed.
  2. Choose To SeedKeeper.
  3. Enter the card PIN if asked.
  4. Enter a Seed Label. The default is the fingerprint. A short name you will recognise is easier later.
  5. Wait for the Secret Saved screen.

The docs say a BIP39 seed is stored together with its wordlist and any passphrase, so loading restores the same wallet.

Write down the fingerprint on screen. You will use it to check recovery.

Step 5: Check the card

  1. Go to Tools, Smartcard Tools, SeedKeeper Functions.
  2. Choose View Secrets on Card to confirm the label is there.
  3. Choose View Free Space to see how much is used.
  4. Choose Card Settings, then Card Info. The source shows this screen lists PIN tries left, among other details.

For a second card as a spare, the menu has Clone Card Secrets, which copies from one SeedKeeper to another, prompting you to present each card. Satochip’s own page also describes a one-time backup function that copies a SeedKeeper to another card. A second card on its own is a convenience copy and is not a substitute for a metal backup.

Step 6: Load your keys to sign

  1. Insert the card.
  2. Go to Seeds, Load a seed, From SeedKeeper.
  3. Enter the PIN if prompted.
  4. Pick your seed from the Select Secret list.
  5. The seed loads into memory and the fingerprint appears. Check it matches the fingerprint you wrote down.

The fork’s docs say a seed can also be stored with a passphrase, or a passphrase kept on a separate card.

Step 7: Pair with Sparrow and sign

Pairing is the same as any SeedSigner, so follow Set Up Your First Hardware Wallet. In short, export the wallet’s public key from the SeedSigner to Sparrow by QR, build the transaction in Sparrow, then scan its PSBT QR with the SeedSigner.

  1. Load the seed from the card (Step 6).
  2. Scan the transaction QR from Sparrow.
  3. Read the address, amount and fee on the SeedSigner screen. Compare them against Sparrow. The release notes say a high-fee warning is now shown on the PSBT screens.
  4. Approve, then scan the signed QR back into Sparrow and broadcast.

The fork’s architecture notes describe this order (scan PSBT, review, select signer, show signed QR).

Step 8: End the session

  1. Finish signing and confirm the transaction in Sparrow.
  2. Slide the card out and put it away, apart from the PIN.
  3. Unplug power. The fork’s SeedKeeper docs say loaded seeds live in memory, and the cached PIN (if you turned it on) is cleared when the device restarts.

Troubleshooting

The card is not detected

The source shows the message No smartcard detected. Insert a card and try again. and, for a missing applet, Unable to find … (or Applet). Try Re-Inserting Card.

  1. Remove the card, check it is the right way up, and push it in firmly.
  2. Check you are using a SeedKeeper card, not a blank card with no applet.
  3. Check smartcard support is on in Settings.
  4. Restart the device with the card in.

The PIN is wrong

The device shows Incorrect PIN with the number of attempts left. Stop and think. Do not keep guessing. Each wrong attempt uses one of a limited number. Take your time and find the PIN before a last attempt.

The card is locked

If the PIN is blocked, assume the card cannot be recovered. The fork’s factory reset screen can wipe a card whose PIN is blocked, which makes it usable again but removes everything on it. Restore from your metal backup onto a fresh or reset card.

The card is full

The source shows a card-full status (0x9C01). The fork’s docs say you can delete a secret on a v0.2 card. On a v0.1 card only a factory reset or a re-flash frees space.

Something looks wrong with the software

Report it using the maintainer’s security policy, which asks for private email, not public issues. If you doubt the image, switch to the standard SeedSigner OS.

What’s next

This is general information about holding your own bitcoin. It is not financial, tax or legal advice.

Sources checked 1 November 2026: the Smartcard Edition listing and its two product photos; the ShieldSigner repository README, release SeSi-0.8.7+ShSi-B13, SECURITY.md and docs for SeedKeeper, the SeedKeeper quick start and smartcard installation; B13 source files smartcard_views.py, seedkeeper_utils.py, seed_views.py and settings_definition.py; the SeedKeeper applet README; the Satochip SeedKeeper page.

Frequently Asked Questions

Do you sell SeedKeeper cards?

No. As of 1 November 2026 there is no SeedKeeper or Satochip card in our catalogue. SeedKeeper is made by Satochip, so buy it from satochip.io.

How many wrong PINs before the card locks?

The SeedKeeper applet's README says the device bricks itself after the wrong PIN is entered several times, typically 5. The ShieldSigner fork sets the limit when it initialises a card: the default is 5, adjustable from 2 to 10 in its Smartcard PIN Attempts setting. The fork also sets the unblock code (PUK) to a random value that is never shown, so treat a locked card as gone. Without a backup that means lost bitcoin.

Is the card a backup of my seed?

No. A smartcard can be lost, damaged or locked. Keep a metal backup of your seed words as well, and test recovery before you rely on the card. The fork's own SeedKeeper quick start says the card may be your only copy if you rely on it, and to treat it accordingly.

Is ShieldSigner as well reviewed as SeedSigner OS?

No. Our listing says this OS does not get the same level of scrutiny as the SeedSigner OS, and asks buyers to do their own research and verification before committing significant savings. If you want the most reviewed software, use the standard SeedSigner OS with a SeedQR or paper backup.

Does it have WiFi or Bluetooth?

No. The listing says it uses a Raspberry Pi Zero v1.3 board with no WiFi or Bluetooth communication capability.

Can I read my seed off the card with something other than the SeedSigner?

The fork's docs say Satochip publishes a standalone Seedkeeper app for reading a card without a SeedSigner.