Cowrie Research

satochip

4 min read

Satochip

  • Name: Satochip
  • URL: https://satochip.io/
  • Category: smart-card hardware-wallet infrastructure / seed-backup vault stack / NFC self-custody tooling / external-wallet integration layer
  • Tags: bitcoin-ecosystem
  • Summary: Satochip is a Belgium-based self-custody stack centered on an NFC smart-card hardware wallet, the Seedkeeper backup vault card, and open-source companion and integration software. Keep this note on the product surface: card-based signing, backup flows, applets, and outside-wallet interoperability. The named operator boundary around webshop distribution, business customization, customer-data policy, and the release/support shell now lives separately in satochip.
  • What it does:
    • Ships the Satochip hardware-wallet card for storing and using crypto keys through NFC or a smart-card reader
    • Ships Seedkeeper as a separate secure-vault / seed-backup card that can pair with Satochip for encrypted seed export and recovery workflows
    • Publishes desktop and mobile setup guides covering Electrum, Sparrow, Uniblow, WalletConnect-compatible flows, and first-party companion utilities
    • Maintains open-source JavaCard applets, bridge and utility software, and developer libraries for integrating the cards into other wallet environments
    • Extends the broader card ecosystem with adjacent products like Satodime, which helps reveal that Satochip is building a reusable card-and-software stack rather than only one wallet SKU
  • Key claims:
    • The homepage says Satochip’s software solutions are open-source and non vendor locking and specifically calls out Electrum, Sparrow Wallet, BitcoinKeeper, Uniblow, and WalletConnect, which is the clearest signal that the stack is designed to plug into outside wallet surfaces rather than trap users in a first-party app alone
    • The main product page says Satochip is powered by an NFC chip card, embeds an EAL6+ certified chip that acts as a secure element, and supports PIN-based access plus optional 2FA approval from a mobile device
    • The same product page says the code is completely open source under the AGPLv3 license, which is a meaningful distinction versus hardware-wallet vendors that are only partly open
    • The software and quick-start pages show separate desktop and mobile onboarding tracks, which makes the operational surface much broader than a card-only ecommerce product page would suggest
    • The SatochipApplet repository describes the project as an Open source javacard applet implementing a crypto-currency hardware wallet with full BIP32/BIP39 support and explicitly says private keys are never exported outside the secure chip
    • The Seedkeeper-Applet repository documents encrypted export, device authentikey pairing, backup-to-backup replication, and secure import into Satochip, which is the clearest evidence that the product family is really a card-based self-custody and backup stack
    • The Toporin GitHub organization page is useful because it surfaces SatochipApplet, Seedkeeper-Applet, bridge tooling, mobile apps, and Python libraries in one place, making the broader platform visible even when the main website is commerce-led
  • Whitepaper: No canonical standalone Satochip whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site’s product/software/quick-start pages plus the Satochip and Seedkeeper applet repositories; for the company boundary above this product layer, also see ../whitepapers/satochip-company-primary-sources-2026-08-10.md.
  • Sources:

Internal linkages

  • Company / operator boundary above the product surface: satochip.
  • Strongest comparison points: coinkite, foundation-devices, and sparrow-wallet.
  • Reusable lens: Satochip is useful when the real comparison is card-based signing, backup-vault separation, and external-wallet interoperability rather than a heavyweight new custody model.

Protocol / company boundary

  • Keep this note on the product surface: the smart-card signer, Seedkeeper backup mechanics, applet capabilities, NFC / reader-based flows, and compatibility with outside wallet or dapp environments.
  • Use satochip for the named operator layer above that product surface: webshop and partner distribution, business customization, customer-data and legal-policy shell, and the broader release/support pipeline around the cards and companion tools.
  • That split matters because what can the Satochip card stack do? and who controls how the official cards, apps, terms, and support reach users or partners? are related but not identical questions.

Control surface

  • At the product layer, practical leverage sits in applet capabilities, card pairing and recovery design, Seedkeeper backup mechanics, supported external-wallet integrations, and how easily the stack plugs into NFC, reader, and WalletConnect-style environments.

  • The fact that the software is open source and integration-friendly matters, but it does not erase the operator boundary above it. For webshop distribution, customization policy, and the legal/support shell around the official stack, read satochip.

  • Read Satochip as reusable card-based self-custody infrastructure, not merely as a low-cost hardware-wallet SKU.

  • Last reviewed: 2026-08-10 UTC

Graph View

Backlinks