Manage nodes
Last updated
Your wallet doesn't hold the blockchain — it connects to a node that does. The node you use decides who sees your wallet's network activity, which makes this setting worth two minutes of your time: Cake Wallet's defaults work out of the box, and pointing the app at your own node gives you the strongest privacy available.
Each currency has its own node list. Open Settings from the top right, then under Wallet settings tap Nodes.
The current node is marked, and Cake Wallet ships several presets per currency. Tap another node to switch to it; use the refresh icon to re-test the list.

If your wallet won't connect or sync, switching nodes is the first fix to try — see Resolving connection issues.

Node label — any name you'll recognize.
Node Address and Node port — e.g. node.example.com and 18081 (Monero clearnet) or 50002 (Electrum-style over SSL). Add login and password only if your node requires them.
Use SSL — on if your node serves TLS (most public nodes on ports like 18089/50002 do).
Trusted — turn on ONLY for a node you control. It tells the wallet to skip some defensive checks for faster syncing.
Use SOCKS Proxy — route this node's connection through a proxy (for example Orbot's 127.0.0.1:9050 for Tor; see Tor with Orbot).
Using someone else's node means that operator can see your wallet's queries. Running your own removes that trust entirely — it's the single biggest privacy upgrade available:
Bitcoin/Litecoin: any Electrum-compatible server (Fulcrum, electrs)
Nano/Banano wallets have a separate Manage PoW nodes list under Settings → Connections (proof-of-work generation).
Litecoin MWEB uses its own node, set under Settings → Privacy → MWEB → MWEB Node.
During wallet creation, the Privacy settings screen lets you set a custom node before the wallet ever connects anywhere.
Last updated

