How to use a custom node in Cake Wallet
Open the Nodes page in the wallet's settings, tap the plus button and enter the node's address and port, turning on Use SSL only if the node serves TLS on that port. Running your own Monero node or Electrum server is the biggest privacy upgrade, and a port and SSL mismatch is the most common reason a custom node fails.
Quick steps
- Open the Nodes page. From the home screen open the settings, go to the current wallet's settings and choose Nodes. Each coin has its own node list.
- Tap the plus button. This opens the form for a new node.
- Enter address and port. Type the host name or IP address and the port, for example 18081 or 18089 for Monero, or 50002 for an Electrum server with SSL.
- Set SSL and other options. Turn on Use SSL only if the node serves TLS on that port. Add a login only if the node requires one. Turn on Trusted only for a node you control.
- Add a SOCKS proxy if needed. To reach the node through Orbot or another proxy, enable the SOCKS proxy option and enter an address such as 127.0.0.1:9050.
- Save, select and test. Save the node, tap it in the list to select it, and check that the wallet connects and starts syncing. If it shows as unreachable, recheck the port and SSL.
Cake Wallet does not download a full blockchain. It talks to a node: a Monero daemon for Monero, an Electrum-compatible server for Bitcoin and Litecoin, an RPC endpoint for Ethereum and similar chains. Cake runs default nodes and lists some community ones, and you can add your own. The node you use affects speed, reliability and privacy.
Why change the node
- Privacy. Any node operator can see your wallet's requests and your IP address unless you use Tor. Cake's docs call running your own node the biggest privacy upgrade available.
- Reliability. If the wallet stays on "Disconnected" or "Attempting Sync", switching node is the first fix the docs suggest.
- Speed. A nearby node, or your own on your home network, usually syncs Monero faster.
- Features. Bitcoin Silent Payments need an Electrum server with the right index (see below).
The node form, field by field
| Field | What to enter |
|---|---|
| Node Address | Host name or IP only, without http:// or a port, for example node.example.com or 192.168.1.20 |
| Node port | The port the node listens on (see the table below) |
| Login and Password | Leave empty unless your node uses RPC authentication |
| Use SSL | On only if that port serves TLS |
| Trusted | Monero: on only for a node you run yourself. It skips some defensive checks to sync faster |
| SOCKS proxy | Optional. Routes this node through a proxy, for example Orbot at 127.0.0.1:9050 |
| Enable for Auto-Switching | Lets the app fall back to this node automatically if the current one fails |
The exact layout changed when the Nodes screen was rebuilt in version 6.2 (June 2026), and version 6.5 added a Nodes page to each wallet's settings (Cake Wallet release notes, 2026). The node form also has a test button that reports whether the connection succeeded.
Common ports
| Coin and server | Typical port | SSL |
|---|---|---|
| Monero daemon, restricted RPC | 18089 | Often on for public nodes |
| Monero daemon, standard RPC | 18081 | Usually off on a home node |
| Monero over HTTPS | 443 | On |
| Bitcoin Electrum server (Fulcrum, electrs) with TLS | 50002 | On |
| Bitcoin Electrum server without TLS | 50001 | Off |
| Onion (.onion) nodes | As published by the operator | Usually off, Tor already encrypts |
These are conventions, not rules: always use the port your node or provider documents. Cake's own default nodes, as listed in the source code, follow the same pattern: a Monero node on 18081 with SSL and a Bitcoin Electrum server on 50002 with SSL.
Monero: your own node
Running monerod at home on a computer or a dedicated node box gives you the most privacy: no third party sees which blocks and transactions your wallet asks for. Point Cake Wallet at the node's local IP and RPC port while on home Wi-Fi, or expose it through Tor as an onion service for use away from home.
- A restricted RPC port (often 18089) is safer to expose than the full RPC port.
- Turn on Trusted only for your own node.
- A pruned node works fine for wallet syncing and needs much less disk space.
Bitcoin and Litecoin: Electrum servers
For Bitcoin, Cake Wallet speaks the Electrum protocol, so you need an Electrum server such as Fulcrum or electrs on top of Bitcoin Core, not Bitcoin Core's RPC port. Many home node packages include one. Litecoin works the same way with a Litecoin Electrum server; MWEB has its own node setting under the Litecoin settings.
Silent Payments caveat: scanning for Silent Payments needs an electrs server built with a tweak index. Cake's docs say that if your server lacks it, the wallet falls back to Cake's own electrs server for scanning, which matters if you run your own node for privacy. See Silent Payments. Version 6.4.2 also made sending Bitcoin work when your node is reachable only on your local network.
Ethereum and other chains
EVM chains, Solana, Tron and other coins also have node lists with an add option. Nano proof-of-work nodes are managed separately. Fewer people self-host these, so the main reason to change is reliability.
When a custom node will not connect
- Check SSL against the port first. Cake's docs say the most common mismatch is "SSL enabled on a non-SSL port or vice versa".
- Remove extras from the address. No
https://, no trailing slash, no port in the address field. - Self-signed certificates. If your home node uses a self-signed certificate and will not connect with SSL on, try a port without SSL on your local network, or use Tor.
- Firewalls and VPNs. Some mobile networks and VPNs block node ports. Try another network.
- Onion addresses need Tor. A
.onionnode only works with built-in Tor or Orbot running; otherwise it stays on "Connecting". See privacy and Tor. - Node still syncing. A daemon that is not fully synced cannot serve your wallet.
- Errors: "Internal error: Failed to get earliest fork height" usually means switching node and restarting the app (Cake Wallet docs, 2026). More in error messages.
If nothing works, switch back to a default node: your funds are on the blockchain, not on the node, and changing nodes never puts them at risk. For general sync trouble see Cake Wallet not syncing.
Frequently asked questions
Is it safe to use Cake Wallet's default node?
Yes, for safety of funds: a node cannot spend your coins. For privacy, the operator can see your IP and wallet requests, so use Tor or your own node if that matters to you.
What does the Trusted switch do?
For Monero it tells the wallet to trust the node and skip some defensive checks, which speeds up syncing. Turn it on only for a node you control.
Which port should I use for my Monero node?
Use the RPC port your node is configured for: 18081 is the usual standard port and 18089 a common restricted port. Match the SSL switch to that port.
Can I connect Cake Wallet to Bitcoin Core directly?
Not to Bitcoin Core's RPC. Cake Wallet needs an Electrum-compatible server such as Fulcrum or electrs running on top of your node.
Why does my .onion node never connect?
Onion nodes need Tor. Turn on built-in Tor or run Orbot, or use a clearnet node instead.