You want to start mining Flux but you’re tired of pool fees eating into your rewards? Here’s the thing: Setting up your own Flux full node for solo mining sounds complicated, but honestly, it’s one of the most satisfying mining projects I’ve tackled. When I got my first solo Flux block after running my own node for three weeks, I literally jumped out of my chair.
Most mining guides assume you’ll just point your GPUs at a pool and call it a day. But if you’re serious about solo mining Flux, running your own full node gives you complete independence. No pool downtime, no trusting third parties with your work, and zero fees.
This isn’t a quick weekend project though. You’ll need decent hardware, some Linux knowledge (or willingness to learn), and realistic expectations about block odds. Let me walk you through exactly how to set up a Flux full node for solo mining, what hardware you actually need, and whether your hashrate gives you a realistic shot at finding blocks.
Why Run Your Own Flux Solo Mining Full Node?
Before we dive into the technical setup, let’s talk about why you’d even want to run your own node instead of using a public solo mining pool.
The independence factor is huge. When you run your own Flux node, you control everything. Your mining rewards go directly to your wallet with zero middlemen. No pool can suddenly change their fee structure or shut down unexpectedly.
I learned this lesson the hard way with another coin. Was solo mining through a public pool that shut down with only 12 hours notice. Lost half a day of mining time scrambling to reconfigure everything. Trust me on this: Having your own infrastructure matters.
Network validation is another reason. Running a full node means you’re actually validating transactions and contributing to Flux network security. You’re not just leeching off someone else’s infrastructure — you’re participating in the decentralized network.
The learning experience alone makes it worthwhile. Setting up and maintaining a Flux node teaches you way more about blockchain technology than just pointing miners at a pool ever will. You’ll understand how difficulty adjustments work, how blocks propagate, and what actually happens when your miner finds a valid share.
Real-time monitoring gives you immediate feedback. When your miner submits a share to your own node, you see it instantly in the logs. No wondering if the pool received your work or if your connection dropped.
Flux Network Basics: What You’re Actually Mining
Flux uses the ZelHash algorithm, which is basically Equihash 125,4 with some modifications. It’s ASIC-resistant and designed for GPU mining, making it accessible for solo miners with consumer hardware.
Current network hashrate sits around 50-60 MS/s depending on the day. Block time targets 120 seconds, so roughly 30 blocks per hour across the entire network. Block rewards vary based on the node tier system, but miners typically get around 37.5 FLUX per block after node operator rewards.
The current Flux price hovers around $0.0230, which matters for calculating whether your electricity costs make sense. More on that later.
Network difficulty adjusts every block using a slow-moving average, so you won’t see wild swings like some coins. This makes estimating your block odds more predictable, which is crucial for solo mining strategy.
One thing that surprised me: Flux has a fairly active development community. The network actually gets regular updates and improvements, unlike some zombie coins that just keep mining along with no real development. That matters for long-term solo mining — you want to mine a coin that’ll still exist in six months.
Hardware Requirements for Flux Full Node Solo Mining
Let’s get specific about what hardware you need. I see too many guides that give vague specs — here’s what actually works in practice.
Node Hardware (Separate from Mining Rigs)
Your Flux node needs to run 24/7, but it doesn’t need to be a beast. Here’s the minimum that works reliably:
- CPU: 4 cores minimum, Intel i5 or Ryzen 5 equivalent works fine
- RAM: 8 GB minimum, 16 GB recommended for smooth operation
- Storage: 250 GB SSD minimum — blockchain grows over time
- Network: Stable connection with open ports, at least 10 Mbps up/down
- OS: Ubuntu 20.04 or 22.04 LTS preferred, Debian also works
I run my Flux node on an old Dell workstation I picked up for $200 on eBay. It’s not sexy, but it runs rock solid. You could also use a newer mini PC or even a higher-end Raspberry Pi 4 with 8GB RAM if you want to keep power consumption down.
Power draw for the node itself is minimal — maybe 50-80W for a basic setup. That’s way less than your mining rigs will pull.
Perfect for running a Flux node — quiet, efficient at around 15W idle, and enough power to handle blockchain sync and mining connections smoothly.
Mining Rig Specs
Your actual mining hardware is separate from the node. Here’s what mines Flux efficiently:
NVIDIA GPUs: RTX 3060 Ti through 4090 all work well. ZelHash loves memory bandwidth. A single RTX 3070 pushes around 63 Sol/s at 120W. RTX 4070 Super does about 85 Sol/s at similar power.
AMD GPUs: RX 6000 and 7000 series work but generally less efficient than NVIDIA for this algorithm. RX 6700 XT gets maybe 55 Sol/s at 130W.
For solo mining Flux with realistic block odds, you ideally want at least 500-1000 Sol/s total. That’s roughly 8-16 RTX 3070s, or 6-12 RTX 4070s. Less hashrate works but your block finding intervals get looooong.
I’ll be honest with you: If you’re running just 2-3 GPUs, you might want to consider dual mining solo setup where you split your rigs between multiple coins to increase your odds of hitting something.
Complete Flux Full Node Setup: Step-by-Step
Now for the actual setup. This looks intimidating written out, but take it step by step and you’ll be fine.
Initial Server Setup
Start with a clean Ubuntu 22.04 LTS installation. SSH into your server and update everything first:
sudo apt update && sudo apt upgrade -y
Install required dependencies:
sudo apt install build-essential pkg-config libc6-dev m4 g++-multilib autoconf libtool ncurses-dev unzip git python3 python3-zmq zlib1g-dev wget curl bsdmainutils automake cmake clang ntp ntpdate nano -y
That’s a lot of packages, but Flux needs them all for compilation and operation.
Install Flux Daemon
Download the latest Flux daemon. Check the official Flux GitHub for the current version — as of writing this it’s 5.27.0 but updates happen regularly.
mkdir ~/flux && cd ~/flux
wget https://github.com/RunOnFlux/fluxd/releases/download/v5.27.0/fluxd-ubuntu-v5.27.0.tar.gz
tar -xzf fluxd-ubuntu-v5.27.0.tar.gz
Move binaries to your path:
sudo mv flux* /usr/local/bin/
Create Flux data directory and config:
mkdir ~/.flux
nano ~/.flux/flux.conf
Here’s the critical config for solo mining. Pay attention to the rpcuser and rpcpassword — you’ll need these later:
rpcuser=fluxrpc
rpcpassword=CHOOSE_STRONG_PASSWORD_HERE
rpcallowip=127.0.0.1
rpcallowip=YOUR_MINER_IP/32
rpcport=16124
port=16125
server=1
daemon=1
listen=1
txindex=1
addressindex=1
timestampindex=1
spentindex=1
insightexplorer=1
gen=0
equihashsolver=tromp
addnode=explorer.runonflux.io
addnode=blockbook.app.runonflux.io
Replace YOUR_MINER_IP with the actual IP address of your mining rig(s). If mining on the same machine, 127.0.0.1 works fine.
Initial Blockchain Sync
Start the daemon for the first time:
fluxd
No joke: This takes a while. The Flux blockchain will sync from genesis, which can take 12-24 hours depending on your hardware and connection speed. Check sync progress with:
flux-cli getinfo
Look for “blocks” and compare it to the current block height on a Flux explorer. When they match, you’re fully synced.
Pro tip: You can speed this up by downloading a bootstrap. Check the Flux Discord for community-provided bootstrap files — can cut sync time to 2-3 hours.
Create Mining Address
Once synced, generate a transparent address to receive mining rewards:
flux-cli getnewaddress
This gives you a “t-addr” starting with “t1”. Save this address somewhere safe — this is where your block rewards will go.
You can also import an existing address if you prefer:
flux-cli importprivkey YOUR_PRIVATE_KEY
Configure Mining Software for Your Flux Node
Now that your node is running, time to point your miners at it. I’ll cover the most common mining software for Flux.
lolMiner Configuration
lolMiner works well for both NVIDIA and AMD cards on ZelHash. Create a batch file or shell script:
lolMiner.exe --algo FLUX --pool YOUR_NODE_IP:16124 --user YOUR_T_ADDR.WORKER_NAME --pass x
Replace YOUR_NODE_IP with your Flux node’s IP address. If mining on the same machine as the node, use 127.0.0.1.
The –user field takes your t-addr that you generated earlier, optionally followed by .WORKER_NAME to identify different rigs.
miniZ Configuration
miniZ is NVIDIA-optimized and often gets slightly better hashrates than lolMiner on RTX cards:
miniZ.exe --par=125,4 --server=YOUR_NODE_IP --port=16124 --user=YOUR_T_ADDR.WORKER_NAME
Same deal with IP and address. The –par=125,4 specifies Equihash 125,4 which is what Flux uses.
GMiner Alternative
GMiner also supports ZelHash if the above don’t work for you:
miner.exe --algo 125_4 --server YOUR_NODE_IP:16124 --user YOUR_T_ADDR.WORKER_NAME
Test all three miners on your specific hardware. I’ve seen hashrate differences of 5-10% between miners on the same GPU depending on the model and overclock settings.
Verify Mining Connection
Watch your node logs to confirm miners are connecting:
tail -f ~/.flux/debug.log
You should see lines like “received submit from [your miner]” when shares come in. If you don’t see this within a few minutes of starting your miner, something’s wrong with your config.
Common issues: Firewall blocking port 16124, wrong IP address in miner config, or rpcallowip not matching your miner’s IP in flux.conf.
Realistic Block Odds: Can Your Hashrate Actually Hit Blocks?
Let’s talk numbers because this determines whether solo mining Flux makes sense for you.
At current network difficulty (around 50,000-55,000 depending on the day), here’s roughly what different hashrates can expect:
100 Sol/s: ~72 days average between blocks
500 Sol/s: ~14 days average between blocks
1000 Sol/s: ~7 days average between blocks
2000 Sol/s: ~3.5 days average between blocks
These are AVERAGES. Variance is brutal in solo mining. You could hit a block on day one with 100 Sol/s, or go 30 days with 1000 Sol/s.
Remember, Flux blocks pay out approximately 37.5 FLUX after node rewards. At current prices around $0.0230, that’s maybe $14-16 per block. Your electricity costs need to stay below that averaged over your expected block interval.
Running 1000 Sol/s typically means 10-12 RTX 3070s at about 1200-1400W total system power. In the US at $0.12/kWh, that’s roughly $3.40 per day in electricity. Over a 7-day average block interval, that’s $23.80 in power costs for a ~$15 block reward.
See the problem?
Solo mining Flux only makes economic sense if you have cheap electricity (under $0.08/kWh), already own the hardware, or you’re mining for reasons beyond immediate profit. The math gets better with larger hashrate operations, but you need serious GPU count to make it work.
For realistic block odds calculations specific to your setup, check out our statistical analysis of solo mining success rates — the methodology applies across different coins.
Optimizing Your Flux Solo Mining Setup
Assuming your electricity costs work out or you’re mining anyway, here’s how to optimize your setup.
GPU Overclocking for ZelHash
ZelHash responds well to memory overclocking and core undervolting. For NVIDIA RTX cards, my typical settings:
RTX 3070:
Core: -200 MHz (yes, negative)
Memory: +1200 MHz
Power Limit: 60-65%
Result: ~63 Sol/s at 115-120W
RTX 4070:
Core: Lock at 1800 MHz
Memory: +1500 MHz
Power Limit: 70%
Result: ~82 Sol/s at 125W
These are starting points. Every GPU is different due to silicon lottery. Increment memory slowly and watch for invalid shares or crashes.
Node Maintenance
Your Flux node needs occasional maintenance:
Weekly: Check debug.log for errors or peer connection issues. Should maintain 8-12 active connections to other nodes.
Monthly: Verify you’re on the latest daemon version. Flux updates regularly and running outdated versions can cause sync issues.
Quarterly: Clean up debug.log if it gets huge. Mine hit 5GB after three months and was slowing down the node.
flux-cli stop
rm ~/.flux/debug.log
fluxd
Monitoring Your Block Hunt
Set up monitoring so you know immediately when you find a block. I use a simple script that checks getblocktemplate output and sends a Telegram notification when a new block appears with my address.
You can also monitor shares submitted vs accepted ratio. Should be 99%+ accepted. If you’re seeing lots of rejected shares, your node might be lagging behind the network or your miners are submitting stale work.
Backup and Redundancy
Here’s something nobody tells you: Back up your wallet.dat regularly. If your node dies and you haven’t backed up recently, any block rewards sitting in your node wallet could be lost.
flux-cli backupwallet /path/to/backup/wallet_backup.dat
Keep this backup somewhere secure and separate from your node. Cloud storage encrypted, separate USB drive, wherever — just not on the same machine as the node.
Consider running a backup node on different hardware if you’ve got the resources. Switch miners to the backup if your primary node goes down. Downtime in solo mining hurts because you’re missing potential blocks.
Zelcore Node Integration: Alternative Setup Path
If running a command-line node feels too technical, Zelcore offers an alternative path with their FluxNode setup. This is actually different from just running a mining node — it’s participating in Flux’s decentralized computing network.
FluxNodes come in three tiers: Cumulus, Nimbus, and Stratus. Each requires collateral (Flux coins locked in the node) and provides computational resources to the network. In return, you earn a portion of block rewards.
Here’s the thing though: FluxNodes earn passive rewards, but you still need to point miners at your node for actual mining. The node itself doesn’t mine — it just validates transactions and provides compute resources.
For pure solo mining purposes, running a standard Flux daemon as described earlier is simpler and doesn’t require collateral. FluxNodes make sense if you’re long-term bullish on Flux and want to support the network infrastructure while mining, but that’s a different calculation than just mining profitability.
The Zelcore wallet makes managing your Flux addresses easier with a GUI, which some people prefer over command-line wallet management. You can use Zelcore for wallet management while still running your own mining node — they’re not mutually exclusive.
Hidden Gem: Network Difficulty Patterns and Strategic Mining
Here’s something I noticed after running my Flux node for six months: Network difficulty has predictable patterns based on price movements and profitability switching.
When Flux pumps in price, nicehash hashrate floods in within hours, spiking difficulty by 20-30%. When price dumps, difficulty drops as renters switch to other coins. These swings can be 40-50% over a week.
Smart solo miners track this. When difficulty drops significantly, your block odds improve proportionally. During low-difficulty periods, even smaller hashrate operations have decent shots at blocks.
I keep a spreadsheet tracking daily network hashrate and my shares vs expected shares. When the network is running cold (low hashrate), I’ll fire up my backup rigs that usually aren’t profitable. When it’s hot with rental hashrate, I sometimes switch those marginal rigs to other coins.
This isn’t pool hopping — your own node stays online regardless. You’re just strategically allocating hashrate based on network conditions. Over time, this significantly improves your block find rate compared to just mining blindly 24/7 at fixed hashrate.
Another pattern: Weekends typically see slightly lower network hashrate than weekdays. Maybe 5-10% difference. Not huge, but measurable. I’ve hit three weekend blocks versus one weekday block over my last four Flux blocks. Could be variance, could be real. Either way, I keep my full hashrate online over weekends now.
When Solo Mining Flux Doesn’t Make Sense
I need to be honest here: Solo mining Flux doesn’t make sense for everyone. Let me save you some wasted effort and electricity.
If you have expensive electricity (over $0.15/kWh): Pool mining with lower expected variance makes way more sense. The consistency of pool payouts helps offset high power costs better than the feast-or-famine of solo mining.
If you’re running under 200-300 Sol/s: Your average block interval stretches beyond 30-40 days. That’s brutal psychologically and financially. You’ll spend $100+ in electricity hoping to hit a $15 block. During bear markets, this gets even worse.
If you can’t handle variance: Solo mining isn’t for everyone. I’ve gone 3x my expected block interval multiple times. If seeing your electricity meter spin while earning nothing drives you crazy, just pool mine. Seriously. The stress isn’t worth it.
If your node setup isn’t stable: Running a full node requires system administration skills. If your node crashes weekly and you don’t know how to debug it, you’ll miss potential blocks and waste hashrate. Pool mining is more forgiving of technical issues.
Alternative strategies that might work better: Consider dual mining where you split your hashrate between Flux and another coin like Ravencoin with your own node. You reduce individual coin block odds but increase the chance of hitting something.
Or look at coins with lower network hashrate where your GPUs represent a larger percentage of network power. Neoxa solo mining or Vertcoin might give better block odds with similar hashrate.
For context on profitability across different coins, check our solo mining profitability comparison between major coins.
Frequently Asked Questions
How much hashrate do I need to realistically solo mine Flux?
Minimum 500 Sol/s if you want blocks within a reasonable timeframe (2-3 weeks average). Below that, you’re looking at month+ intervals between blocks. I’d recommend 1000 Sol/s or more for consistent mining. That’s roughly 8-16 mid-range GPUs depending on model and optimization. Less than 200 Sol/s and you’re better off pool mining — the variance will kill you.
Can I use a Raspberry Pi to run my Flux node?
Technically yes, but it’s not ideal. The Raspberry Pi 4 with 8GB RAM can handle the blockchain and validation, but sync time is painfully slow and performance under load is marginal. I’ve tested it and wouldn’t recommend it for production solo mining. A cheap mini PC with an actual x86 processor and SSD performs way better for similar power consumption. Raspberry Pis work fine for monitoring or learning, just not for serious mining operations.
What happens if my node goes offline while mining?
Your miners will show connection errors and stop submitting shares. Any potential block finds during downtime are lost — your rigs can’t submit to a node that’s offline. This is why node stability matters so much. Set up monitoring to alert you immediately if your node crashes. I use uptimerobot.com to ping my node every 5 minutes and get SMS alerts if it goes down. Average node restart takes 2-3 minutes, but you’ve lost potential shares during that time.
How do Flux block rewards compare to other solo-mineable coins?
Flux blocks pay approximately 37.5 FLUX after node operator rewards, currently worth around $14-16. Compare this to Ravencoin blocks at 2500 RVN (~$50), Kaspa’s 231 KAS (~$30), or Alephium’s varying rewards based on mining group. Flux rewards are on the lower end, meaning your electricity costs need to be really efficient. The advantage is lower network hashrate than major coins, giving smaller operations better block odds. It’s a trade-off between reward size and find frequency.
Can I run multiple coins on one node server?
Absolutely, and I actually recommend this if you have the resources. I run Flux, Ravencoin, and Alephium nodes on the same server — a 6-core CPU with 32GB RAM and 1TB SSD. Each blockchain is separate, using different ports. Total CPU usage rarely exceeds 30-40% even with all three active. This lets you strategically switch mining hashrate between coins based on difficulty and profitability without relying on third-party pools. Just make sure your storage can handle multiple blockchains — they add up over time.