If you only hold Bitcoin, why is your signing device running code written for coins you'll never own?
That's not a philosophical question.
Because multi-coin firmware has to maintain its own protocol logic, cryptographic signing rules, and transaction construction for every coin it supports.
Each addition brings more code that needs to be reviewed, maintained, and kept secure, whether you use those coins or not. You're carrying that overhead by default.
Keystone's BTC-only firmware serves as the best alternative. Not a trimmed version of the multi-coin build, but a completely separate codebase written from scratch for Bitcoin.
When the codebase is smaller and purpose-built, security researchers can audit more of it and audit it properly. Fewer lines of code means fewer places for vulnerabilities to go unnoticed between review cycles, which makes for a structurally sounder security foundation overall.
BTC-only users also get access to advanced Bitcoin features that multi-coin firmware doesn't offer.
All three address formats:
- P2PKH (legacy), P2SH-P2WPKH (nested segwit), and P2WPKH (native segwit).
- PSBT (BIP-174) for air-gapped transaction signing via QR codes.
- Native multisig support, coinjoin, and the ability to connect your wallet to your own Bitcoin node for fully independent chain verification.
Plus, the wallet compatibility covers Sparrow, Electrum, BlueWallet, Specter, and everything a serious Bitcoin setup actually runs on.
Switch to BTC-only, and you're not giving anything up.
You're getting a leaner security foundation and a deeper Bitcoin feature set in the same move.