XBT guide · updated 2026-11-15

How to self-custody XBT: which hardware wallets support it

Quick version

  1. Get a signer that can make XBT’s replay-protected signature: Paperclip Krux (ready-made) or a SeedSigner with privkeyio’s XBT firmware (DIY). Stock Ledger, Trezor, Coldcard, BitBox, Jade, Keystone and Passport can’t yet.
  2. Make a brand-new seed on the device, write it on paper, verify the backup. Never use your BTC seed.
  3. Pair it with Shrike (watch-only), receive a small test, send a small test, check the send screen says replay protected, then move the rest.

The plain answer: you self-custody XBT by holding it at addresses whose seed only you have, ideally on a signing device that never goes online. No mainstream hardware wallet supports XBT on its normal firmware yet. Ledger, Trezor, Coldcard, BitBox, Jade, Keystone and Passport can’t make XBT’s replay-protected signature. Without it, a spend of coins you held before the split could be copied onto the BTC chain. What works today is Paperclip Krux, a $70 signer built only for XBT; a SeedSigner running community XBT firmware; or a spare Trezor or Coldcard re-flashed with unofficial firmware. Each one signs for Shrike, the desktop XBT wallet, which needs your own Bitcoin Knots node. All of it is new and unaudited, so start small.

Jump to: Best option · Device table · Device notes · New seed · Pair with Shrike · No hardware wallet? · New words: glossary

  1. Get a signer that supports XBTPaperclip Krux or SeedSigner
  2. Make a new seed on itPaper backup, never your BTC seed
  3. Pair it with ShrikeWatch-only, mark replay protection
  4. Test, then move the restSmall receive, small send

Golden rule: never type a seed that still guards bitcoin into new or unfamiliar software. Move your BTC to a fresh wallet first. Nobody needs your seed to “claim” anything.

Step 1: get a signer that supports XBT

Our ranking today, best first. The full device table and per-device notes follow.

Our pick

Paperclip Krux

Ready-made, $70, and it only signs the XBT kind, so a slip can’t produce a signature that’s valid on BTC. No Wi-Fi, no Bluetooth, no battery. Signs by QR code or microSD. Its firmware updates are checked by the device itself. Works with Shrike.

Catch: out of stock when we checked on November 15 (the shop offers a restock alert). Its firmware is weeks old.

Krux setup notes

Best DIY

SeedSigner + XBT firmware

About $60 in Raspberry Pi parts, and xbt.live’s pick for savings. It stores nothing and signs by QR code. Its screen names the signature type (Unified sighash (0x21)), so you can see you got replay protection. The XBT build has signed a real mainnet transaction on hardware.

SeedSigner setup notes

Only if it’s a spare

Trezor or Coldcard, re-flashed

Unofficial firmware exists. Flashing a Trezor erases it; a flashed Coldcard warns on every boot and loses its green “genuine” light permanently. Never flash the device that holds your bitcoin. Only Trezor’s Model One build has been run on real hardware.

Trezor notes Coldcard notes

Don’t wait for the big brands. Coinkite (Coldcard) closed a request to add XBT signing with “We only support bitcoin.” SatoshiLabs (Trezor) closed one too, saying it falls outside what it accepts and that its coin rules exclude coins whose addresses look like Bitcoin’s. We found no plans from Ledger, BitBox, Blockstream, Keystone or Foundation.

Which hardware wallets support XBT?

“Supported” means the device can sign with XBT’s replay protection (SIGHASH_UNIFIED, hash type 0x21): valid on XBT, rejected by BTC. Checked November 15, 2026. Tap a device name for details.

DeviceXBT statusSource
Paperclip KruxSupported XBT-only devicekrux-blake2b
SeedSignerCommunity firmwareprivkeyio/seedsigner
Trezor (One, T, Safe 3/5/7)Community firmware stock: Noprivkeyio/trezor-firmware
Coldcard (Mk4, Mk5, Q)Community firmware stock: Noprivkeyio/cc-firmware
Bitkey (Lazarus Key app)Unofficial app phone key adds the protectionlazarus-key
LedgerNot supported yetBitcoin app notes
BitBox02Not supported yetchangelog
Blockstream JadeNot supported yetchangelog
Keystone 3Not supported yetchangelog
Passport (Core)Not supported yetreleases
Passport PrimeUnknownnot checked
Krux on other devicesUnknownKrux notes
SeedSigner + Satochip cardUnknown untested pre-releaseprivkeyio/seedsigner

Cross-checked against Shrike’s docs (“Stock firmware from any manufacturer cannot produce SIGHASH_UNIFIED yet”), xbt.live’s wallet list (last checked by xbt.live November 11, 2026) and the awesome-bitcoin-blake hardware list.

A stricter view: BitcoinBIP110.org, the project’s reference site, says “There are no hardware wallets that currently support Bitcoin BIP110” and advises waiting until a hardware wallet maker publishes official support. By that standard, only Paperclip Krux comes from its own maker, and that site doesn’t list it. Every option here is community-built. Treat them as experimental and start small.

“Not supported” doesn’t mean your XBT is lost. If you held bitcoin before August 8, 2026, your XBT sits at the same addresses, under the same keys, as your BTC, so any device still holds those keys. What a stock device can’t do is make the protected signature. Shrike’s docs say an unmarked device “still signs, but produces signatures with no replay protection”, and a legacy-signed spend of pre-split coins can be replayed onto BTC. The safe order: move your BTC to a new wallet first. After that the old device only guards XBT, and you can send that XBT to a new seed on a supported signer.

Device-by-device details

Paperclip Krux: supported (XBT-only)
  • What it is: a Yahboom K210 with a touchscreen and camera, running Connor’s Lab’s Krux fork. No Wi-Fi, Bluetooth or battery; power it from a USB power bank or wall adapter. $70, paid in XBT. Out of stock on November 15, 2026.
  • How it signs: the shop says the firmware “requires unified-sighash transactions and rejects incompatible signing requests rather than silently switching modes.” Current firmware: v26.09.0-xbt.2 (prerelease, October 20, 2026), reproducible, with 1,220 regression tests passing.
  • Update first: devices on v26.09.0-xbt.1 or older need one USB install of xbt.2 to turn on signed microSD updates (install guide). After that, the device checks each update’s signature itself.
  • New seed: at the start screen choose New Mnemonic, then camera, words, D6 or D20 dice. Dice are recommended: 99 D6 rolls or 60 D20 rolls for 24 words.
  • Optional encrypted copy on flash, microSD or a QR. It doesn’t include a BIP39 passphrase and doesn’t replace your paper backup.
  • Pair: on the Krux open Extended Public Key and export the XPUB or ZPUB as a QR. In Shrike, choose Krux when adding the keystore.
  • Check addresses: Address → Scan Address. Sign: Sign → PSBT → Load from camera, check the details, then Sign to QR code.

Sources: Paperclip Shop listing; krux-blake2b README, seed storage, generating a mnemonic, coordinator and signing; xbt.live write-up.

SeedSigner: supported via community firmware
  • Firmware: privkeyio’s unofficial build, v0.8.7-unified-sighash.6 (September 5, 2026). It isn’t a SeedSigner project release. Images: pi0 for Pi Zero v1.3/Zero W, pi02w for Zero 2 W/Pi 3B, pi2, pi4. The release says it signed a mainnet transaction carrying the opt-in on real hardware.
  • Install: download the image plus SHA256SUMS, SHA256SUMS.asc and the signing key. Verify before flashing (look for Good signature from "Kyle Santiago" and fingerprint A47D 99B6 DB0D 715D 40C5 9A20 23AE 8A8E A7E2 4E38). Then write the image to a microSD card with Balena Etcher or Raspberry Pi Imager; copying the file onto the card does nothing.
  • New seed: Tools → New seed (dice), choose 24 words, roll 99 times. Write the words down, then choose Verify and finish when it shows Backup Verified.
  • No PIN, no storage: SeedSigner forgets the seed at power-off. You load it from your paper (or a SeedQR you make) each time, so guard that backup.
  • Pair: Export xpub → Native SegWit → Sparrow, then scan it into Shrike as an airgapped hardware wallet.
  • Sign: the approval screen reads Unified sighash (0x21) or Standard sighash (0x01). Only approve 0x21. It refuses a transaction it can only partly sign.

Sources: release notes, README and source menus; xbt.live cold storage guide.

Trezor: community firmware only (stock not supported)
  • Firmware: privkeyio’s unofficial fork, release unified-sighash.2 (September 4, 2026), Bitcoin-only. Match the file to your model: Model One T1B1 (1.14.2); Model T T2T1, Safe 3 T3B1, Safe 5 T3T1, Safe 7 T3W1 (2.12.5).
  • Tested: only the Model One has been run on real hardware, including a signed mainnet transaction. The others were tested only on the emulator.
  • Costs: installing it erases the device, and so does going back to official firmware. It shows an unofficial-firmware warning and a fingerprint on every boot, permanently. Shrike’s docs add that it voids the warranty and can brick the device.
  • Software: Trezor Suite can’t ask for the XBT signature. Shrike can, over USB, through its lark library. Keep Shrike and the firmware updated together: a mismatched pair refuses to opt in.
  • New seed: after flashing, set it up as a brand-new wallet and write down the new words.
  • SatoshiLabs closed the request to add this upstream on October 6, 2026.

Sources: release notes; Shrike: hardware wallet firmware; trezor-firmware PR #7817.

Coldcard: community firmware only (stock not supported)
  • Firmware: privkeyio’s unofficial fork v5.6.3U for Mk4/Mk5 (-mk-coldcard.dfu) and 1.5.3QU for Q (-q1-coldcard.dfu), October 2, 2026, built on Coinkite’s 5.6.3 / 1.5.3Q. It signs the XBT message when the PSBT asks for it. No taproot.
  • Costs: it’s signed with Coldcard’s public development key, so every boot shows a warning and a forced delay, the green “genuine” light never comes on, and installing needs your main PIN. The release says: “Do not put this on a device holding funds you cannot afford to lose access to.”
  • Seed warning: Coinkite’s advisory, carried in the fork’s README, says seeds made on firmware from 2021 to July 2026 had poor entropy and are only trusted from 5.6.0 (Mk4/Mk5) or 1.5.0Q (Q) onward. Make your XBT seed on the fork itself, and add dice rolls.
  • Pair: microSD or QR (Q), as an airgapped hardware wallet in Shrike, then tick Replay protection.
  • Coinkite closed the request to add this upstream on September 3, 2026: “We only support bitcoin.”

Sources: release notes, README; Coldcard PR #807; Shrike: hardware wallet firmware.

Bitkey with Lazarus Key: unofficial app, with a catch
  • What it is: a fork of Block’s Bitkey app for Android (NFC), installed by sideloading an APK and checking its checksum. The Bitkey device isn’t re-flashed.
  • The catch: its own notes say “The Bitkey hardware cannot produce” the XBT signature. In Bitkey’s 2-of-3 setup, the phone key adds it, which protects the whole transaction. The site also says not to rely on it alone for coins from before block 961,640 until its next release.
  • Other limits: a new wallet has to be created through Block’s servers once. The app trusts its Electrum server rather than checking BLAKE2b proof of work. It uses a paper Emergency Exit Kit instead of seed words. xbt.live hasn’t tested it, and Lazarus is an xbt.live sponsor.

Sources: lazarus-xbt.xyz/key; XBT.md; xbt.live wallets.

Ledger: not supported yet

We found no XBT app or firmware. Ledger’s Bitcoin app release notes (through 2.6.0) don’t mention it, and neither does anything else on Ledger’s GitHub. On August 9, 2026, before XBT’s opt-in signature existed, Ledger warned users not to claim or move BIP-110 coins because of replay risk (as reported by Lookonchain). A Ledger can still hold the keys to pre-split XBT, but it signs only the legacy, replayable way. Use the safe order in the callout above.

Sources: Ledger Bitcoin app changelog; Ledger Academy: BIP-110; Lookonchain report.

BitBox02, Jade, Keystone, Passport and others
  • BitBox02: not supported yet. No mention in the firmware changelog (latest v9.27.1, August 31, 2026) or its issue tracker.
  • Blockstream Jade: not supported yet. No mention in the changelog (latest 1.0.41, August 22, 2026) or its issue tracker.
  • Keystone 3: not supported yet. No mention in the changelog (latest 3.2.2, November 10, 2026) or its issue tracker.
  • Foundation Passport (Core / Founder’s Edition): not supported yet. The latest release, v2.3.11, is from December 2025, before the split. Passport Prime: unknown; we didn’t check its release notes.
  • Krux on other devices (M5StickV, Amigo, etc.): unknown. Upstream Krux (26.09.0) doesn’t mention XBT, and the XBT fork publishes builds only for the Yahboom K210.
  • SeedSigner with a Satochip smartcard: unknown. privkeyio publishes a pre-release that it says “has not been run on card hardware.”
  • No community XBT firmware was found for any of these. Shrike’s docs list builds only for Coldcard, SeedSigner and Trezor.

Step 2: make a brand-new seed on the device

  1. Get the firmware only from its official page (links above) and verify the signed checksums before installing. Paperclip Krux comes ready to use.
  2. Choose “new seed”, never “restore”. Never type or load the seed that guards your BTC. A separate seed keeps the two coins apart for good.
  3. Use dice for randomness where the device offers it: 99 six-sided rolls for 24 words.
  4. Write every word, in order, on paper. Copy it to steel later if this is savings. No photos, no cloud, no typing it anywhere.
  5. Verify the backup with the device’s check (SeedSigner: Verify), or reload from your paper and confirm the wallet fingerprint matches.
  6. Lock it: set a PIN or password if the device has one (Trezor, Coldcard), and label the device “XBT only”. SeedSigner has no PIN and keeps nothing; Krux’s encryption key only protects a saved copy.

Step 3: pair it with Shrike

  1. Install Shrike and connect it to your node. Shrike ships with no public servers. It needs your own Bitcoin Knots node (v29.4.1.knots20260508 or later; use the newest release), connected directly or through your own BLAKE2b-aware Electrum server in front of that node, under Settings → Server. Follow Set up Shrike, steps 1–5, then come back here.
  2. Create a new wallet and pick the keystore type: Airgapped Hardware Wallet for QR or microSD devices (Krux, SeedSigner, Coldcard), or Connected Hardware Wallet for USB (a Trezor on the XBT firmware).
  3. Import the device’s public key (the xpub export in the device notes above). Before going further, check that the wallet fingerprint in Shrike matches the one on the device. Shrike can now see your balance but can’t spend on its own.
  4. Mark it: wallet settings → keystore tab → tick Replay protection. Shrike can’t detect firmware, so it’s off until you tick it. Only tick it for a supported device.

Step 4: test receive and test send, then move the rest

  1. Receive: in Shrike’s Receive tab, click Get Next Address and confirm the same address on the device. Send a small amount to it.
  2. See it arrive in Shrike and on the XBT explorer mempool.guide.
  3. Send a small amount back to another address in the same wallet. Before signing, Shrike’s send screen must say replay protected. On the device, check the amount, the address and, where shown, the hash type 0x21.
  4. Broadcast and wait for confirmation. If the device says signing failed, nothing was sent and your coins haven’t moved (Shrike FAQ).
  5. Move the rest. Your XBT is now in your own custody.

No hardware wallet? Use Shrike on a computer

You can self-custody XBT today with Shrike alone. It makes and holds the seed on your computer and signs with replay protection by default; a wallet holding its own key needs no mark. You still need your own Knots node. That’s fine for getting started or for smaller amounts, but the keys sit on a computer that goes online.

Set up Shrike step by step

Sources for this page, all checked November 15, 2026: the links in each device section; Shrike’s firmware, replay protection, quick start, node and FAQ pages; BitcoinBIP110.org users guide; Sparrow Quick Start (keystore types); xbt.live cold storage guide. Listing is not an endorsement.

← Your path in detail Next: Set up Shrike → Back to Start here

Not financial or tax advice. This guide is education only. Splitting, selling or trading fork coins may be a taxable event where you live; talk to a tax professional. The XBT wallets and firmware mentioned are new, community-built and unaudited. Test with small amounts; you are responsible for your own keys. We never ask for seeds, keys or money. See sources.