KeepKey · Solana
Solana on KeepKey
KeepKey natively signs Solana (SOL) and SPL tokens on-device — in open-source firmware 7.14.1. Full dApp support via the Solana Wallet Standard (Jupiter, Tensor, Raydium, and more), running on enclave-free open hardware. Not Bitcoin-only, not a Trezor fork.
Capabilities
Solana support at a glance.
| Capability | KeepKey | Detail |
|---|---|---|
| Native SOL signing (on-device) | Yes | Implemented in open-source firmware 7.14.1 |
| SPL token support | Yes | SPL token transfers signed on-device |
| Solana dApp connection | Yes | Wallet Standard (navigator.wallets) + legacy window.solana |
| On-device transaction approval | Yes | Verify and approve every transaction on the device screen |
| EVM coexistence | Yes | EIP-6963 — no window.ethereum hijack, no MetaMask masking required |
| Closed-source secure element | No | Enclave-free: fully open, auditable MCU + published hardware schematics |
How it works
From dApp to device, verifiably.
01
Wallet discovery
The KeepKey browser extension registers as a Solana wallet via the Wallet Standard (window.navigator.wallets) — the same mechanism Phantom and Solflare use — and also exposes a legacy window.solana provider for older dApps.
02
EVM coexistence
For Ethereum and EVM chains, KeepKey is announced via EIP-6963 multi-injected provider discovery, so it coexists with other wallets without hijacking window.ethereum. No MetaMask masking required.
03
Local bridge
Transaction payloads are routed through the local KeepKey bridge (localhost:1646) to the connected device — no third-party middleware between the dApp and your hardware.
04
On-device approval
Every Solana transaction is shown on the KeepKey screen and must be physically approved on the device before it is signed and broadcast. Keys never leave the hardware.
dApps
Full Solana dApp support.
KeepKey connects to any Solana dApp built on the Wallet Standard (the @solana/wallet-adapter registry) — and to older dApps via the legacy window.solana provider. Connect, then approve every transaction on the device screen. High-intent dApps people use with KeepKey include:
Logos and names belong to their respective projects. Listing indicates wallet-standard compatibility, not endorsement or affiliation.
Security model
Enclave-free. Fully auditable.
Unlike hardware wallets that rely on a proprietary, NDA-locked secure element, KeepKey runs exclusively on a fully open-source, general-purpose microcontroller. Every piece of the device's hardware logic and firmware — including the Solana signing path — can be compiled, reviewed, and audited publicly on GitHub. There is no closed-source black box between you and your Solana keys.
FAQ
Solana on KeepKey, answered.
Does KeepKey support Solana?
Yes. KeepKey natively signs Solana (SOL) and SPL token transactions on-device. Solana signing is implemented in the open-source firmware (7.14.1) — keys are generated and held offline and every transaction is approved on the device screen.
Can I use KeepKey with Solana dApps like Jupiter or Tensor?
Yes. The KeepKey browser extension registers as a first-class Solana wallet via the Wallet Standard (window.navigator.wallets) — the same discovery mechanism Phantom and Solflare use — and also exposes a legacy window.solana provider for older dApps. Solana dApps see KeepKey as a connectable hardware signer.
Is KeepKey only for Bitcoin and EVM chains?
No. That describes older firmware. As of firmware 7.x, KeepKey natively signs Bitcoin, Ethereum (and all EVM chains via EIP-155), Solana, TRON, TON, XRP, Cosmos, THORChain, and Maya, plus any ERC-20 token. Solana, TON, and TRON were added in the 7.x multi-chain expansion.
Does KeepKey use a closed secure element for Solana?
No. KeepKey runs on a fully open-source, general-purpose microcontroller with no proprietary, NDA-locked secure element. 100% of the device firmware and hardware schematics are published and auditable on GitHub — Solana keys are protected by open, verifiable code rather than a closed black box.
How does KeepKey avoid conflicting with other wallet extensions?
For EVM, KeepKey uses the EIP-6963 multi-injected provider standard, so it is discovered alongside other wallets without hijacking window.ethereum. For Solana it registers through the Wallet Standard registry. No MetaMask masking is required for modern dApps.
Get the Hardware Wallet You Can Verify
Open-source firmware and hardware schematics. Bitcoin, Ethereum, Solana, TON, TRON, Cosmos, and all EVM chains. Built-in decentralized swaps. Premium aluminum. All for $49.95.