Cake Wallet vs Passkeys Wallet

Cake Wallet4.3/5

VS

Passkeys Wallet3.9/5

Feature	Cake WalletVisit	Passkeys WalletVisit
Ratings
Our score	4.3/5	3.9/5
User rating	No reviews yet	No reviews yet
Security	4.5	4.0
Ease of use	4.0	4.5
Chain support	4.0	4.5
Features	4.0	3.5
Privacy	5.0	3.0
Specs
KYC required	No	No
Wallet type	Mobile, Desktop	Web, MPC
Custody	Self-custodial	MPC (shared)
Chains	Bitcoin, Ethereum, Solana, Arbitrum, Base, Polygon, BNB Chain, Tron, Other	Bitcoin, Ethereum, Solana, BNB Chain, Arbitrum, Base, Optimism, Polygon, Avalanche, Other
Platforms	iOS, Android, macOS, Linux	iOS, Android, Chrome, Firefox, Brave, Safari, Windows, macOS
Open source	Yes	Not disclosed
Hardware wallet support	Yes	Not disclosed
In-app swaps	Yes	Yes
Buy crypto in app	Yes	Yes
Security features	PIN protection, Encrypted backups, Tor routing, Bitcoin Silent Payments, Coin control, Replace-by-Fee	Biometric authentication, Multi-party computation, Spending limits, Seedless backup, Client-side key decryption
Recovery without a seed phrase	No	Yes
Passkey login	Not disclosed	Yes
Built-in dApp browser	No	No
Perpetuals trading	No	Not disclosed
Company
Founded	2018	2024
Headquarters	—	United States
Investors	Not disclosed	Not disclosed
Strengths and weaknesses
Pros	Fully open source under the MIT license Self-custodial design requires no user account creation or identity verification Built-in Tor routing conceals IP addresses when broadcasting transactions Integrates hardware signing devices alongside an air-gapped phone signing option	Eliminates seed phrases in favor of biometric login Supports Bitcoin, Solana, and multiple Layer 2 networks in one interface No browser extension installation required for dApp interactions Private key export allows users to migrate keys to other compatible wallets
Cons	Native in-app bridging is restricted to USDT across Ethereum, Polygon, and Arbitrum In-app exchange rates and fiat purchases carry external third-party provider fees Fee customization and bumping tools are unavailable on Solana, Tron, and Arbitrum Requires users to manage seed phrase backups without automated social recovery	Windows Hello requires manual QR scanning to back up keys across devices Fiat on-ramps require third-party KYC verification depending on jurisdiction Relies on Exodus multi-party computation infrastructure to coordinate signatures Transaction signing depends on device browser and WebAuthn platform support
Best for	Monero and privacy-focused asset holders, Users routing transactions through Tor, Mobile users pairing hardware wallets	Developers embedding multichain web3 onboarding, Users avoiding seed-phrase management, Applications targeting mobile web traffic

Highlighted cells show the stronger value in each row. Data comes from each provider's site and public sources; check details before you sign up.

More comparisons