Como Rodar um Nó Completo do Monero: Guia para Iniciantes

Why Run Your Own Monero Node?

Running your own Monero full node is one of the most impactful things you can do for both your personal privacy and the health of the Monero network. While Monero's privacy features protect your transaction details, connecting to a remote node still exposes your IP address and can leak information about which transactions belong to you.

Here are the key reasons to run your own node:

• Maximum privacy — When you use a remote node, the node operator can see your IP address and correlate it with the transactions you submit. Running your own node eliminates this risk entirely.
• Independent verification — Your node independently validates every block and transaction, ensuring you are not relying on anyone else's honesty about the state of the blockchain.
• Network contribution — Each full node strengthens the Monero network by relaying transactions and blocks, increasing decentralization and resilience against attacks.
• No downtime dependence — Remote nodes can go offline, be rate-limited, or become overloaded. Your own node is always available when you need it.
• Avoid IP logging — Public remote nodes may log the IP addresses that connect to them. Even well-intentioned operators may be compelled to provide logs to authorities.

System Requirements

Before setting up your node, ensure your system meets the minimum requirements:

• Storage: At least 150 GB of free disk space for the full blockchain (as of early 2026). An SSD is strongly recommended for performance — synchronization on a traditional hard drive can take significantly longer.
• RAM: Minimum 4 GB, though 8 GB is recommended for smoother operation, especially during initial synchronization.
• CPU: Any modern dual-core processor is sufficient. The initial sync is CPU-intensive but normal operation is lightweight.
• Bandwidth: A stable internet connection with at least 10 Mbps. Running a public node that serves other users will require more bandwidth.
• OS: Linux is recommended for server deployments. Windows and macOS are supported for desktop use.

If storage is a concern, a pruned node requires only about 50 GB while still providing full transaction validation. More on this later.

Linux Setup (Recommended)

Step 1: Download and Verify

Always download Monero software from the official source and verify the cryptographic signatures:

• Visit the official Monero downloads page at getmonero.org and download the Linux CLI package for your architecture (most likely x86_64).
• Download the hash file and the GPG signature file from the same page.
• Import the Monero signing key and verify the signature against the hash file.
• Compute the SHA256 hash of the downloaded archive and compare it against the verified hash file.

Verification is not optional. It protects you against tampered downloads that could steal your funds or compromise your privacy. Never skip this step.

Step 2: Extract and Install

Extract the downloaded archive to a directory of your choice. A common convention is to place it in /opt/monero/ or your home directory. The key binary is monerod, the daemon that runs the full node.

Step 3: Initial Configuration

Create a configuration file to customize your node's behavior. A basic monero.conf (or monerod.conf) file should include:

• data-dir — The directory where the blockchain data will be stored. Ensure this points to a drive with sufficient free space.
• log-level — Set to 0 for minimal logging or 1 for more verbose output during initial setup.
• rpc-bind-port=18081 — The default RPC port. Your wallet will connect to this port to communicate with the node.
• restricted-rpc=1 — Enables restricted RPC mode, which limits the commands available over RPC. Essential if the port is exposed to the network.
• confirm-external-bind=1 — Required if you want to allow connections from other machines on your network.
• rpc-bind-ip=0.0.0.0 — Bind to all interfaces to accept connections from other devices. Use with restricted-rpc.

Step 4: Start and Synchronize

Launch monerod with your configuration file. The initial synchronization will download and verify the entire blockchain from the network. This process takes anywhere from 12 hours to several days depending on your hardware and internet connection.

During synchronization, you will see blocks being downloaded and verified in the console output. The sync is complete when the block height matches the current network height, which you can check on any Monero block explorer.

Step 5: Run as a Service

For a server or always-on machine, configure monerod to run as a systemd service so it starts automatically on boot and restarts if it crashes. Create a systemd unit file that specifies the monerod binary path, configuration file, and the user account under which it should run. Enable and start the service through systemctl.

Windows Setup

Running a Monero node on Windows is straightforward:

• Step 1: Download the Windows CLI or GUI package from getmonero.org and verify the signatures as described above.
• Step 2: Extract the archive to a permanent location such as C:\Monero.
• Step 3: Open Command Prompt or PowerShell, navigate to the Monero directory, and run monerod.exe. The first sync will begin automatically.
• Step 4: To run in the background, you can create a Windows Task Scheduler entry that starts monerod at login or system boot.

Note that Windows Defender or other antivirus software may flag monerod as suspicious due to its network activity. You may need to add an exception for the Monero directory.

VPS Setup

Running your node on a Virtual Private Server provides high uptime and bandwidth without taxing your home internet connection. For maximum privacy, choose a VPS provider that accepts cryptocurrency payments and does not require identity verification.

• Recommended specs: 4 GB RAM, 2 CPU cores, 200 GB SSD storage
• Crypto-accepting providers: Several VPS providers accept Monero directly, including Njalla, 1984 Hosting, and others. Search for "VPS accept Monero" to find current options.
• Security: Harden your VPS with a firewall, SSH key authentication, and disable password login. Only expose the necessary Monero ports.

Running Behind Tor

For the highest level of network privacy, route your Monero node's traffic through the Tor anonymity network. This prevents your ISP and network observers from knowing that you are running a Monero node.

• Install Tor on your system and ensure it is running.
• Add the following to your monero.conf: proxy=127.0.0.1:9050 to route all outgoing connections through Tor.
• Optionally add anonymous-inbound configuration to accept incoming connections as a Tor hidden service, allowing other Tor users to connect to your node.
• Set pad-transactions=1 to add padding to transaction messages, making traffic analysis more difficult.

Running behind Tor will significantly slow down the initial synchronization. Consider synchronizing over clearnet first, then switching to Tor for ongoing operation. Alternatively, download a verified copy of the blockchain separately to skip the network sync entirely.

Pruned Node vs Full Node

Monero offers a pruned node option that reduces storage requirements by approximately two-thirds:

• Full node (approximately 150 GB): Stores the complete blockchain including all transaction data. Can serve any block to any peer and provides maximum network contribution.
• Pruned node (approximately 50 GB): Stores all block headers and a random subset of transaction data. Still validates all transactions during sync but discards most historical data afterward.

To run a pruned node, add prune-blockchain=1 to your configuration file. A pruned node provides the same level of privacy and verification for your own transactions. The only downside is reduced ability to serve historical data to other nodes synchronizing from scratch.

For personal use, a pruned node is an excellent choice that balances storage efficiency with full privacy and verification benefits.

Connecting Your Wallet to Your Node

Once your node is synchronized, connect your Monero wallet to use it:

• GUI Wallet: In Settings, change the "Daemon address" to 127.0.0.1:18081 (or your node's IP if running remotely). The wallet will connect to your local node automatically.
• CLI Wallet: Launch the wallet with the flag --daemon-address 127.0.0.1:18081 to direct it to your local node.
• Mobile wallets: Some mobile wallets like Cake Wallet and Monerujo allow you to specify a custom node address. Enter your node's IP and port to connect.

If connecting from another device on your local network, replace 127.0.0.1 with your node machine's local IP address and ensure that restricted-rpc is enabled in your configuration.

Monitoring and Maintenance

Your node requires minimal ongoing maintenance, but periodic checks ensure smooth operation:

• Disk space: The blockchain grows by approximately 2-3 GB per month. Monitor your available disk space to avoid running out.
• Software updates: Keep monerod updated to the latest version, especially before scheduled network upgrades (hard forks). Subscribe to the Monero announcement channels for update notifications.
• Connection count: A healthy node should maintain 8-12 outgoing connections and accept incoming connections if you have forwarded the appropriate port (18080 for P2P).
• Sync status: Periodically verify that your node is fully synchronized by comparing its block height with a block explorer.

Remote Node Risks

To underscore why running your own node matters, here are the risks of using remote nodes:

• IP correlation: The remote node operator sees your IP address alongside every transaction you submit, potentially linking your identity to your Monero activity.
• Transaction censorship: A malicious remote node could refuse to relay your transactions, effectively censoring you.
• Data manipulation: While the wallet verifies most data, certain attacks against lightweight wallet users are possible through malicious nodes.
• Logging and surveillance: Node operators may log all connecting IP addresses voluntarily or under legal compulsion.

Using your own node, especially behind Tor, eliminates all of these risks.

Frequently Asked Questions

How long does the initial sync take?

On a modern system with an SSD and fast internet, the initial sync takes approximately 12-24 hours. On older hardware or slower connections, it can take several days. A pruned node syncs somewhat faster due to reduced data requirements.

Can I run a Monero node on a Raspberry Pi?

Yes, but with caveats. The Raspberry Pi 4 with 8 GB RAM can run a pruned Monero node. Use an external SSD for storage as the microSD card will be too slow and will wear out quickly. Expect the initial sync to take significantly longer than on a desktop system.

Will running a node slow down my internet?

The ongoing bandwidth usage of a Monero node is modest — typically a few GB per day. The initial synchronization uses more bandwidth. If you are concerned, you can limit the number of peer connections in your configuration to reduce bandwidth usage.

Is it legal to run a Monero node?

Yes, running a cryptocurrency node is legal in virtually all jurisdictions. A node simply validates and relays publicly available blockchain data. It does not facilitate illegal activity any more than running a web server does.