DIY Satochip JavaCard Hardware Wallet Guide

So, in this article, we’re going to run through how to create a DIY Bitcoin hardware wallet using Satochip, an open-source hardware wallet that runs on JavaCards. It’s basically like an open-source version of a Tapsigner or Tangem-style tap-to-sign device: small, discrete, and practical if you want a self-hosted signing option without assembling custom hardware.

You can also follow along with the full walkthrough here: Watch the video.

Satochip is a good DIY project for a few reasons. First, setup is simple compared with many other open-source Bitcoin wallets. There is no soldering or PCB assembly involved. You flash an applet onto a compatible JavaCard and you have a working hardware wallet. Second, the cards are affordable if you want to make several devices for yourself, family, or friends. Third, the physical form factor is very discreet. JavaCards come in many shapes: full-size contact cards, SIM-sized cards, key tags, rings, and other small formats.

The main security idea is that your keys stay inside a secure element on the card. The card signs transactions without exposing the private key to your computer or phone. That makes it useful for people who want a practical hardware wallet but do not want to build something from scratch at the chip level.

Satochip DIY JavaCards and Satochip devices
Blank J3R180 and J3H145 JavaCards next to SIM-sized cards and Satochip-style display cards

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 you need for the simplest setup

The easiest path is to use hardware that already matches what Satochip expects. In other words, buy a compatible blank JavaCard and a card reader from Satochip, then install the official applet using their published tooling.

For this path, you want:

  1. A compatible blank JavaCard.
  2. A smart card reader or NFC reader that works for flashing.
  3. The official Satochip CAP file.
  4. GlobalPlatformPro, usually accessed through gp.exe.
  5. A working Java installation, such as OpenJDK 8.

The simplest route is useful because it avoids a lot of guesswork. JavaCards can look identical on the outside but behave very differently underneath. If you are new to this, start with the known-good option before experimenting with cheaper or unfamiliar cards.

Satochip web store product pages for blank JavaCard and reader
Satochip web store page showing a blank JavaCard for DIY projects

Step 1: Download the official Satochip CAP file

A CAP file is the installable applet package for a JavaCard. For the simplest setup, use the official release from the Satochip GitHub repository. Do not grab a beta unless you specifically want to test something unstable.

Go to the official Satochip applet repository, open the releases section, choose the latest stable release, and download the CAP file asset. Save it somewhere easy to find, such as your Downloads folder.

Satochip-DIY GitHub repository
The 3rdIteration/Satochip-DIY GitHub repository with guides for building and flashing Satochip

Step 2: Get GlobalPlatformPro

GlobalPlatformPro is the tool used to install applets onto JavaCards. For this demo, I use the gp.exe file from the Satochip repository or documentation source because it keeps things close to the official process.

Download the raw executable and save it in a folder where you can run it from the command line. On Windows, that is usually as simple as opening Command Prompt, changing into your Downloads folder, and running gp.exe with the install option.

One important detail: GlobalPlatformPro needs Java to work. If you already have Java installed, it may just work. For this demo, I install OpenJDK 8 so the environment is clean and predictable.

OpenJDK 8 download instructions
GitHub readme showing how to download and install Java SDK 8

Step 3: Install OpenJDK 8 if needed

If you do not already have a working Java installation, install OpenJDK 8. For Windows, download the 64-bit JDK installer. During setup, make sure Java Home is set correctly so tools that depend on Java can find it.

You do not need to be an expert here. The goal is just to get a normal Java environment installed so gp.exe can run without errors.

Step 4: Flash the Satochip applet onto the card

Once you have the CAP file and GlobalPlatformPro ready, open Windows Command Prompt. Change into the folder where your files are located. For example:

cd Downloads

Then list the contents to confirm the files are there:

dir

Next, run the install command using gp.exe and the name of the CAP file. The exact filename will depend on which release you downloaded. In the video, the command looks like this:

gp.exe --install SatoChip-0.12-05.cap

Before running it, insert the JavaCard into your reader. If the reader light is active and green, the card should be ready. Press Enter in the terminal to start flashing.

Command prompt showing gp.exe install command
Flashing Satochip with gp.exe while the JavaCard sits in a USB smart card reader

When it finishes, you have a working Satochip hardware wallet. You can connect it from Sparrow Wallet, which has supported Satochip since version 1.8. In Sparrow, choose to connect a hardware wallet and scan for the device. The card should appear as your Satochip signer.

Which JavaCards work best?

This is where DIY gets interesting. There are many JavaCards available, but not all of them will run Satochip correctly. Some may look like they should work, but they fail because of missing vendor keys, unsupported firmware, or incompatible secure chip features.

The card I recommend if you want the smoothest experience is the J3R180. This is the type of card you get when ordering from Satochip. It is available in both full-size card and SIM form factor. The SIM version does not support NFC, but either format can be a great option for running Satochip.

Recommended JavaCards including J3R180
Blank J3R180 cards in full-size and SIM form factors next to other test cards

If you want a cheaper alternative, the J3H145 JavaCard is listed as tested and working. It costs less than the J3R180, but it is noticeably slower. You will feel that difference when signing transactions or generating wallets. It is not broken, just less responsive.

There are also THD89-based cards that work with Satochip after some tweaking. Examples include CodeWave NFC sticker tags and ThetaKey devices. These can be very discreet, especially in key-tag form factors. However, they have a few caveats:

  • Some are NFC-only.
  • Some contain batteries, and when the battery dies, the card is dead.
  • Some have displays that are not yet used by Satochip.
  • The underlying Java operating system may not carry the same certification level as other cards.

Security certifications matter, but they need to be understood correctly. A certification such as EAL6 or EAL6+ gives you confidence in the secure hardware and operating environment. It does not directly certify your Bitcoin applet. In other words, it tells you something about the foundation your applet is running on, not a direct audit of Satochip itself.

Incompatible JavaCards that will not work with Satochip
Three blank JavaCards listed as incompatible with SatoChip

What to do if flashing fails

If you try a card and see cryptogram warnings, invalid key errors, or messages saying the command or keys may break the card, stop. Do not keep trying blindly.

This usually means one of two things:

  1. The card is not compatible with Satochip.
  2. You do not have the correct vendor management keys for that specific card.

If you bought the card from a third-party seller and see this kind of error, contact them and ask for working keys or confirmation that the card supports the required JavaCard features. If they cannot provide usable keys, the card is effectively useless for this project. Treat it as a dud and move on.

Failed install showing cryptogram warnings
Command prompt showing failed SatoChip installation with cryptogram warnings

Choosing a safe smart card reader

You can use many types of readers: contact USB readers, dual-interface readers, or NFC readers. The important thing is to avoid using an unsafe reader for flashing.

In the video, I specifically warn against using an ACR122U NFC reader to flash these cards over NFC. It may work fine for normal operation once the card is already installed, but it can brick the card during the flashing process. If you have one of those readers lying around, use it only after the applet is safely installed, or better yet, avoid relying on it for this workflow.

Smart card reader options including ACR122U warning
Different USB smart card readers laid out for comparison

For sourcing readers, I use a mix of cheap contact readers and dual-interface NFC/contact readers. Some readers support both full-size cards and SIM-sized cards, which is convenient if you want to test different form factors. One thing to keep in mind: these are the same kinds of readers people use for government IDs, defense IDs, and other secure documents. Be careful where you get them from. There have been cases where smart card reader drivers were bundled with malware. On modern operating systems, a legitimate reader should usually work without needing you to install suspicious driver packages.

Building Satochip from source

If you want more control, you can build the applet yourself from source. This is useful if you want to verify what you are installing or experiment with different builds. For this part of the demo, I use a small NFC key tag because it is easy to carry and very discreet.

You will need Git and Apache Ant. On Linux, installing Ant can be simple. On Windows, download the binary distribution zip file from Apache Ant. Extract it somewhere convenient, such as your C drive, so the command path is easier to use.

Then recursively clone the Satochip-DIY repository. Do not just click “Download ZIP” if you want to follow this process correctly. You need a proper Git clone with all submodules included.

Git for Windows download page
Installing Git for Windows before cloning the Satochip-DIY repository

After cloning, switch into the Satochip-DIY folder and run Ant using the path to ant.bat. The exact path depends on which version of Ant you downloaded. When the build finishes successfully, a new build folder appears inside the repository. That folder contains compiled CAP files for different Satochip projects and builds.

Ant download page
Apache Ant binary distributions download page

Installing a built CAP file in Sparrow

Installing a self-built applet uses the same basic idea as installing the official CAP file. You run GlobalPlatformPro with the path to your newly built CAP file.

In Command Prompt, use:

gp.exe --install <path-to-built-cap-file>

Make sure the card is inserted into the reader before running the command. After installation, open Sparrow and scan for hardware wallets. Some THD89-based devices may take a few extra seconds to initialize the first time you use them, so give it a moment if the wallet does not appear immediately.

Successful build creating CAP files in build folder
Command prompt showing BUILD SUCCESSFUL and new build folder with compiled applets

Locking the JavaCard management interface

Once your Satochip card is working, you can optionally lock the JavaCard management interface. This prevents someone from installing or deleting applets without the correct key.

This is different from locking a wallet seed phrase. The card’s private keys are not exposed just because the JavaCard management layer is unlocked. Even if the card is not locked, it is not possible to download your Satochip wallet data off the card in normal use. However, an unlocked card can still be queried for installed applets, and someone with physical access could potentially delete applets or brick the card through management operations.

To lock the card, you need a 32-character hexadecimal management key. Generate one yourself and store it safely. Do not reuse keys from examples in documentation, and do not write your real key into public notes or screenshots. Once locked, only someone with that key can perform management operations such as listing applets, installing new ones, uninstalling them, or unlocking the card again.

Important: this management key is not needed for normal Satochip wallet operation. You do not need it to sign transactions or use the device as a hardware wallet. It is only relevant when managing the JavaCard itself.

Locking JavaCards with a management key
GitHub readme section explaining optional locking of JavaCards

Adding TOTP and SmartPGP applets

One powerful feature of the JavaCard platform is that multiple applets can exist on the same card while remaining securely segregated from each other. That means you can add extra functionality to your DIY hardware wallet without turning it into a single-purpose device.

Two useful options are:

  • A TOTP applet for one-time passwords.
  • SmartPGP for cryptographic verification and PGP-related use cases.

You install these the same way as Satochip: download the relevant CAP file and run gp.exe --install with that file.

Installing TOTP applet
Command prompt installing a TOTP CAP file onto a JavaCard

For TOTP, you can pair the card with Yubico Authenticator on a compatible phone. Tap the tag to the phone, add an account, and save it. You now have a hardware-backed one-time password token alongside your Bitcoin wallet.

Yubico Authenticator paired with Satochip key tag
Android phone showing Yubico Authenticator connected by USB to a JavaCard reader

For SmartPGP, you can pair the card with something like OpenKeyChain on Android. This lets you cryptographically verify that the card is the one you expect without relying only on PIN entry or visual inspection. That can be useful if you want stronger assurance that you are signing with your actual device and not a clone or counterfeit.

Installing TOTP and SmartPGP applets
Command prompt installing both TOTP and SmartPGP CAP files

My practical recommendation

If this is your first Satochip DIY build, start simple. Use the official applet, a known-compatible card such as J3R180, and a reader that you trust for flashing. Get it working in Sparrow before experimenting with custom builds, unusual cards, or extra applets.

Once you are comfortable, building from source is not too hard if you have basic command-line experience. It gives you more control and makes the project feel much more like a real self-hosted hardware wallet build.

For long-term use, I would also think about pairing Satochip with Seedkeeper. That setup generally uses two cards: one for Satochip signing and another for Seedkeeper backup or initialization support. This helps you create backups and initialize devices without relying on a hot machine to handle sensitive seed material.

If something goes wrong, the Satochip team is active in their official Telegram group, which is a good place to ask questions about both retail and DIY setups. And if you have questions about the cards, readers, applets, or general wallet safety covered here, leave a comment. I do my best to answer them.

Final thoughts

Satochip on JavaCard is one of the more interesting DIY options in Bitcoin hardware wallets right now. It is low cost, open source, physically secure by design, and much easier to set up than many other self-built devices. The tradeoff is that you need to be careful with card compatibility and reader selection, especially when flashing over NFC.

If you want a discreet tap-to-sign wallet that feels closer to a Tangem or Tapsigner but gives you more control over the software and hardware, this is a very practical path. Start with the simplest setup, lock down management access if you care about physical tamper resistance, and then expand into extra applets only once your core wallet is working reliably.

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