Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Cake Wallet Review
Region Restricted
Not available in your region
Cake Wallet is unavailable in your region.
Cake Wallet Overview
Product Name Cake Wallet
Release Date 2018
Wallet Type Multi-platform wallet
Custodial Status Non-custodial
Token Standards ERC-20, TRC-20, SPL
Platforms iOS, Android, Desktop (Windows), Desktop (macOS), Desktop (Linux)
Hardware Wallet Support Yes
Built-in Swaps Yes
Staking Support None
Open-source Fully open-source
Fiat On-ramp Yes
Supported Hardware Wallets Ledger, Trezor, COLDCARD, BitBox02
Hardware Connection Methods USB, Bluetooth
Cake Wallet Screenshots
Cake Wallet Pros and Cons
Pros
Cons
Who Cake Wallet is Best for — and Who Should Skip It
Cake Wallet website hero showing “Crypto Made Easy” with app screenshots and a Download Now button.
Cake Wallet fits users who want everyday self-custody with Monero at the center. It works well for people who want to hold XMR and BTC, swap between assets, use privacy tools, and handle all of that from one app.
It is a weaker fit for users who want the easiest wallet possible or deep browser-based DeFi access. People who want one-click extension use, broad NFT features, or cold-storage-first security should look elsewhere.
What is Cake Wallet and How Does it Work?
Cake Wallet is a self-custody wallet app for Android, iPhone, iPad, macOS, Linux, and Windows. It started as a Monero wallet. It now supports a wider set of chains, token wallets, swaps, buy and sell partners, Cake Pay, and Lightning for Bitcoin.
Users access it on their own device. There is no exchange-style account to open before creating a wallet. Setup starts with a local PIN. Then the user creates a wallet or restores one from a seed phrase, backup file, QR code, or a supported hardware flow.
Keys stay on the user’s device. Cake does not hold them. Most transactions are approved in the app. On supported hardware flows, signing moves to the external device for the assets and platforms it supports.
However, Cake does more than store coins.
Wallet Type, Custody and Recovery Model
Cake Wallet is a non-custodial hot wallet. The user controls the keys. Cake does not hold funds or recover access for the user.
Recovery depends on wallet type. Standalone Monero wallets use 16-word Polyseed by default or 25-word legacy seeds. Wallet Groups can use one 12-word BIP39 seed across multiple supported assets. Cake also supports backup-file, QR, and hardware-based restore flows where applicable.
Wallet classHot software wallet
Who controls the keysUser
Recovery methodRecovery depends on wallet type. Standalone Monero wallets use 16-word Polyseed by default or 25-word legacy seeds. Wallet Groups can use one 12-word BIP39 seed across multiple supported assets. Cake also supports backup-file, QR, and hardware-based restore flows where applicable
Can you export keys or seed?Yes, but the exact export and restore path varies by wallet type
Portability to another walletPartial
What happens if you lose the deviceYou can restore on a new device if you still have the correct seed, backup file, QR restore path, or supported hardware setup
What happens if you lose the recovery methodAccess to funds can be permanently lost
Who can help recover accessNobody can recover funds without the recovery method; support can help with app issues only
Best use caseDaily self-custody, privacy-focused asset management, and in-app swaps
Cake is not a managed account. There is no provider-side reset if you lose both the device and the recovery method. The user gets full control. The user also carries full recovery responsibility.
Supported Assets, Networks and Compatibility
Cake Wallet supports far more than its Monero-first image suggests. Users searching for Cake Wallet supported coins or Cake Wallet supported cryptocurrencies are usually asking two things: which chains work natively, and which token standards work on top. It covers major privacy, Bitcoin, and selected smart-contract ecosystems. It also supports tokens on several networks. Support is not identical across platforms. Mobile gets newer assets and features first, and Linux desktop 5.9.0 did not include Zcash, Decred, or Zano. It is still more focused than a browser-extension web3 wallet.
Major chains supportedMonero, Bitcoin, Ethereum, Litecoin, Bitcoin Cash, Polygon, Base, Arbitrum, BNB Smart Chain, Solana, Tron, Dogecoin, Nano, Zano, Decred, Wownero, and Zcash
Token standardsERC-20 and other EVM tokens, including BEP-20 on BNB Smart Chain, plus SPL tokens on Solana and TRC-20 tokens on Tron
PlatformsiPhone, iPad, Android, macOS, Linux, Windows
Hardware supportDevice-, asset-, and platform-specific support across Ledger, Trezor, BitBox, Trezor Safe 7, and selected Cupcake or Coldcard Q flows
Connection methodsUSB, Bluetooth on supported Ledger flows, QR on supported restore or signing flows, and in-app swap and payment flows
Notable gapsNo browser extension, limited dApp access, no broad NFT-first tooling, and hardware support varies by asset and platform
Cake covers many assets, but it is not a browser-based web3 hub. It is stronger for self-custody, swaps, privacy tools, and mixed mobile or desktop use than for extension-led DeFi workflows.
Core Features and Real-world Use Cases
Cake Wallet website section showing “Trusted by 1,000,000+ users” and feature cards for trustless software and built-in exchange.
Cake is broader than a simple Monero wallet, but narrower than a full web3 wallet plus extension stack. It works best for self-custody users who want to hold XMR and BTC, swap between assets, buy or sell through partners, and spend through Cake Pay without leaving the app.
For users wondering how to buy Monero on Cake Wallet, the main routes are partner buys when available or swapping into XMR inside the app.
The strongest tools sit inside Cake’s core wallet experience. That includes self-custody, privacy controls, Monero and Bitcoin support, and simple in-app asset movement. Buys, sells, swaps, and Cake Pay extend what the wallet can do, but those layers depend on partners, quotes, regional availability, and extra fees. Users who want privacy-focused self-custody with a few convenience tools will find the mix strong. Users who want broad DeFi access, NFT management, staking depth, or a full smart-account experience will not.
Fees and Total Cost of Ownership
Cake Wallet is free to download. There is no account fee. There is no subscription fee. The real costs come later. Users pay network fees, swap spreads, partner fees for buying or selling, and Cake Pay conversion costs when they use those services.
The biggest pricing mistake is to treat all of that as one wallet fee. It is not.
Cake Wallet swap fees and Cake Wallet exchange fees are not fixed wallet charges. They change by provider, route, region, and network. Blockchain gas is separate from swap pricing. Swap pricing is separate from buy and sell partner quotes. Cake Pay has its own cost layer too. Optional hardware costs also sit outside the wallet itself.
The day-to-day cost profile is reasonable for a self-custody wallet, but it is not always easy to predict before the final transaction screen. Users who mostly hold and send will mainly notice network fees. Users who buy, swap, and cash out inside the app will see more hidden friction. That friction comes from partner quotes, spread differences, and region-based pricing. Cake is cheap as a wallet. It gets more expensive if it becomes your all-in-one service hub.
Security Architecture and Trust
Cake Wallet website privacy and security section highlighting Monero support, Bitcoin privacy tools, and Litecoin privacy features.
Cake’s security model is solid for a hot wallet, but it still carries normal hot-wallet risk. Keys stay on the user’s device, and recovery stays with the user. Signing happens in the app unless a supported hardware flow moves signing to an external device. Protection layers include a local PIN, biometric unlock on supported devices, custom nodes, and Tor options. Cake 2FA is a limited secondary control for casual or local-access threats. It is not a substitute for hardware-wallet security or multisig. Cake also lacks some protections common in web3-first wallets, such as broad transaction simulation, a built-in revoke dashboard, and stronger extension-style approval tooling.
Cake is open source under an MIT license, and the code is public.
The table below gives the trust model in one place.
Key control modelUser-held local keys
Recovery modelRecovery depends on wallet type. Standalone Monero wallets use 16-word Polyseed by default or 25-word legacy seeds. Wallet Groups can use one 12-word BIP39 seed across multiple supported assets. Cake also supports backup-file, QR, and hardware-based restore flows where applicable
External validationOpen-source codebase is public; broad current wallet-wide audit coverage is Not disclosed
Open-source statusYes, MIT license
Anti-scam protectionsLocal PIN, biometrics, custom nodes, and Tor options; Cake 2FA is a limited secondary control for casual or local-access threats; no broad transaction simulation or revoke dashboard
Incident posturePublicly disclosed older weak 12-word Electrum-format Segwit Bitcoin wallet issue with clear migration guidance; no provider-side recovery model
Risk remains where it usually remains in hot wallets. A compromised phone or desktop can still expose funds. Fake apps, fake support, bad backups, and careless signing are still the main failure points. Cake reduces some of that risk through local controls and clearer self-custody boundaries. It does not remove it. Users who want the strongest isolation should still use a hardware wallet for larger balances.
One older Bitcoin issue is still worth noting: some Cake Wallet versions before v4.1.7 created weak 12-word Electrum-format Segwit Bitcoin wallets. Affected funds should be moved to a newly generated wallet from a known-good version or another compatible wallet. Other coin types and mnemonic-format variations were not part of that vulnerable Bitcoin-wallet class in the public write-up.
Backup, Recovery and Loss Scenarios
Recovery is one of the most important parts of this wallet. Cake gives the user control, but that also means the user carries the recovery burden. Support can help with app issues, sync issues, and setup problems. Support cannot restore funds if the user loses the recovery method.
The exact recovery path depends on the wallet type. Standalone Monero wallets use 16-word Polyseed by default or 25-word legacy seeds. Wallet Groups can use one 12-word BIP39 seed across multiple supported assets. Cake also supports backup-file, QR, and hardware-based restore flows where applicable. Recovery is flexible, but not uniform across every asset and setup.
The main rule is simple. Lose the device, and recovery is usually still possible. Lose the recovery method, and the loss can become permanent. That is the trade-off of non-custodial control.
UX, Performance and Platform Support
Cake Wallet website download section with QR code and buttons for App Store, Play Store, Android APK, Linux, and Windows, plus FAQ.
Cake is easy enough to use once the basics are clear. Sending and receiving are simple. More advanced actions take more attention because users need to watch sync status, node health, fees, and provider quotes. That makes Cake a better fit for users who want control than for users who want the easiest possible setup.
Platform support is broad, but parity is incomplete. Cake runs on iPhone, iPad, Android, macOS, Linux, and Windows. There is no browser extension and no web app. Mobile gets new assets and features first, and Android gets broader background sync. Cake works best as a privacy-focused self-custody wallet for holding, sending, swapping, and spending. It is a weaker fit for heavy dApp use or simple beginner-first use.
Cake gets the balance mostly right for its target user. The interface is safe enough to use well, but only if the user pays attention. It favors clear wallet state over maximum simplicity. That suits privacy-focused self-custody users. It does not suit everyone.
Customer Support, Documentation and Incident Handling
Cake has useful documentation. Human support is more limited. The docs help with setup, sync problems, swap basics, and common errors. Human support can help with app issues and partner-routing questions. It cannot reverse an on-chain transfer or restore a lost seed phrase.
Support works best when the problem is technical, not custodial. If the wallet is not syncing, a node is failing, or a trade is stuck in a provider flow, support can point the user in the right direction. If the user sent funds to the wrong address or lost the recovery method, support cannot get the funds back.
Cake can help with the app. It cannot act like a bank or exchange. That is normal for a non-custodial wallet.
Final Verdict
Cake Wallet earns its rating for privacy-focused self-custody. The Monero workflow is strong, the chain coverage is wider than the wallet’s reputation suggests, and built-in swaps, Cake Pay, and Lightning reduce the need to switch apps for everyday use. The friction is real too. Sync issues, node health, and layered partner fees require more user attention than most mainstream wallets ask for. The missing browser extension rules it out for active DeFi use. Users who want Monero at the center with a practical set of tools around it will find it well suited. Users who want simplicity or extension-led web3 access will not.
Overall Score
6.0
How We Rank
PROS
CONS
Affiliate Disclosure
Disclaimer: CryptoSlate may receive a commission when you click links on our site and make a purchase or complete an action with a third party. This does not influence our editorial independence, reviews, or ratings, and we always aim to provide accurate, transparent information to our readers.
FAQ
Is Cake Wallet custodial or non-custodial?
Cake Wallet is non-custodial. The user controls the keys and the recovery method.
Cake Wallet is a hot software wallet. It can work with some hardware flows, but the wallet itself is not a cold wallet.
Recovery depends on wallet type. Standalone Monero wallets use 16-word Polyseed by default or 25-word legacy seeds. Wallet Groups can use one 12-word BIP39 seed across multiple supported assets. Cake also supports backup-file, QR, and hardware-based restore flows where applicable.
It is a legitimate non-custodial wallet with public code and a long operating history. For a hot wallet, the security model is solid. Keys stay on the user’s device, and the wallet supports PIN, biometrics, Cake 2FA, custom nodes, and Tor options. It still carries normal hot-wallet risk.
It supports Monero, Bitcoin, Ethereum, Litecoin, Bitcoin Cash, Polygon, Base, Arbitrum, BNB Smart Chain, Solana, Tron, Dogecoin, Nano, Zano, Decred, Wownero, and Zcash. It also supports ERC-20 and other EVM tokens, including BEP-20 on BNB Smart Chain, plus SPL tokens on Solana and TRC-20 tokens on Tron. Support is not identical across platforms. Mobile gets newer assets and features first.
The wallet is free to download. Users mainly pay network fees, swap spreads, partner buy or sell fees, and Cake Pay conversion costs when those services are used. Cake Wallet exchange fees and swap fees are not fixed wallet charges.
Not at wallet level. Partner KYC may apply when buying, selling, or using some payment flows.
If you lose the device but still have the correct recovery method, you can usually restore the wallet on a new device. If you lose the recovery method too, access to funds can become permanent loss.