How to run your own Monero node
Download the official Monero CLI, run monerod with pruning enabled and let it sync, which needs about 100 GiB for a pruned node or about 250 GiB for a full one as of January 2026. Then point your wallets at it, optionally over Tor, so nobody else sees your wallet traffic.
Quick steps
- Prepare storage. Use an SSD with at least 250 GiB free for a pruned node, or 625 GiB for a full node, on a machine that can stay on.
- Download and verify Monero. Download the CLI from getmonero.org by typing the address yourself and verify the SHA256 hash before running it.
- Start monerod with pruning. Run monerod with prune-blockchain enabled and wait until it reports that it is synchronized.
- Configure ports. Open peer port 18080 in your router, expose only the restricted RPC on 18089 and keep 18081 on localhost.
- Add Tor if needed. Publish the restricted RPC as a Tor onion service to reach your node from your phone without exposing your IP.
- Connect your wallets. Point Cake, Feather, Monerujo or the GUI at your node's local address or onion address and confirm they sync.
Why run your own node
- Privacy. No third party sees your IP address when your wallet syncs or broadcasts.
- Trust. Your node verifies every block itself, so it cannot be fed false data.
- Mining. P2Pool requires a local node. See how to mine Monero.
- Payments. Merchant tools such as BTCPay Server run a node alongside the wallet. See accepting Monero payments.
- The network. More independent nodes make Monero harder to attack or censor.
What you need
| Item | Pruned node | Full node |
|---|---|---|
| Blockchain size (docs.getmonero.org, 20 Jan 2026) | about 100 GiB | about 250 GiB |
| Free space the guide recommends | 250 GiB or more | 625 GiB or more |
| Storage type | An SSD is strongly preferred; the first sync on a hard disk can take a very long time | |
| Internet | An unmetered connection; the initial download is the full chain, and a public node keeps serving data afterwards | |
Pruning keeps about one third of the blockchain data while still validating everything, which is why it saves about two thirds of disk space. It is the right choice for almost everyone. A small always-on computer, a home server or a rented VPS all work.
Step 1: download and verify
Get the CLI bundle from getmonero.org (type the address yourself). The current release line is 0.18.5.x: 0.18.5.0 shipped on 11 May 2026, followed by point releases 0.18.5.3 on 6 October 2026 and 0.18.5.4 on 17 October 2026. Check the SHA256 hash against the signed hashes file before running anything. The Monero GUI can also start a local node for you in Advanced mode if you prefer not to use a terminal.
Step 2: start monerod
A simple private node for your own wallets:
monerod --prune-blockchain
Let it run until it reports it is synchronized. That can take from several hours to a few days, depending on disk and connection. Add --sync-pruned-blocks to download blocks that peers have already pruned and save bandwidth.
Step 3: a sensible configuration
For a node that also serves your phone or other people, use a config file (often bitmonero.conf) instead of long command lines. Key options from the official docs:
prune-blockchain=1: pruned storage.p2p-bind-port=18080: the default peer port. Open it in your router to help the network. UPnP was removed in 0.18.5.0, so port forwarding is now manual.rpc-restricted-bind-ip=0.0.0.0andrpc-restricted-bind-port=18089: a restricted RPC port that only answers safe, view-only requests. This is what you expose to wallets.- Keep the unrestricted RPC on 18081 bound to localhost. If you ever bind it to another address, monerod demands
--confirm-external-bindas a warning. public-node=1: advertise your restricted port so other wallets can find it. Leave it off if bandwidth is limited.zmq-pub=tcp://127.0.0.1:18083: needed if you will run P2Pool.rpc-ssl=autodetect: allow SSL connections from wallets.
On Linux the official docs include a systemd unit so monerod starts at boot and restarts after crashes.
Step 4: reach it from your phone over Tor
The docs describe publishing your node as a Tor onion service: Tor forwards an onion address to your restricted RPC port, and wallets such as Cake, Feather and Monerujo can connect to it. This hides your home IP and works without opening router ports for RPC. The docs also suggest disable-rpc-ban=1 for onion nodes, because all Tor clients appear to come from one local address.
Step 5: connect your wallets
- Same computer: wallets find a local node on 127.0.0.1:18081 automatically.
- Home network: use the node's local IP and port 18089.
- Anywhere: use your onion address and port.
Step-by-step settings for each wallet are in Monero remote nodes.
Maintenance
- Update monerod when a new release is announced on getmonero.org. Ignore update emails: the project does not send them.
- A network upgrade (hard fork) needs an update before the fork height. The FCMP++ upgrade was on a test network in October 2026 with no mainnet date announced. See FCMP++ explained.
- Watch disk space; the chain grows over time.
- Compare your height with network stats now and then.
Home, VPS or the GUI?
| Setup | Pros | Cons |
|---|---|---|
| GUI with local node on your desktop | No terminal; one app does it all | Only runs while the computer is on |
| Always-on home machine | You own the hardware; reachable over Tor | Needs a little Linux knowledge and a stable connection |
| Rented VPS | Fast connection, public IP, easy to share | The provider can see the server; check their bandwidth limits and terms |
Whatever you choose, never keep a spending wallet with large funds on a public server. The node does not need your keys at all.
Frequently asked questions
How big is the Monero blockchain in 2026?
The official docs gave about 250 GiB for a full node and about 100 GiB for a pruned node as of 20 January 2026, and recommend leaving more free space for growth.
Does a pruned node help the network?
Yes. A pruned node validates every block and relays transactions. It stores only part of the old data, so it serves fewer historical blocks to other nodes.
Which port should I open for my Monero node?
Open port 18080 for peer-to-peer traffic. Expose the restricted RPC, usually on port 18089, only if other wallets need to use your node. Keep port 18081 private.
Can I run a Monero node on a small home computer?
Yes, as long as it has an SSD with enough space and an unmetered connection. Expect the first sync to take longer on low-power hardware.