Hardware wallet signing keeps private keys on a dedicated device. Your application builds the transaction, the device shows what is being signed, the user confirms with a physical button, and only the signature leaves the device. Even if the computer or phone is compromised, an attacker cannot extract the key. For wallets, treasury tools and DeFi applications with serious amounts at stake, hardware support is often a requirement.
Integration Routes
- Ledger: USB or Bluetooth, from browsers through WebHID/WebUSB and from desktop or mobile apps through Ledger's SDKs. Each chain runs as an app on the device.
- Trezor: through Trezor Connect, which handles device communication and user prompts.
- Air-gapped QR signers such as Keystone: the unsigned transaction is shown as a QR code, scanned by the device, and the signature comes back as a QR code. No cable, no Bluetooth.
- Through other wallets: many users connect a hardware wallet via MetaMask, Rabby or WalletConnect; your app then needs to handle the slower, device-confirmed flow correctly.
Clear Signing Instead of Blind Signing
A hardware wallet is only as safe as what its screen shows. If the device displays a hash instead of readable fields, users sign blindly. Using EIP-712 typed data, and providing metadata so devices can show contract calls in plain language, lets users verify the recipient, amount and action on the device itself. See blind signing prevention.
Details That Matter
- Derivation paths: different wallets derive accounts on different paths. Supporting the common ones avoids "my funds are missing" support tickets.
- Timeouts and retries: a user may take a minute to confirm, or the device may lock; the app must wait and recover gracefully.
- Transaction size: complex calls can exceed what a device displays or accepts in one go, so test with real devices, not just emulators.
- Multisig: hardware wallets work well as signers on a multisig, combining physical key security with shared approval.
Frequently Asked Questions
Which hardware wallets should we support?
Ledger and Trezor cover most users; QR-based signers matter for users who want fully air-gapped storage. The right mix depends on your audience.
Can hardware signing work in a mobile app?
Yes, through Bluetooth for devices that support it, or QR codes for air-gapped signers.
Does hardware signing work on Solana and EVM chains?
Yes. Each chain needs its own device app and signing format, which the integration has to support.
Who owns the code?
Ownership of the source code is set out in the contract, and the code can be fully yours, including documentation and tests.
Part of our crypto wallet development work, alongside desktop, mobile and browser extension wallets.
Add Hardware Wallet Support
Tell us which devices and chains your users need. We will build a signing flow that is secure and still pleasant to use.