Ergo Node Solo Mining Setup: Configure Your Full Node 2026

Running your own Ergo node for solo mining is more involved than pointing your GPU at a pool, but it gives you complete control over your mining operation. No pool fees, no middleman, just you versus the Ergo network.

I’ve been running an Ergo node on my home network for the past eight months. The setup took me about two hours the first time — most of that was syncing the blockchain. Once it’s running, the node requires minimal maintenance. Based on my testing: The actual configuration is straightforward if you follow the steps in order.

Let me break this down into concrete steps. We’ll cover hardware requirements first, then the actual node setup, miner configuration, and finally the math on whether solo mining Ergo makes sense for your hashrate.

Step 1: Check Hardware Requirements for Your Ergo Node

Before you download anything, verify your system meets the minimum requirements. The Ergo node itself isn’t resource-heavy, but you need enough storage for the blockchain and enough RAM to run it smoothly.

Minimum specs for the node computer (not your mining rig — these can be separate machines):

• CPU: Any dual-core processor from the last decade works
• RAM: 4GB minimum, 8GB recommended for stability
• Storage: 50GB free space (blockchain grows about 1-2GB per month)
• Network: Stable internet connection, at least 5 Mbps up and down
• OS: Windows 10/11, Ubuntu 20.04+, or macOS 10.15+

I’m running mine on an old Dell Optiplex with an i3-4160 and 8GB RAM. Cost me $80 used. The node uses about 15-20 watts at idle. It runs 24/7 without issues.

Storage is important. The Ergo blockchain was about 42GB when I synced it in early 2026. An SSD makes the initial sync much faster — maybe 3-4 hours instead of 8-10 on a mechanical drive. After that initial sync, drive speed doesn’t matter as much.

Network Configuration Basics

Your node needs two open ports: 9030 for P2P connections with other nodes, and 9053 for your mining software to communicate with the node. If you’re running the node and miner on the same computer, you don’t need to forward ports. If they’re on separate machines, you’ll need to forward port 9053 to your node computer.

Port forwarding varies by router. Most modern routers let you set this up through their web interface at 192.168.1.1 or similar. Forward external port 9053 to internal port 9053 on your node’s local IP address.

Step 2: Download and Install the Ergo Node Software

The official Ergo node is available at GitHub. You want the latest stable release — as of early 2026, that’s version 5.0.x. Download the appropriate version for your operating system.

For Linux (my preference for node hosting):

• Download the .jar file from the releases page
• Install Java Runtime Environment if you don’t have it: sudo apt install openjdk-11-jre
• Create a directory for your node: mkdir ~/ergo-node
• Move the .jar file there: mv ergo-*.jar ~/ergo-node/

For Windows, the process is similar. Download the .jar file, install Java from Oracle or AdoptOpenJDK, and create a folder like C:ergo-node to keep everything organized.

Don’t run the node yet. We need to create the configuration file first.

Blockchain Storage Location

By default, the node stores blockchain data in your user directory. On Linux that’s ~/.ergo, on Windows it’s C:UsersYourName.ergo. If you want to change this location (maybe you have a dedicated drive), you’ll specify that in the config file in the next step.

Step 3: Create Your Node Configuration File

The configuration file tells your node how to behave. Create a file named ergo.conf in your node directory. Here’s a basic configuration for solo mining:

ergo {
  node {
    mining = true
    stateType = “utxo”
    blocksToKeep = 1440
  }
}

scorex {
  network {
    bindAddress = “0.0.0.0:9030”
    nodeName = “my-ergo-solo-node”
    knownPeers = []
  }
  restApi {
    bindAddress = “0.0.0.0:9053”
    apiKeyHash = “your_api_key_hash_here”
  }
}

Let me explain the important parts. The mining = true flag tells the node you’ll be mining. The stateType = “utxo” setting is the standard mode. The blocksToKeep parameter determines how many blocks your node stores — 1440 blocks equals about 3 days of history.

For the API key, generate a secure random string and then hash it with SHA256. On Linux: echo -n “your_secure_password” | sha256sum. Use the resulting hash in the config file. You’ll use the original password (not the hash) when connecting your miner.

Important detail: The bindAddress “0.0.0.0” means the node accepts connections from any IP. If you’re only mining locally, you can change this to “127.0.0.1” for better security. If your miner is on a different computer, keep it as 0.0.0.0 and use firewall rules to restrict access.

Step 4: Start Your Node and Sync the Blockchain

Now we can start the node. Navigate to your node directory and run:

java -jar -Xmx4G ergo-5.0.x.jar –mainnet -c ergo.conf

The -Xmx4G flag allocates 4GB of RAM to the node. If you have 8GB total system RAM, this is a safe setting. With 16GB or more, you can increase this to -Xmx6G for slightly faster sync.

The node will start syncing. You’ll see output scrolling by as it downloads and verifies blocks. This takes anywhere from 3 to 10 hours depending on your hardware and connection speed. My SSD-based node synced in about 4 hours.

You can check sync progress by opening a browser and going to http://localhost:9053/info (replace localhost with your node’s IP if accessing remotely). You’ll need to authenticate with your API key. The response shows your current height versus the network height.

Common Sync Issues

If your node gets stuck or syncs very slowly, try these fixes:

• Restart the node — sometimes peer connections drop
• Check your firewall isn’t blocking port 9030
• Manually add known peers to your config file (list available on Ergo Discord)
• Verify you have enough disk space — syncing needs extra room for temporary files

During my initial sync, the node paused at about 70% for twenty minutes. Turned out my router had temporarily blocked too many simultaneous connections. A router reboot fixed it.

Step 5: Configure Your Mining Software for Solo Mining

Once your node is synced, you can point your mining rig at it. Ergo uses the Autolykos2 algorithm, which is GPU-mineable. Most miners use lolMiner, TeamRedMiner, or NBMiner for Ergo.

Here’s an example command for lolMiner pointing at your local node:

lolMiner.exe –algo AUTOLYKOS2 –pool http://127.0.0.1:9053 –user your_ergo_wallet_address –apikey your_api_password

Replace 127.0.0.1 with your node’s IP if it’s on a different machine. The apikey is the original password you used before hashing it for the config file.

For TeamRedMiner, the syntax is similar:

teamredminer.exe -a autolykos2 -o http://127.0.0.1:9053 -u your_wallet_address -p x –api_key=your_api_password

Both miners will connect to your node and start submitting shares. You won’t see “accepted shares” like you do with pool mining. Instead, you’ll see “solution found” messages when your GPU finds a potential block. Most of these won’t meet the network difficulty — that’s normal.

Verifying Your Miner Connection

Check your miner is actually connected properly by looking at the node’s API endpoint: http://your-node-ip:9053/mining/candidate. If everything is working, you’ll see JSON data with the current mining candidate block. If you get an error, double-check your API key and firewall settings.

Step 6: Understand Your Solo Mining Odds on Ergo

Now for the math. Ergo’s network hashrate fluctuates between 15-20 TH/s depending on market conditions. Current ERG price: $0.3491. Block time is 2 minutes, so about 720 blocks per day.

Let me break this down: If you’re mining with 1 GH/s (about 5-6 modern GPUs), your expected time to find a block is roughly 20-30 days at current difficulty. That’s just the average — you might find one in a week, or go three months without hitting anything.

Based on my testing: I ran 2 GH/s for four months and found three blocks. Expected value would be about 4-5 blocks in that timeframe, so I was slightly unlucky. The variance is real.

Here’s a realistic breakdown by hashrate:

• 500 MH/s (2-3 GPUs): Average 40-60 days per block
• 1 GH/s (5-6 GPUs): Average 20-30 days per block
• 2 GH/s (10-12 GPUs): Average 10-15 days per block
• 5 GH/s (25-30 GPUs): Average 4-6 days per block

Block reward is currently 66 ERG minus a small storage rent fee of about 0.3-0.5 ERG. So you’re getting roughly 65.5 ERG per block. Do the math on your electricity cost versus the variance you can tolerate.

For comparison with other solo mining scenarios, check out our statistical analysis of success rates by hashrate across different coins.

The Variance Reality Check

This is critical to understand. Average block time doesn’t mean regular intervals. I’ve gone 47 days without a block, then found two in three days. That’s just how probability works. If you can’t handle the possibility of mining for 2-3x your expected time without a payout, solo mining isn’t for you.

Some miners prefer to dual mine — running part of their hashrate on a pool for steady income while solo mining with the rest. That’s actually a pretty practical approach for testing solo mining without going all-in.

Hardware Recommendations for Ergo GPU Mining

Ergo mining favors GPUs with good memory bandwidth and at least 4GB VRAM. The DAG size is currently around 2.8GB, so 3GB cards work but are getting close to their limit.

Power consumption matters significantly for solo mining where you might go weeks without a payout. A rig pulling 1000W costs you about $2.40 per day at $0.10/kWh. That’s $72 per month in electricity before you find a block. Make sure the math works for your situation — our guide on cutting solo mining electricity costs has more strategies.

Maintaining Your Node and Troubleshooting Common Issues

Once everything is running, your node needs minimal maintenance. I check mine about once a week, mostly to verify it’s still in sync and hasn’t crashed. The node software is pretty stable — in eight months, I’ve had maybe three unexpected restarts.

Regular Maintenance Tasks

Check sync status weekly through the API or web interface. If your node falls behind by more than a few blocks, investigate immediately. Usually it’s a network issue or the process died.

Monitor disk space. The blockchain grows steadily, and if you run out of space, the node will crash ungracefully. Set up an alert if possible, or just check it manually when you verify sync status.

Update the node software when new versions release. The Ergo team pushes updates every few months with bug fixes and optimizations. Always read the release notes — some updates require resyncing or config changes.

Troubleshooting: Node Won’t Start

Common causes: Port 9030 is already in use, corrupted blockchain data, or Java version incompatibility. Check the error log in the .ergo directory. If the blockchain is corrupted, you’ll need to delete the blocks folder and resync. Painful, but sometimes necessary.

Troubleshooting: Miner Can’t Connect

Verify the node is actually running and accessible at the IP and port you specified. Test with curl: curl -X GET “http://your-node:9053/info” -H “api_key: your_password”. If you get a response, the node is fine and the issue is in your miner configuration. Double-check wallet address and API key spelling.

Troubleshooting: Found Block Not Accepted

This happens occasionally. Your miner finds a solution that meets the difficulty, but by the time it reaches the network, another miner already found that block. It’s called an orphan block. Frustrating, but part of solo mining. You can reduce orphan risk slightly by having good network latency and multiple peer connections on your node.

I had an orphan block in month three. Really disappointing after weeks of nothing, then losing it to network timing. That naturally depends on network conditions beyond your control.

Solo Mining vs Pool Mining: When Does Running Your Node Make Sense?

Running your own node for solo mining makes sense if you value independence and have the hashrate to find blocks reasonably often. Pool mining is definitely easier and gives predictable payouts, but you’re paying 1-2% in fees and trusting the pool operator.

Based on my experience, the breakeven point is around 500-700 MH/s. Below that, you’re looking at 2+ months between blocks on average, which is tough psychologically and financially. Above 1 GH/s, solo mining becomes more practical.

The variance issue is real. If you need steady income to cover electricity and can’t handle going months without a payout, stick with pools. If you’re mining with “fun money” or surplus electricity, solo mining through your own node is incredibly satisfying when you actually hit a block.

For perspective on how Ergo compares to other solo mining options, check our profitability comparison covering Bitcoin, Litecoin, and Kaspa alongside GPU-mineable coins.

The Independence Factor

Running your own node means you’re not dependent on pool infrastructure. Pools get DDoS’d, go offline for maintenance, or occasionally just disappear with accumulated unpaid balances. Your node gives you direct connection to the Ergo network. No middleman can block your payouts or decide to change fee structures.

That matters more in a bear market. When prices drop and smaller pools shut down, you’re still mining independently.

Alternative: Mining Pool with Solo-Like Setup

If you want some of the benefits of solo mining without running a full node, a few pools offer “solo mining mode” where you mine alone but through their infrastructure. You still get the full block reward (minus a small fee, usually 0.5-1%), and the pool handles the node.

This is actually a decent compromise if your hashrate is borderline for true solo mining. You get the variance and reward structure of solo mining, but without the technical overhead of maintaining a node.

Popular pools offering solo mining mode for Ergo include HeroMiners and 2Miners. Configuration is similar to regular pool mining, just specify the solo port (usually different from the regular pool port). Your miner will only find blocks when you personally solve them — no shared rewards.

Frequently Asked Questions

How much hashrate do I need to solo mine Ergo realistically?

Minimum 500 MH/s to have a reasonable chance of finding blocks within 2-3 months. Ideally 1 GH/s or more for monthly block expectations. Below 300 MH/s, you’re looking at such long dry spells that it’s hard to justify versus pool mining. The math is straightforward: 20 TH/s network hashrate divided by your hashrate gives you your share of the 720 daily blocks.

Can I run the Ergo node on the same computer as my mining rig?

Yes, absolutely. The node only uses 15-20W and minimal CPU resources once synced. I’ve run both on the same machine with no issues. Just make sure you have enough RAM — the mining software plus node plus OS wants at least 8GB total, preferably 12GB if you’re mining with multiple GPUs. Your mining performance won’t be affected noticeably.

What happens if my node goes offline while I’m mining?

Your miner will lose connection and stop mining until the node comes back online. If you find a block while offline, obviously that’s lost opportunity. The node itself will resync when it restarts — usually takes just a few minutes if it wasn’t offline long. This is why I recommend running the node on dedicated hardware that stays on 24/7, not your main PC that you shut down daily.

Is it worth solo mining Ergo compared to other GPU coins?

That naturally depends on your electricity cost and risk tolerance. Ergo’s block time (2 minutes) and current difficulty make it one of the more practical GPU coins for solo mining. Compare it to Ethereum Classic (block time 13 seconds, much higher network hashrate) or Ravencoin (1 minute blocks, lower network hashrate). For under 2 GH/s, I’d say Ergo and Ravencoin are your best GPU solo options. Above 5 GH/s, you have more flexibility.

Do I need to keep the node running if I’m not actively mining?

No, but it’s easier to keep it running. If you shut down the node, you’ll need to resync when you restart — that’s usually quick if it’s only been offline a few days, but annoying if you let it sit for weeks. The node uses so little power that I just leave mine on. If you’re going on vacation or won’t mine for months, sure, shut it down to save electricity and reduce wear on your node hardware.