Methodology
We do not compare fundamentally different products with one misleading score. Each product type has its own model.
1. Self-custody wallets (software, mobile, browser)
Criteria: control over private keys, security architecture, backup and recovery, network support, ecosystem-specific features, hardware integration, open-source status, independent audits, usability, platform availability, transaction controls, transparency and documented limitations.
2. Hardware wallets
Criteria: secure element and certification (e.g. EAL), supported networks (including via third-party interfaces), backup format and recovery phrase, passphrase support, open-source firmware, independent audits, battery and connectivity, supported platforms, price, warranty and documented limitations (e.g. no native support for a coin).
3. Custodial exchanges
Criteria: availability in the target country, coin support, trading fees, spread, deposit methods, withdrawal availability, withdrawal fees, custody model, security controls, customer support, ease of use, regulatory status and transparency. Exchanges are scored only on exchange criteria and are never ranked as wallets.
4. Buying platforms
Criteria: country availability, payment methods, fees and spread, minimum amounts, delivery speed, withdrawal options, regulation and customer support.
Evidence labels
Every recommendation carries one of three statuses: hands-on tested (with version and date), documentation reviewed (official sources, not used by us), or not yet tested. We do not fabricate tests, screenshots, transactions, fees or user counts.
Scoring
Scores (0–10) on reviews are based on the relevant model above and are never combined into one score across product types. “Best overall” picks on coin pages weigh: network compatibility, backup quality, security, ease of use and ecosystem features — in that order of importance.
Backup and recovery assessment
We assess per wallet: who controls the private keys, the backup format, recovery phrase format, interoperability, passphrase support, hardware compatibility, recovery options if the app disappears, migration possibilities, derivation paths where relevant, wallet-file availability, common backup mistakes and ecosystem-specific risks. We never ask users for seed phrases, private keys or passwords.