Four questions decide
whether a wallet holds.
Hardware wallets share one problem no product fixes: a device whose only purpose is holding Bitcoin marks its owner as worth attacking — distributor databases have been breached, and supply-chain tampering is real even where the vendor ships no backdoors. If you need one anyway, four things stand between an attacker and your seed: how much of the wallet actually runs inside the secure element, whether the screen and buttons are driven by it, where the randomness comes from, and how much of the stack you can read. No affiliate links, no aggregate star ratings — just the architecture.
Scores are architecture, not verdicts.
A high composite means fewer places for a compromise to hide. It does not mean a device is right for you — threat model, custody plan and firmware discipline still decide that. Read the rubric before you read the table.
READ THE METHODOLOGY →Know a wallet that belongs on this sheet?
Send it over — along with any question about a score, a correction, a datasheet we missed, or just what you think of the rubric. Every message is read by a person, and submissions are never paid placements.