Two different trust models to start with. Real hardware. The trade-offs that matter more than a ranking number.
A touchscreen wallet with a public-code approach. Inspect the architecture and recovery design before choosing it.
Publicly reviewable design is a priority.
Review the physical-security disclosure and the manufacturer's response.
Direct manufacturer link. No affiliate commission is active. Check current specifications, price, seller and recovery design before purchase.
A screen-first Ledger device. Compare its software ecosystem with the components of its trust model you accept.
You prefer the Ledger companion ecosystem.
Check closed components and optional recovery-service trust.
Direct manufacturer link. No affiliate commission is active. Check current specifications, price, seller and recovery design before purchase.
Nano Gen5, Black. The link specifies the Ledger Official seller; verify that seller, the model and the condition before paying. Availability and the displayed seller can change.
Check price on AmazonPaid link. As an Amazon Associate I earn from qualifying purchases. Manufacturer reseller directory.
Trezor Safe 7: we have not verified an exact US Amazon offer. Use the manufacturer link above, rather than buying a different model by mistake. Still researching? Compare learning resources
Code openness, display, backup, charging and connection.
A wallet protects signing keys. Your recovery plan needs its own protection. Match any metal backup to your wallet's exact backup format.
Pictured: Trezor Keep Metal 20-word. Product-specific compatibility required.Which loss is more plausible for you: backup loss, backup theft, blind signing, device compromise, physical extraction, software error, or an heir who cannot recover the funds?
Control: Geographically separate durable backups and a tested restore
Limit: More copies increase theft and coercion exposure.
Control: Threshold shares, a well-understood passphrase, or controlled physical separation
Limit: A forgotten passphrase or unavailable share can be indistinguishable from theft loss.
Control: Trusted-display verification and clear signing for the exact supported action
Limit: Unsupported contracts may still appear as hashes or opaque data.
Control: Official purchase path, authenticity checks, firmware verification, and a newly generated backup
Limit: Authenticity checks reduce risk; they do not prove every component or build is defect-free.
Control: Secure-element design, PIN policy, passphrase or share separation, and realistic possession assumptions
Limit: Published attacks differ in cost, prerequisites, destructiveness, scope, and whether key material is actually reachable.
Control: Plain-language inventory, tested instructions, role separation, and periodic rehearsal
Limit: A secret plan that heirs cannot locate or execute is not a recovery plan.
No. It does not stop you approving a malicious transaction, exposing recovery material or losing access without a recovery plan. Inspect the exact action being signed.
Start with the manufacturer or verify an authorized seller, authenticity procedure, shipment and return policy. Never use a device supplied with a pre-written seed phrase.
July assessment. Manufacturer claims, laboratory findings and editorial interpretation are kept separate.
Review boundary: Read both the independent TROPIC01 disclosure and Trezor's response. Decide whether the required physical access, laboratory capability, layered key isolation, and unpatchable chip issue fit your threat model. This entry is dated 2026-07-14; it is not a current security clearance.
Trezor describes Safe 7 as an open-source device with two secure elements plus an MCU, a large touchscreen, USB-C, Bluetooth, full iOS support, and multi-share backup support.
Ledger Donjon reported a laser fault-injection path against TROPIC01 firmware verification and later attack stages after invasive chip access and arbitrary-code prerequisites.
Trezor says Safe 7 uses three independent security layers, does not store keys or backups on TROPIC01, and that the disclosed path does not expose customer funds remotely.
The disclosure is not a remote exploit and requires specialist physical work, but the hardware issue cannot be patched. It belongs in the purchase decision rather than being dismissed or generalized into total compromise.
Manufacturer claims; availability, compatibility, and firmware state can change.
Manufacturer comparison, not an independent security ranking.
Manufacturer interpretation of a disclosure affecting a component used in its product.
Component-level invasive laboratory work; it does not by itself establish remote compromise or extraction of Safe 7 user keys.
Vendor advisory; product-level impact depends on the complete architecture and threat model.
Review boundary: Document whether Ledger Recover will remain disabled or be accepted. Review the service terms, identity process, fragment model, and jurisdictional trust before subscribing. This entry is dated 2026-07-14; it is not a current security clearance.
Ledger lists a 2.8-inch E Ink touchscreen, USB-C, Bluetooth, NFC, Secure Element protection, broad asset support, and an included PIN-protected Recovery Key.
Ledger states that Ledger apps, SDKs, and several components are open while parts of Ledger OS and low-level code cannot be fully open because of secure-element supplier agreements.
Ledger Recover is an optional subscription that encrypts and divides recovery material into three fragments, with two required for identity-verified recovery.
The optional service is not forced, but it creates a different trust model. Partial reviewability is a hard mismatch for users whose policy requires fully inspectable firmware.
Manufacturer shop page; price, stock, bundles, and specifications can change.
Manufacturer announcement, not an independent audit; price and availability are time-sensitive.
Ledger's own description of its source-availability boundary.
Manufacturer overview; users must read current device and service terms.
Legal terms can change and differ by jurisdiction; not a technical audit of service providers.
Review boundary: Verify the exact network in the current support matrix. Do not infer Solana, XRP, token, NFT, or contract support from general EVM compatibility. This entry is dated 2026-07-14; it is not a current security clearance.
BitBox describes open-source firmware and app code, reproducible builds, a dual-chip architecture, an EAL6+ secure chip, and microSD-based backup.
Nova supports desktop, Android, and iOS through USB-C and optional Bluetooth Low Energy that can be disabled.
Its narrower first-party asset scope is a benefit only when it matches the portfolio. It is a hard mismatch for unsupported networks, not a reason to improvise with an unverified integration.
Manufacturer overview, not an independent security assessment.
Manufacturer claims; exact compatibility and availability can change.
Manufacturer explanation, not a complete independent evaluation of every component or build.
Compatibility is version-dependent and does not guarantee every token or contract action is decoded.
Review boundary: Complete a full PSBT round trip and recovery rehearsal before funding. Bitcoin-only and air-gapped do not compensate for an owner who cannot verify files, addresses, fees, change, or backups. This entry is dated 2026-07-14; it is not a current security clearance.
Coinkite describes Mk5 as a Bitcoin-only signer with dual secure elements, open and reproducible firmware, microSD, NFC, USB-C, multisig, and advanced transaction controls.
The narrow scope reduces unsupported-network ambiguity, but the advanced workflow transfers more responsibility to the owner. A mismanaged PSBT or backup remains an operational failure.
Manufacturer claims; users must verify current firmware, companion compatibility, and workflow.
Manufacturer description, not a complete independent product audit.
Specifications may change by hardware revision and do not prove safe user operation.
Price, inventory, shipping, and bundles are time-sensitive.
Review boundary: Confirm the exact multi, Bitcoin-only, or Cypherpunk firmware, companion version, network, derivation path, QR format, and decoded display before moving funds. This entry is dated 2026-07-14; it is not a current security clearance.
Keystone lists a 4-inch touchscreen, QR air-gapped signing, three secure elements, open-source firmware, Shamir recovery, fingerprint support, and three wallet profiles.
Keystone publishes separate multi-coin, Cypherpunk, and Bitcoin-only firmware and claims support for more than 5,500 assets through more than 45 software wallets.
Breadth is integration-dependent. Every companion and transaction type must be verified independently; asset-count marketing is not clear-signing evidence.
Manufacturer claims; price, stock, and compatibility can change.
A release registry does not independently prove build reproducibility or transaction correctness.
Repository visibility does not prove that a shipped device or binary exactly matches reviewed source.
Vendor-listed support is integration-dependent and is not proof of clear signing for every action.
Review boundary: Read the Donjon disclosure and Tangem response, then document acceptance of the no-display model, closed immutable firmware, destructive physical attack requirements, and inability to patch cards already in circulation. This entry is dated 2026-07-14; it is not a current security clearance.
Tangem describes an EAL6+ card, seedless multi-card backup or BIP39 mode, broad mobile asset support, audited firmware, and an immutable design.
Tangem states that card firmware is closed, uses a security-through-obscurity approach, and cannot be updated after manufacture.
Ledger Donjon reported an invasive laser-fault method that can reset the access code on one card without the original code or backup card after specialist physical work.
Tangem says the destructive attack is expensive, non-scalable, requires prolonged possession, and does not reveal who owns a card or what assets it controls.
The finding is not remote and does not justify a broad panic claim. It is still material for a stolen-card physical threat model, and affected immutable cards cannot receive a firmware patch.
Manufacturer claims and audit summaries; scope and current physical disclosures require separate review.
Manufacturer comparison, not an independent security ranking.
Manufacturer explanation of a non-public firmware design; users cannot independently review the complete source.
Specialist destructive physical attack; not a remote exploit, scalable theft method, or proof that every Tangem use case is compromised.
Manufacturer interpretation of an independent finding affecting cards already in circulation.
| Device | Asset scope | Source boundary | Recovery |
|---|---|---|---|
| Trezor Safe 7 | Broad multichain support; verify the exact asset and companion before use | Open / reviewable | 12-, 20-, or 24-word and multi-share backup options |
| Ledger Nano Gen5 | Broad multichain support through Ledger's app ecosystem; verify exact transaction decoding | Partially reviewable | Recovery words, included offline Recovery Key, and optional paid Ledger Recover service |
| BitBox02 Nova | Native app focus on BTC, LTC, and ETH; selected EVM and Cardano flows use third-party companions; no native SOL or XRP support | Open / reviewable | microSD backup plus optional BIP39 recovery words |
| COLDCARD Mk5 | Bitcoin only | Open / reviewable | Bitcoin recovery words and advanced backup or multisig workflows |
| Keystone 3 Pro | Vendor states 5,500+ assets and 45+ software-wallet integrations; exact support must be checked | Open / reviewable | BIP39 and Shamir options, passphrases, and up to three wallet profiles |
| Tangem Wallet 2.0 | Broad vendor-listed multichain support through the mobile app; verify exact networks and tokens | Closed firmware | Seedless backup cards or optional BIP39 recovery words |
Model names, prices, stock, supported assets, companion-wallet compatibility, firmware versions, security advisories, and transaction-decoding coverage can change. Recheck the exact product and intended network on official pages immediately before purchase or signing. A supported asset count does not prove that every transaction will be decoded clearly on the trusted display.
Do not enter real recovery words into this website, a support chat or an online checker.
This tool uses the July model. Any product-specific mismatch or failed recovery gate blocks the process. A first-place result is not a current buy recommendation.
Strong fit for broad asset support, a large trusted display, and multi-share recovery, provided the buyer accepts the disclosed TROPIC01 physical-lab issue and Trezor's layered response.
Matched: Asset scope, Use case, Platform, Connection, Transparency preference, Recovery style, Trusted display. Continue to the product disclosure and all six hard stops.
A buyer who values open design, a large display, full iOS support, and broad asset coverage.
A household prepared to rehearse a multi-share recovery and document inheritance.
A buyer who will not accept a product carrying a new, hardware-level physical-lab disclosure.
A minimalist Bitcoin-only user who does not need wireless, battery, or broad ecosystem features.
Read both the independent TROPIC01 disclosure and Trezor's response. Decide whether the required physical access, laboratory capability, layered key isolation, and unpatchable chip issue fit your threat model.
Buy only from the manufacturer or an authorized seller and complete every authenticity check before setup.
The device creates a new backup during setup; no prefilled words, PIN, or supplied recovery sheet is accepted.
A restore drill succeeds on a spare or compatible device with a tiny test amount before material funding.
The exact receive address, amount, network, fee, and human-readable transaction are verified on a trusted device display.
The vault address never connects to random dApps; active signing uses a separate, intentionally limited wallet.
A written inheritance and emergency plan exists, and backups are geographically separated without exposing one complete secret.
Passing these checks does not certify the wallet as safe. It only clears the minimum process for a tiny recovery and signing test.
Keep routine experiments separate from long-term custody. Hardware protects keys, not bad approvals.
Useful for: Useful for transaction simulation, approval visibility, and connecting supported hardware wallets in EVM workflows.
Boundary: It is software on a general-purpose device, not a replacement for a hardware signing device or an isolated vault address. Simulation and warnings can be incomplete.
Useful for: Useful for PSBT, hardware-wallet coordination, multisig, UTXO control, fee control, watch-only monitoring, and Tor workflows.
Boundary: It is a coordinator and interface, not the vault hardware itself. The computer, node connection, descriptors, change handling, and backup process still require verification.
Supports: Offline savings, backups, software updates, multisig, smaller active balances, and inheritance planning.
Limit: General guidance, not a product test or guarantee against every operational failure.
Supports: Mnemonic lengths, entropy mapping, checksum, seed derivation, and optional passphrase behavior.
Limit: A technical interoperability specification, not an endorsement of any backup storage or passphrase process.
Supports: Threshold mnemonic shares and two-level group structures.
Limit: Compatibility and implementation quality must be verified for each device and companion.
Supports: Wallet, phishing, approval, transaction, and seed-phrase risk guidance for Ethereum users.
Limit: General ecosystem guidance, not a hardware-wallet comparison.
Supports: The need for human-readable transaction descriptions and open descriptor standards such as ERC-7730.
Limit: An initiative and standardization effort; clear signing depends on wallet and transaction support and cannot decode every action automatically.
Supports: Manufacturer specifications for display, connectivity, architecture, recovery, platforms, and asset support.
Limit: Manufacturer claims; availability, compatibility, and firmware state can change.
Supports: Relative model features and supported workflows across the current Trezor lineup.
Limit: Manufacturer comparison, not an independent security ranking.
Supports: Trezor's description of Safe 7's layered architecture, key isolation, attack prerequisites, and customer-impact position.
Limit: Manufacturer interpretation of a disclosure affecting a component used in its product.
Supports: Physical laser-fault findings, firmware-verification bypass, prerequisites, and later attack stages against TROPIC01.
Limit: Component-level invasive laboratory work; it does not by itself establish remote compromise or extraction of Safe 7 user keys.
Supports: Component vendor acknowledgement and framing of the firmware-verification issue.
Limit: Vendor advisory; product-level impact depends on the complete architecture and threat model.
Supports: Current Ledger product positioning and lineup features.
Limit: Manufacturer shop page; price, stock, bundles, and specifications can change.
Supports: Display, connectivity, Secure Element, Ledger OS, Recovery Key, price-at-publication, and product positioning.
Limit: Manufacturer announcement, not an independent audit; price and availability are time-sensitive.
Supports: Which Ledger components are open or reviewable and which low-level parts remain restricted.
Limit: Ledger's own description of its source-availability boundary.
Supports: Differences among recovery words, the offline Recovery Key, and optional Ledger Recover.
Limit: Manufacturer overview; users must read current device and service terms.
Supports: Identity-verified subscription, encrypted fragment, service-provider, eligibility, and recovery conditions.
Limit: Legal terms can change and differ by jurisdiction; not a technical audit of service providers.
Supports: Current lineup, software, backup, and transparency positioning.
Limit: Manufacturer overview, not an independent security assessment.
Supports: Nova connectivity, platform, backup, security, and user-interface specifications.
Limit: Manufacturer claims; exact compatibility and availability can change.
Supports: BitBox's dual-chip, secure-chip, open-source, reproducible-build, and transaction-verification design claims.
Limit: Manufacturer explanation, not a complete independent evaluation of every component or build.
Supports: Native and third-party asset or network support plus explicit limitations such as SOL and XRP.
Limit: Compatibility is version-dependent and does not guarantee every token or contract action is decoded.
Supports: Bitcoin-only scope, keypad, display, dual secure elements, microSD, NFC, USB-C, PSBT, and advanced features.
Limit: Manufacturer claims; users must verify current firmware, companion compatibility, and workflow.
Supports: Bitcoin-only positioning, open-source and reproducible-firmware claims, and signing design.
Limit: Manufacturer description, not a complete independent product audit.
Supports: Current model interfaces, components, and operating specifications.
Limit: Specifications may change by hardware revision and do not prove safe user operation.
Supports: Current model availability and purchase channel.
Limit: Price, inventory, shipping, and bundles are time-sensitive.
Supports: Display, secure elements, QR signing, recovery, profiles, and product specifications.
Limit: Manufacturer claims; price, stock, and compatibility can change.
Supports: Current multi-coin, Cypherpunk, and Bitcoin-only firmware tracks and release paths.
Limit: A release registry does not independently prove build reproducibility or transaction correctness.
Supports: Public firmware release dates, notes, and downloadable artifacts.
Limit: Repository visibility does not prove that a shipped device or binary exactly matches reviewed source.
Supports: Vendor-listed asset and companion-wallet breadth.
Limit: Vendor-listed support is integration-dependent and is not proof of clear signing for every action.
Supports: Secure-element, certification, audit, backup, and firmware design claims.
Limit: Manufacturer claims and audit summaries; scope and current physical disclosures require separate review.
Supports: Wallet-generation, seedless and seed modes, card backup, and model differences.
Limit: Manufacturer comparison, not an independent security ranking.
Supports: Closed-source, immutable firmware, authenticity checks, and the manufacturer's security-through-obscurity position.
Limit: Manufacturer explanation of a non-public firmware design; users cannot independently review the complete source.
Supports: Invasive laser-fault method, password-reset result, affected card state, cost and physical prerequisites.
Limit: Specialist destructive physical attack; not a remote exploit, scalable theft method, or proof that every Tangem use case is compromised.
Supports: Tangem's assessment of possession time, equipment cost, destructiveness, scalability, anonymity, and practical risk.
Limit: Manufacturer interpretation of an independent finding affecting cards already in circulation.
Supports: EVM wallet features, transaction simulation, risk prompts, and hardware-wallet connection positioning.
Limit: Project claims; simulation and warnings can be incomplete and do not replace hardware signing or user verification.
Supports: Public browser-extension source, releases, issue history, and license.
Limit: Repository access does not prove that every installed build, dependency, or transaction simulation is safe.
Supports: PSBT, hardware-wallet, multisig, UTXO, fee-control, watch-only, Tor, and licensing claims.
Limit: A desktop coordinator and interface, not hardware key isolation or a guarantee against computer, node, or backup compromise.
There is no universal winner. Trezor Safe 7 fits open-source, broad multichain and large-display needs; Ledger Nano Gen5 fits a polished broad ecosystem; BitBox02 Nova fits a focused transparent workflow; COLDCARD Mk5 fits advanced Bitcoin-only vaults; Keystone 3 Pro fits QR-first multichain use; and Tangem fits a narrower phone-and-card convenience profile. The correct choice depends on the failure mode you can manage.
Not automatically. It can isolate signing keys, but it cannot make a malicious contract safe, fix the wrong network or address, or guarantee that an opaque approval is understood. Use a separate active wallet and verify human-readable transaction details on a trusted display.
Open code improves the possibility of review and reproducible builds, but it does not guarantee that a shipped device matches the code, that reviewers find every defect, or that the owner follows a safe process. Reviewability is one dimension, not a universal verdict.
No. QR or microSD separation can reduce direct connectivity, but malicious data, bad addresses, compromised coordinators, unsafe update files, and unread transaction details remain possible. The complete signing and recovery workflow matters.
BIP39 converts entropy into portable recovery words and allows an optional passphrase. SLIP39 defines threshold Shamir mnemonic shares so a chosen number of shares can recover the secret. Compatibility and operational complexity differ, so test the exact recovery path before funding.
Only if you can back it up and rehearse recovery without ambiguity. A passphrase can separate wallets even when recovery words are exposed, but a lost or mistyped passphrase creates a valid different wallet and can permanently hide the intended funds.
Both published findings require physical possession and specialist invasive laboratory work; neither is a remote internet exploit. Their scope and architecture differ. Read each lab disclosure and manufacturer response, then decide whether cost, prerequisites, key reachability, patchability, and your own theft risk make the issue material.
Use the manufacturer's current site or an explicitly authorized seller, inspect the packaging and device, run authenticity checks, install firmware from the official source, and require the device to generate a fresh backup. Never use prefilled recovery words.
Replaced the 2022 legacy list with a failure-mode fit model, six current hardware approaches, two software companions, balanced physical-lab disclosures, six hard-stop gates, recovery rehearsal, source limitations, and machine-readable output.
Independent educational research, not personalized security, financial, legal or tax advice. Model bctb-wallet-fit-review v1.0. No device, software or backup is guaranteed safe. Partner commissions must never determine editorial placement.
Mastering Bitcoin, 3rd Edition by Andreas M. Antonopoulos and David A. Harding. A technical resource on Bitcoin, transactions and recovery, not a promise of investment returns.
Read the authors' free online edition Third edition, 2023. Not a live market guide. Publisher details.