Wallet specification / research record
COLDCARD Q
A Bitcoin-focused signer with a keyboard, QR scanner and microSD options. Read the current security advisory before any setup or recovery decision.
- Format
- Hardware signer
- Asset category
- Bitcoin
- Prepared by
- WalletClause research desk
- Source check
- 9 November 2026
Documented configuration
| Attribute | Documented approach |
|---|---|
| Key location | Dedicated device |
| Signing interface | LCD + physical keyboard |
| Connection | QR, microSD, USB-C; NFC |
| Asset scope | Bitcoin |
| Backup approach | Seed backup; advanced options by firmware |
| Primary workflow | Compatible coordinator, such as Sparrow |
Detailed research
4 notes / expand or collapse eachRead the security status first
The official security status explains a July 2026 seed-generation incident. It includes Q in the affected scope and distinguishes current firmware from seeds created on affected releases. Firmware updates correct future generation but do not repair an affected existing seed. Follow the linked migration guidance rather than improvising from this summary.
We intentionally do not freeze a recommended version number here. Open the current status and verify the signed download using the manufacturer’s procedure. This profile is not an incident response service.
What the documentation establishes
Q has a physical keyboard, LCD, QR scanner and two microSD slots. Coinkite describes battery-powered operation, USB-C and NFC options. It can work with compatible coordinator software rather than a mandatory proprietary companion account. “Air-gapped” describes a chosen transfer workflow, not a promise that every possible configuration has no data connection.
The decision that matters
Draw your intended transaction path before buying: where the request is created, how it reaches the signer, how you review it and how the signed result returns for broadcast. A QR or storage-card transfer creates a boundary to inspect. It does not remove the need to read the device screen.
Extra controls also require extra records. Someone who rarely signs should consider whether they can reproduce the workflow after six months away. Keep public wallet configuration separate from secrets, and document the coordinator and account type you chose.
Questions to resolve before use
- Have you read the current advisory and determined whether an existing seed needs migration?
- Can you verify the current firmware download?
- Which transfer path will you consistently use?
- Can you recover the wallet configuration as well as its signing secret?
Advanced features increase the number of decisions to understand. Choose them to address an identified need, and practice using an unfunded setup before relying on them. WalletClause has not independently audited the remediation or tested this hardware.
Sources & scope
Source-based desk research. Checked . Product specifications and documentation can change. No hands-on testing or independent security audit is claimed.