How a wallet review works
Pledge tracks wallets. It does not score them. Every review answers the same key-control questions and names the tradeoff.
Review lens
Recovery safety
We look for clear backup paths, recovery contacts, inheritance options, emergency kits, and whether the recovery design can survive device loss without handing unilateral control to a provider.
Review lens
Key control
We check whether signing is single-sig, multisig, hardware-signer based, or assisted multisig, and whether the user can understand who can or cannot move funds.
Review lens
Ease of use
We weigh practical setup burden, mobile access, guided onboarding, and whether the product fits smaller everyday balances or demands advanced operational skill.
Review lens
Hardware support
We look for dedicated signing devices, airgapped workflows, PSBT compatibility, QR or microSD flows, and coordinator-wallet compatibility.
Review lens
Privacy tooling
We look for open tooling, coin control, Tor, descriptors, PSBT flows, and other controls that matter to users who want more self-custody and privacy posture.
Evidence
Official sources first
A wallet review should not rest on marketing copy. Claims trace to official docs or product materials.
Counted
Source counts
Each profile lists the pages behind its claims: 65 sources across 22 wallets.
Boundary
Not custody advice
The review compares design signals. It does not verify device supply chains, custody setup, or user backup execution.
How to read a profile
Fit, then the case that does not fit
Profiles name who the wallet fits, the case that does not fit, and the main risk. Read those against your own situation.
Winding down
Listed, then left out of shortlists
When the vendor page says a wallet is winding down, the profile keeps the wallet, the notice, the source, and that page’s date as the review date. Finder shortlists leave it out. The open-source chip can therefore list fewer wallets than the number that name an OSI license.