Monero Daemon Startup Flags: A Guide to Optimizing Your XMR Node

Introduction: Why Mastering monerod Flags Matters in 2026

Running your own Monero node is one of the most important steps for true sovereignty and privacy. It eliminates reliance on third-party nodes that could log your IP, censor transactions, or leak metadata.

The Monero daemon — monerod — is highly configurable via startup flags (command-line options) or a configuration file (bitmonero.conf). These flags control everything from blockchain storage and sync speed to networking, privacy routing (Tor/I2P), and RPC access.

In March 2026 (Monero version 0.18.4.x ‘Fluorine Fermi’ series), proper flag usage can:

• Reduce disk usage by ~2/3 with pruning
• Speed up initial sync dramatically
• Hide your node behind Tor or I2P
• Turn your node into a safe public remote node for wallets
• Minimize attack surface and logs

This Monero Hub guide covers the most useful flags, recommended setups for different users, full config examples, and advanced privacy optimizations.

How to Use Startup Flags

You can pass flags directly when launching monerod:

Bash

./monerod --prune-blockchain --detach --log-level=1

Or use a config file (recommended for long-term setups):

Bash

./monerod --config-file=/path/to/bitmonero.conf

In the Monero GUI: Settings → Node → “Daemon startup flags” box.

Official reference: https://docs.getmonero.org/interacting/monerod-reference/

Essential Flags Everyone Should Know

Core & Storage Flags

• —data-dir — Set custom blockchain location (default: ~/.bitmonero)
• —prune-blockchain — Enable pruning (saves ~2/3 disk space; keep 1/8 of ring signatures). Best used from first sync.
• —sync-pruned-blocks — Download only pruned data when syncing a pruned node (highly recommended with pruning).
• —db-sync-mode — Options: safe (default, reliable), fast, fastest (riskier but quicker). Use safe:sync for production.

Daemon & Logging

• —detach — Run in background (daemonize).
• —pidfile — Create PID file (useful with systemd).
• —log-file — Custom log file.
• —log-level <0-4> — 0 = minimal (recommended for privacy), 4 = verbose.

Networking (P2P)

• —p2p-bind-ip 0.0.0.0 — Bind to all interfaces.
• —p2p-bind-port 18080 — Default P2P port.
• —no-igd — Disable UPnP (security best practice).
• —enable-dns-blocklist — Block known malicious peers.
• —disable-dns-checkpoints — (Advanced) Skip developer checkpoints.
• —out-peers / —in-peers — Limit outgoing/incoming connections (e.g., 12/48).

RPC (Wallet Connection)

• —rpc-bind-ip 127.0.0.1 — Bind RPC only to localhost (most secure).
• —rpc-restricted-bind-ip 0.0.0.0 / —rpc-restricted-bind-port 18089 — Public restricted RPC (view-only, safer for remote access).
• —restricted-rpc — Restrict RPC to safe commands.
• —public-node — Advertise as public remote node.
• —rpc-login user:pass — Basic auth for RPC.
• —confirm-external-bind — Allow binding to external IPs.
• —disable-rpc-ban — Be lenient with wallet connections (useful over Tor).

Performance & Limits

• —max-concurrency — Limit CPU threads.
• —limit-rate-up <kb/s> / —limit-rate-down <kb/s> — Bandwidth limits.
• —max-txpool-weight — Larger mempool for high-activity nodes.

Privacy-Focused Flags: Tor & I2P Integration

Monero has excellent built-in support for anonymity networks.

Basic Tor routing:

• —proxy 127.0.0.1:9050 — Route all traffic through Tor SOCKS.
• —tx-proxy tor,127.0.0.1:9050,12,disable_noise — Send your own transactions over Tor.

Advanced hidden service setup (run your own onion node):

• —anonymous-inbound=yourlongv3onionaddress.onion:18084,127.0.0.1:18084,24
• Combine with Tor hidden service in torrc.

I2P equivalent:

• —tx-proxy i2p,127.0.0.1:4447,12,disable_noise
• —anonymous-inbound=youri2paddress.b32.i2p:18085,127.0.0.1:18085,24

Hide your port:

• —hide-my-port

These flags make your node and transactions far harder to link to your real IP.

Recommended Configurations by Use Case (2026)

1. Personal Desktop/Laptop Node (Most Users)

Bash

monerod \  --prune-blockchain \  --sync-pruned-blocks \  --detach \  --log-level=1 \  --enable-dns-blocklist \  --no-igd

2. Privacy-Maximalist Tor Node

Bash

monerod \  --prune-blockchain \  --sync-pruned-blocks \  --proxy 127.0.0.1:9050 \  --tx-proxy tor,127.0.0.1:9050,12,disable_noise \  --hide-my-port \  --disable-rpc-ban \  --detach

3. Public Remote Node (Help the Community)

Bash

monerod \  --prune-blockchain \  --sync-pruned-blocks \  --rpc-restricted-bind-ip 0.0.0.0 \  --rpc-restricted-bind-port 18089 \  --restricted-rpc \  --public-node \  --rpc-login username:strongpassword \  --no-igd \  --enable-dns-blocklist \  --detach

4. Full Archival Node (Mining/Research — Needs Lots of Storage)

Omit —prune-blockchain and use —db-sync-mode safe.

Use a config file for systemd setups (example in official docs).

Advanced Optimization Tips

• Faster initial sync: Use SSD, —db-sync-mode fast, and —sync-pruned-blocks. Avoid fastest mode on important nodes.
• Reduce logs for privacy: —log-level=0 + large max-log-file-size.
• Systemd service: Create /etc/systemd/system/monerod.service with proper user/group and config file.
• Bootstrap node: Use —bootstrap-daemon-address for quicker initial sync (then switch to local).
• Resource limits: On low-RAM machines, lower —max-concurrency and peers.

Disk usage (2026 estimates):

• Full node: ~175–200+ GB
• Pruned node: ~60–70 GB

Common Pitfalls & Troubleshooting

• “Unknown option” in GUI: Some flags (like —data-dir) should be set in Blockchain location instead.
• Sync stuck: Try removing custom flags temporarily or check disk space/firewall.
• RPC connection refused: Use correct port (18081 unrestricted, 18089 restricted) and —trusted-daemon in wallets.
• High bandwidth usage: Set —limit-rate-up and —limit-rate-down.
• Tor issues: Ensure Tor is running and use correct SOCKS port.

Always test small changes and monitor with tail -f ~/.bitmonero/bitmonero.log.

Pros & Cons of Key Flags

Pruning (—prune-blockchain): Pros: Massive disk savings, still fully validating.Cons: Contributes slightly less to network (but still valuable).

Tor/I2P flags: Pros: Excellent IP hiding.Cons: Slightly slower connections.

Restricted RPC: Pros: Safer for public exposure.Cons: Limited commands for connected wallets.

FAQ – Monero Daemon Flags 2026

Do I need to prune? Yes for most users — it saves huge space with no privacy/security loss.

Can I run a public node safely? Yes — use —restricted-rpc, auth, and a dedicated port.

Best flags for maximum privacy? Tor/I2P + —hide-my-port + minimal logging + pruned node.

How do I update flags? Stop monerod, edit config or GUI flags, restart.

Where is the official flag list?https://docs.getmonero.org/interacting/monerod-reference/

Final Verdict & Call to Action

Mastering monerod startup flags turns a basic node into a powerful, private, and efficient piece of Monero infrastructure.

Whether you’re a daily user wanting a trusted local node, a privacy maximalist hiding behind Tor, or someone running a public remote node to help the network — the right flags make all the difference.

Start today:

1. Download latest monerod from getmonero.org
2. Choose a config from above
3. Launch and sync (be patient — first sync takes time)
4. Connect your wallet to 127.0.0.1:18081 (or your restricted port)

Running your own node is one of the best ways to support Monero and protect your privacy.

Follow us on X: @MoneroHub for more Monero node guides, privacy tools, and ecosystem deep-dives.

Last updated: March 27, 2026Always check the official monerod reference for the latest flags, as new versions may add options. Test configurations on stagenet first. DYOR.

‍