Default Cake Wallet remote node. Operator-run by the Cake team.
Best evidence tier. Signup tested end-to-end by xmr.club curator — deposit + withdrawal + edge cases. No-KYC posture verified at retail volume. Last_verified within 12 months.
Full rubric + 7-step verification walkthrough at /methodology.
This is the node millions of Cake Wallet users hit by default — which makes its uptime a real feature and its trust model worth understanding before you rely on it.
Background xmr-node.cakewallet.com is the public Monero node Cake Wallet ships as its default. Mainnet, restricted-RPC, operated by the Cake team. Because every Cake user who hasn't switched providers routes through it, the operational pressure to stay up and performant is real — and it shows.
What you trust A remote node sees your IP and the timing of your wallet's broadcasts/queries — never your keys, balances, or transaction details (Monero keeps those private at the node level). The key insight: if you already use Cake Wallet, you're already trusting the Cake team, so using their node adds no new party to your threat model. Cake's built-in Tor toggle blunts the IP exposure.
Operational specs Mainnet, restricted-RPC, high-availability at consumer-default scale. Reachable from any Monero wallet, not just Cake — usable as a reliable fallback node. Pairs naturally with Cake's Tor routing.
Philosophy A sane, well-resourced default so the median user gets a working node without having to choose one — while keeping the door open to switch providers or self-host. It's infrastructure-as-convenience done responsibly.
Grade rationale Grade A. A reliable, well-maintained default from a known operator, with adoption-driven uptime incentives. Coherent especially if Cake is already your wallet; graded as a remote node, with the usual self-hosting caveat.
Useful when You use Cake Wallet (it's already your default); you want a dependable fallback node; you need high uptime without running your own; you route over Tor and want a node that expects it.
Caveats A remote node sees your IP + tx-broadcast timing — route over Tor (Cake's toggle makes this easy); your own node is strictly more private. You're trusting the Cake team's no-log posture, which is reputable but unverifiable externally. Single operator — keep a backup node configured so a outage doesn't strand you.
Free · restricted RPC
Sourced from operator pages — verify identity via more than one channel before trusting time-sensitive instructions.
.onion mirror listed 2026-05-13 (<90d) No community reviews yet. Be the first below.
Honest, brand-neutral feedback welcome. A curator approves before it appears here. No JS required.
Silence censorship. Protect your privacy and bypass restrictions with Xeovo VPN. No email required.
Long-running no-KYC aggregator. XMR-friendly, Tor mirror, broad coin support.
Mobile + desktop multi-coin wallet (XMR, BTC, LTC, ETH) with in-app swap + CakePay.
Non-custodial cross-chain swap router with refund-on-refusal AML policy and multi-destination split swaps. No
Two-year-old no-account instant swap — in-house test swap settled in 3 minutes (0–1 conf), Trocador A privacy