Cake Wallet

• Name: Cake Wallet
• URL: https://cakewallet.com/
• Category: non-custodial multi-currency wallet shell / privacy-first wallet-operations software
• Tags: bitcoin-ecosystem monero-ecosystem
• Summary: Cake Wallet is a broad wallet shell with privacy knobs, hardware-wallet support, and partner payment/exchange rails. Useful, but not a category anchor. The project note is still the right place for node choice, Tor and custom-server routing, and the attached service surface like Trocador and Cake Pay; the named operator boundary around release workflow, partner packaging, docs, and distribution now lives in cake-labs.
• What it does:
  • Provides a non-custodial multi-currency wallet for Android, iOS, macOS, Linux, and Windows
  • Supports privacy and operational-security features such as on-device sync privacy, Tor-only connectivity options, Cake 2FA, and device-hardening guidance
  • Lets users configure custom nodes and explicitly recommends running their own node for stronger privacy and control
  • Supports Ledger hardware-wallet workflows for Monero, Bitcoin, Ethereum, Litecoin, and Polygon via USB or Bluetooth restore/use flows
  • Includes built-in exchange, fiat buy/sell flows, invoice and donation-link generation via Trocador AnonPay, and a separate Cake Pay surface for gift cards, debit cards, and Apple/Google Pay spending
  • Publishes the wallet codebase openly and documents APK-signing verification for releases distributed via GitHub, Accrescent, and F-Droid
• Key claims:
  • The Cake Labs company site says Cake Wallet has operated since January 2018 and serves 250,000 users as a leading non-custodial wallet on iOS and Android
  • The docs homepage says Cake Wallet focuses on making crypto easier through intuitive privacy tools, cross-chain swaps, buying and selling crypto, and hardware-wallet support
  • The public GitHub repo describes Cake Wallet as open-source, non-custodial, private, and multi-currency, with support for custom nodes/servers, Tor-only connections, donation links, invoices, and exchange flows
  • The docs queryable pages say Cake Wallet is available on Android, iOS, macOS, Linux, and Windows, supports custom nodes, and documents Ledger hardware-wallet use across multiple chains
  • The docs queryable pages also indicate Lightning support is not a documented product focus in the current docs set; payment-related features are instead framed around Cake Pay, fiat buy/sell, Trocador AnonPay, and Bitcoin privacy features such as Silent Payments and PayJoin
  • The GitHub README says APK releases on GitHub, Accrescent, and F-Droid use the same signing key and can be independently verified, which is a meaningful trust signal for an open wallet product
• Whitepaper: No canonical standalone Cake Wallet whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official docs, Cake Labs company site, and the public Cake Wallet repository; see ../whitepapers/cake-wallet-primary-sources-2026-05-01.md.
• Sources:
  • https://cakewallet.com/
  • https://cakelabs.com/
  • https://docs.cakewallet.com/
  • https://docs.cakewallet.com/home.md?ask=What%20features%20does%20Cake%20Wallet%20documentation%20highlight%20around%20privacy%20tools%2C%20hardware%20wallet%20support%2C%20node%20customization%2C%20and%20supported%20platforms%3F
  • https://docs.cakewallet.com/home.md?ask=Does%20Cake%20Wallet%20documentation%20mention%20Lightning%20support%20or%20other%20payment-related%20features%3F
  • https://github.com/cake-tech/cake_wallet

Internal linkages

• Company / operator boundary for release workflow, support, distribution, and partner packaging: cake-labs.
• Best upward comparison points: bluewallet and sparrow-wallet.
• Keep Cake Wallet pointed upward toward those stronger wallet-ops reads rather than sideways across every consumer multi-asset wallet.

Protocol / company boundary

• Keep this note on the product surface: node choice, Tor posture, hardware-wallet flows, custom-server support, and the attached exchange / spend rails users encounter inside the wallet.
• Use cake-labs for the named-operator layer around release workflow, docs, support, distribution, and the broader Cake Wallet / Monero.com packaging shell.
• That split matters because what features does Cake Wallet expose? and who controls the software and partner-routing shell around Cake Wallet? are related but not identical questions.

Control surface

• At the product layer, the leverage sits in node defaults, Tor and custom-server routing, hardware-wallet support, and which exchange or spend partners Cake makes feel native.

• The wallet itself is not doing anything especially deep. It is a broad convenience shell with better privacy posture than most peers.

• Read it as wallet-ops software with attached partner rails, not as payment infrastructure in its own right.

• For the distribution and operator shell above that product surface, read cake-labs.

• Last reviewed: 2026-08-06 UTC