A separate signer.
Your hardware key is a separate part of your custody. Choose and configure it with the same care you give the wallet itself.
Device names below are references, not a compatibility certification. Support depends on the model, firmware, connection method, and Coinhost beta build. Confirm the combination with support before buying a device or starting setup.
Before pairing
Initialize and back up your signer using its manufacturer's instructions. Follow the pairing route provided for your Coinhost beta build. If it uses a desktop bridge, verify the supplied address before connecting; do not follow unsolicited pairing links.
Pairing uses public wallet information, such as an extended public key and fingerprint. A public-key export is different from a seed or private-key export. Never enter recovery words into the Coinhost website or send them to support.
Trezor
Check the exact model and firmware with the beta team. Follow the manufacturer's setup and backup instructions, and review any wallet policy or address confirmation the device presents. Resolve unexpected warnings before approving.
Ledger
Confirm the device model, firmware, Bitcoin app, and pairing route required by your beta build. If the device asks you to register a multisig policy, verify the threshold and signers before approving it. Report signing failures with the error text and versions; never include recovery words.
TAPSIGNER
TAPSIGNER is an NFC signing card without a transaction display. It cannot provide the independent on-device address check available on a signer with a screen. Understand that trade-off and follow its backup instructions before using it. The manufacturer's guide explains the card and its encrypted backup.
BitBox
Confirm your exact model and Coinhost integration before setup. Complete the manufacturer's device and backup checks, then use the supported pairing instructions for your beta build.
QR and offline signing
A device accepting QR codes does not by itself establish compatibility. The wallet and signer must agree on the public-key export, signing policy, network, and transaction format. Do not assume a QR or removable-storage workflow is available in the current beta; check it before choosing a signer.
Before every approval
- Check the intended network, destination, amount, and fee.
- Compare transaction details on the signer's own display where available.
- Stop if a key fingerprint, wallet policy, or address differs from what you expect.
- Use test coins for beta rehearsals, including recovery.
For help, include your device model, firmware, beta version, and a description of the problem. Keep seed phrases, PINs, passwords, and private keys out of support messages.