تقليم عقدة مونيرو: تشغيل عقدة كاملة بمساحة تخزين محدودة

Why Run a Monero Node

Running your own Monero node is one of the most impactful things you can do for both your personal privacy and the health of the Monero network. When you connect your wallet to your own node, your transaction queries never leave your machine, eliminating the risk that a remote node operator could log your IP address alongside your transaction data. Additionally, every full node strengthens the network by independently verifying every block and transaction, making it harder for any entity to manipulate the consensus.

The primary barrier to running a node has traditionally been storage. The full Monero blockchain exceeds 150 GB as of early 2026 and continues to grow. For users with limited disk space, especially those running nodes on VPS instances, Raspberry Pi devices, or laptops with small SSDs, this requirement can be prohibitive. That is where pruning comes in.

What Pruning Actually Does

The Technical Mechanism

Monero's pruning implementation removes seven-eighths of the blockchain data that is no longer needed for validation. Specifically, it discards most of the transaction data from old blocks while retaining all block headers, key images, and output commitments required to verify new transactions and maintain consensus.

When a pruned node syncs, it downloads and validates every block in full, exactly as a non-pruned node does. The difference is that after validation, it discards the bulk of the historical transaction data according to a deterministic pattern. Each pruned node retains a different one-eighth of the historical data (determined by a random "pruning seed"), which means the network as a whole still stores complete copies of the blockchain distributed across many pruned nodes.

Storage Savings

The practical savings are substantial:

• Full node: approximately 150-170 GB (as of March 2026)
• Pruned node: approximately 50-60 GB
• Savings: roughly 100 GB, or about 65% reduction

This brings the storage requirement well within the range of a modest VPS, a Raspberry Pi with a 128 GB microSD card, or a laptop with a 256 GB SSD.

What You Retain vs. What You Lose

A pruned node retains full validation capability. It verifies every transaction, checks every signature, and enforces every consensus rule exactly as a full node does. What you lose is the ability to serve historical block data to other nodes that are syncing from scratch. Pruned nodes can still serve block headers and the one-eighth of historical data they retain, so they do contribute to the network, just not as comprehensively as a full archival node.

How to Enable Pruning

Fresh Sync with Pruning

The simplest approach is to start a fresh sync with the pruning flag enabled. When you launch monerod with the --prune-blockchain flag, it will download, validate, and prune data as it syncs, never storing more than necessary.

Linux Step-by-Step

First, download the latest Monero CLI release from the official getmonero.org website. Verify the download using the provided GPG signatures. Extract the archive and navigate to the directory containing the binaries.

To start a pruned node, run:

./monerod --prune-blockchain --data-dir /path/to/your/data --log-level 0

The --data-dir flag specifies where the blockchain data will be stored. Choose a location on your fastest available storage (SSD is strongly recommended). The --log-level 0 flag reduces log verbosity to save disk I/O.

For a more complete configuration suitable for long-term operation, consider these additional flags:

./monerod --prune-blockchain --data-dir /mnt/ssd/monero --log-level 0 --max-concurrency 4 --db-sync-mode safe --enforce-dns-checkpointing --enable-dns-blocklist

To run the node as a background service, create a systemd unit file. This ensures the node starts automatically on boot and restarts if it crashes.

Windows Step-by-Step

On Windows, download the Monero GUI or CLI from getmonero.org. If using the GUI, open Settings > Node and check the option for "Prune blockchain." If using the CLI, open a command prompt, navigate to the Monero directory, and run:

monerod.exe --prune-blockchain --data-dir D:\MoneroData

For Windows users who prefer the graphical interface, the Monero GUI wallet includes a built-in local node option with a pruning checkbox that handles everything automatically.

VPS Deployment

Running a pruned node on a VPS is an excellent way to maintain a private node accessible from anywhere. A VPS with 2 CPU cores, 4 GB RAM, and 80 GB SSD storage is sufficient for a pruned node. Popular providers include Hetzner, DigitalOcean, and Contabo.

After provisioning your VPS and connecting via SSH, install Monero using the same Linux steps above. Consider running monerod behind a firewall that only exposes port 18081 (RPC) to your personal IP addresses, and port 18080 (P2P) to the public for network participation.

For enhanced privacy, deploy monerod as a Tor hidden service. Install Tor on the VPS, configure a hidden service pointing to monerod's P2P port, and your node will be accessible via a .onion address without revealing the VPS IP to Monero peers.

Pruning an Existing Blockchain

If you already have a fully synced node and want to reclaim disk space, you can prune in place. Use the monero-blockchain-prune tool included with the Monero CLI:

./monero-blockchain-prune --data-dir /path/to/your/data

This tool reads through the existing blockchain database and removes the pruneable data. The process takes several hours depending on your disk speed but does not require re-syncing from scratch. After pruning, start monerod with the --prune-blockchain flag to maintain the pruned state going forward.

Sync Time Comparison

Sync times vary significantly based on hardware, internet speed, and network conditions. As a rough benchmark on a modern machine with SSD storage and a 100 Mbps connection:

• Full node initial sync: 24-48 hours
• Pruned node initial sync: 18-36 hours
• Pruned node from bootstrap: 6-12 hours (using a trusted bootstrap file)

The sync time improvement for pruned nodes comes from reduced disk I/O during the write phase. Both pruned and full nodes download and validate the same data during sync; the difference is that pruned nodes discard data immediately after validation rather than writing it all to disk.

Trade-offs: Pruned vs. Full Node

Advantages of Pruning

• 65% less storage required, making it accessible on cheap hardware
• Faster sync times due to reduced disk writes
• Lower ongoing I/O, extending the life of SSDs
• Same validation security as a full archival node
• Full wallet privacy when connecting your wallet to your own pruned node

Disadvantages of Pruning

• Cannot serve complete historical data to syncing peers
• Slightly reduced network contribution compared to a full node
• Cannot be used for blockchain analysis tools that need full historical data
• One-way operation: once pruned, you cannot "un-prune" without re-syncing

When to Use Each

Use a pruned node if you are running on limited storage, deploying on a VPS with modest disk allocation, setting up a node primarily for wallet privacy, or running on a Raspberry Pi or similar low-resource device. Use a full archival node if you have abundant storage, want to maximize your contribution to the network, need historical data for research or analysis, or are running a public remote node service.

Configuration Tips for Optimal Performance

Memory and CPU Settings

Monerod can be tuned for your hardware. The --max-concurrency flag limits the number of CPU threads used during sync. On a VPS with 2 cores, set this to 2. The --db-sync-mode safe flag ensures database consistency at the cost of slightly slower sync, which is recommended for VPS deployments where power loss could corrupt the database.

Bandwidth Management

If your internet connection has limited bandwidth, use --limit-rate-up and --limit-rate-down flags to cap bandwidth usage in kB/s. For a home connection, setting upload to 1024 (1 MB/s) and download to 8192 (8 MB/s) is a reasonable starting point that allows normal browsing alongside node operation.

Monitoring Your Node

Once running, you can monitor your node through the monerod interactive console. Type status to see sync progress, print_net_stats for bandwidth usage, and print_cn for connected peers. For remote monitoring, the RPC interface on port 18081 provides programmatic access to node status, which can be integrated with monitoring tools like Grafana.

Connecting Your Wallet

After your pruned node is synced, configure your wallet to connect to it. In the Monero GUI, go to Settings > Node and enter 127.0.0.1:18081 as the daemon address (or your VPS IP if running remotely). In Monero CLI wallet, use --daemon-address 127.0.0.1:18081. For mobile wallets like Cake Wallet, add your node's address in the node settings.

Using MoneroSwapper alongside your own node gives you the best of both worlds: acquire XMR without KYC through MoneroSwapper, then manage your funds through a wallet connected to your own pruned node for maximum privacy.

Conclusion

Pruning makes running a Monero node accessible to virtually anyone with a modest amount of storage. You retain full validation security, complete wallet privacy, and meaningful network contribution, all while using only about 50 GB of disk space. Whether you deploy on a VPS for always-on accessibility, a Raspberry Pi for a dedicated home node, or simply on your laptop's SSD, a pruned Monero node is one of the best investments you can make in your financial privacy. The setup process takes under an hour, the sync completes in a day or two, and the benefits last as long as you keep it running.