Running your own node for solo mining Clore changed how I think about Blake3 mining. Most guides just tell you to point your miner at a pool and forget about it, but setting up a full Clore node teaches you exactly how the blockchain works — and honestly, it’s not nearly as complicated as people make it sound.
Let me break this down: Clore uses the Blake3 algorithm, same as Alephium. The difference? Clore’s network difficulty makes solo mining actually feasible with GPUs. A single RTX 3080 can hit around 2.5-3 GH/s on Blake3, and depending on network conditions, you might see a block every few weeks to months.
Quick math: At current network difficulty (check clore.ai for live stats), a 3 GH/s setup gives you roughly 1-2% of a block per day. That’s not pool mining where you get small payouts daily — this is the real solo mining lottery where you either hit a full block or nothing.
Why Run Your Own Clore Solo Mining Node
Before we dive into the technical setup, here’s why running your own node matters for solo mining Clore.
First: Trust. When you point your miner at someone else’s node, you’re trusting them to report your submitted shares correctly. With your own node, you verify everything yourself. You see every block attempt, every orphan, every network change in real-time.
Second: Speed. Network latency actually matters in solo mining. The faster your miner gets new work templates from your node, the less time you waste on stale shares. Running a local node on your network cuts out the internet roundtrip entirely.
Third: Learning. This might sound like the boring answer, but running a full node shows you exactly how proof-of-work consensus works. You’ll see mempool activity, block propagation times, difficulty adjustments — all the stuff that mining pools abstract away.
The data shows: Miners running local nodes typically see 1-2% fewer stale shares compared to remote connections. That might not sound like much, but over months of mining, it adds up.
Similar to what we covered in our Kaspa solo mining node guide, the setup process requires some technical comfort but nothing you can’t handle with careful attention to detail.
Step 1: Hardware Requirements for Clore Node Setup
Let’s start with what you actually need to run a Clore full node. The good news: It’s lighter than Bitcoin or Ethereum nodes.
Minimum specs that actually work:
- CPU: Any dual-core processor from the last 5 years (Intel i3, AMD Ryzen 3, even older i5/i7)
- RAM: 4 GB minimum, 8 GB recommended
- Storage: 100 GB SSD (blockchain grows roughly 1-2 GB per month)
- Network: Stable internet connection, minimum 5 Mbps up/down
- OS: Ubuntu 22.04 LTS, Windows 10/11, or macOS 12+
Honestly? An old laptop works fine. I run my Clore node on a refurbished ThinkPad T480 that cost me $200. It’s been running 24/7 for six months without issues.
The SSD part is non-negotiable though. I tried running it on a mechanical hard drive first — sync took forever and the node kept falling behind the network. Switched to a cheap 256 GB SSD and sync finished in under 4 hours.
Reliable SATA SSD for blockchain node storage. More than enough capacity for Clore blockchain, proven reliability for 24/7 operation.
Power consumption runs around 15-25W for the node itself. That’s separate from your mining rigs — we’re just talking about the computer running the blockchain node here. At $0.12/kWh, that’s roughly $2-3 per month in electricity.
One thing that surprised me: The node doesn’t need to be on the same physical machine as your miners. You can run the node on one computer and point multiple mining rigs to it over your local network. That’s actually how most serious solo miners set it up.
Step 2: Installing Clore Core Node Software
Now we get to the actual installation. I’m covering Ubuntu 22.04 first because that’s what I use, then Windows afterward.
Ubuntu/Debian Installation:
First, update your system packages:
sudo apt update && sudo apt upgrade -y
Install required dependencies:
sudo apt install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils libboost-all-dev libminiupnpc-dev libzmq3-dev -y
Download the latest Clore Core release from the official GitHub (check clore.ai for the current version link). As of early 2026, version 1.2.x is current, but verify before downloading.
wget https://github.com/clore-ai/clore/releases/download/v1.2.0/clore-1.2.0-x86_64-linux-gnu.tar.gz
Extract the archive:
tar -xvf clore-1.2.0-x86_64-linux-gnu.tar.gz
Move binaries to your local bin directory:
sudo mv clore-1.2.0/bin/* /usr/local/bin/
Verify installation:
clored --version
You should see version information printed to the terminal. If you get “command not found”, check your PATH or try using the full binary path.
Windows Installation:
Download the Windows .exe installer from the official Clore releases page. Run the installer and follow the prompts. Default installation directory is usually C:Program FilesClore.
The Windows version includes a GUI wallet interface, but for solo mining we’ll primarily use the command-line daemon (clored.exe).
Important: Windows Defender might flag the mining-related binaries. Add an exception for the Clore installation folder — these are false positives common with cryptocurrency software.
Step 3: Configuring Your Clore Node for Solo Mining
This is where we actually configure the node to accept mining connections. The configuration file is called clore.conf and needs specific settings for solo mining.
Create the Clore data directory (if it doesn’t exist):
Linux: mkdir -p ~/.clore
Windows: Usually auto-created at %APPDATA%Clore
Create/edit clore.conf in that directory:
nano ~/.clore/clore.conf (Linux) or use Notepad (Windows)
Here’s the configuration I use for solo mining:
server=1
daemon=1
rpcuser=cloreuser
rpcpassword=YOUR_SECURE_PASSWORD_HERE
rpcallowip=192.168.1.0/24
rpcport=8766
listen=1
txindex=1
Let me explain each line:
- server=1 — Enables RPC server so miners can connect
- daemon=1 — Runs as background process (Linux only)
- rpcuser/rpcpassword — Authentication credentials your miner will use
- rpcallowip — IP range allowed to connect (adjust to your local network)
- rpcport=8766 — Port miners connect to (default for Clore)
- txindex=1 — Indexes all transactions (helpful for block verification)
Change the rpcpassword to something actually secure. I use a random 20-character string. This password will be visible in your miner configuration, so don’t reuse passwords from important accounts.
The rpcallowip setting depends on your network setup. If your node and miners are all on 192.168.1.x, use that. If you’re using 10.0.0.x or something else, adjust accordingly. The /24 means “allow any IP in this subnet”.
Save and close the file.
Step 4: Initial Blockchain Sync and Verification
Now start the Clore daemon and let it sync the blockchain. This is the part that takes a few hours.
Linux:
clored
The daemon starts in the background. Check sync progress with:
clore-cli getblockchaininfo
Look for the “blocks” and “headers” values. When blocks = headers, you’re fully synced.
Windows:
Run clored.exe from the installation directory. A console window stays open showing sync progress.
Initial sync took me about 3.5 hours on a 100 Mbps connection. Your mileage will vary based on internet speed and hard drive performance.
While syncing, the node downloads every block from genesis to current height. You’ll see progress in the console output. The data shows: First 80% of blocks download quickly, last 20% take longer because newer blocks have more transactions.
Don’t close the terminal/console while syncing. If you need to stop the node:
clore-cli stop
When you restart, it resumes from where it left off.
Once synced, verify your node is actually connected to the network:
clore-cli getpeerinfo
You should see at least 8-10 connected peers. If you see 0 or very few, check your firewall settings — port 8765 (P2P port) needs to be open for outbound connections.
Step 5: Connecting Your Mining Software to the Node
Your node is running and synced. Now we point mining software at it.
I’ll cover the two most common Blake3 miners: lolMiner (AMD-focused) and SRBMiner (multi-GPU). Both support solo mining through RPC connections.
lolMiner Configuration:
Create a batch file (Windows) or shell script (Linux) with your mining parameters:
lolMiner.exe --algo BLAKE3 --pool 192.168.1.50:8766 --user cloreuser --pass YOUR_SECURE_PASSWORD_HERE --wallet YOUR_CLORE_ADDRESS --solo
Replace:
- 192.168.1.50 with your node’s local IP
- cloreuser and password with your clore.conf credentials
- YOUR_CLORE_ADDRESS with your actual Clore wallet address
The –solo flag tells lolMiner this is a solo connection, not a pool. Critical detail: Without this flag, the miner might not submit blocks correctly.
SRBMiner Configuration:
SRBMiner-MULTI.exe --algorithm blake3_alephium --pool 192.168.1.50:8766 --wallet YOUR_CLORE_ADDRESS --password YOUR_SECURE_PASSWORD_HERE
SRBMiner uses blake3_alephium as the algorithm name even though it works for Clore (they’re both Blake3 implementations).
For detailed GPU optimization settings, check our WildRig Multi solo mining guide — many of the Blake3 tuning parameters apply here too.
Start your miner and watch for the connection confirmation. You should see something like:
Connected to node at 192.168.1.50:8766
New work received, target difficulty: XXXXX
If you see connection errors:
- Verify the node IP address is correct
- Check rpcuser/rpcpassword match your clore.conf
- Confirm rpcallowip includes your miner’s IP range
- Make sure the node is actually running (clore-cli getblockchaininfo)
Understanding Blake3 Solo Mining Odds for Clore
Here’s the reality check part. Before you get too excited about solo mining Clore, let’s look at actual block probabilities.
Current Clore network hashrate fluctuates between 50-150 TH/s depending on profitability and market conditions. Block time is 60 seconds, block reward is 10 CLORE.
Quick math for common GPU setups:
Single RTX 3080 (2.8 GH/s):
- At 100 TH/s network: 2.8% of network hashrate
- Expected time to block: ~35-40 days
- Variance means could be 10 days or 90 days
6x RTX 3070 rig (12 GH/s):
- At 100 TH/s network: 12% of network hashrate
- Expected time to block: ~8-10 days
- More consistent than single GPU but still high variance
Mining farm (100 GH/s):
- At 100 TH/s network: Full 100% means you’re the entire network (unrealistic)
- At 500 TH/s network: 20% of hashrate, block every 5 days on average
For comparison with ASIC-mineable Blake3 coins, check our Alephium Blake3 profitability analysis — Alephium has much higher network difficulty making solo mining essentially impossible without massive hashrate.
The data shows: Clore’s relatively low network hashrate makes it one of the few GPU-mineable coins where solo mining with 5-10 cards remains viable. Compare that to something like Ravencoin where you’d need 50+ GPUs for reasonable block odds.
Use our solo mining block calculator to run your own numbers based on current network stats.
Monitoring Your Node and Mining Performance
Once everything’s running, you need to monitor both the node health and mining performance.
Node monitoring commands:
clore-cli getblockcount — Current block height (compare to block explorer)
clore-cli getmininginfo — Network difficulty, hashrate estimates
clore-cli getpeerinfo | grep version — Connected peer count
clore-cli gettxoutsetinfo — Blockchain state verification
Check these every few hours initially. Once you’ve confirmed everything works, daily checks suffice.
For remote monitoring from your phone or another computer, consider setting up TeamViewer or similar remote access. We cover this in detail in our remote mining monitoring guide.
Miner monitoring:
Watch for these metrics in your mining software:
- Accepted shares: Should increase steadily (every 10-30 seconds depending on difficulty)
- Rejected shares: Should be under 1-2%
- Stale shares: Should be under 0.5% with local node
- Hashrate stability: Should vary less than 5% over 10 minutes
If rejected shares exceed 3-4%, something’s wrong. Usually it’s outdated work templates (node fell behind) or connection issues.
One thing I learned the hard way: The node logs grow pretty large over time. On Linux, I set up logrotate to compress old logs. Otherwise you’ll wake up one day to a full SSD.
Electricity Costs and ROI Reality
Let’s talk money. Running a node plus mining rigs costs electricity, and you need to know if it makes sense.
Typical power consumption for Clore solo mining setup:
- Node computer: 15-25W constant
- RTX 3080 mining Blake3: ~220-240W per card (with optimization)
- RTX 3070 mining Blake3: ~130-150W per card
- RX 6800 XT mining Blake3: ~180-200W per card
Let’s run a realistic scenario. You’re running a 6x RTX 3070 rig plus the node:
Daily power consumption:
- 6x RTX 3070 at 140W each: 840W
- System overhead (motherboard, CPU, fans): ~100W
- Node computer: 20W
- Total: ~960W = 23 kWh per day
At $0.12/kWh: $2.76 per day in electricity
Expected mining results at current difficulty (check live stats):
- 6x RTX 3070 = ~12 GH/s
- At 100 TH/s network: Block every ~8-10 days
- Block reward: 10 CLORE
Electricity cost for 8 days: $22.08
Revenue from 1 block: 10 CLORE × current market price
Current CLORE price: price unavailable (check live markets — Clore isn’t on all exchanges yet)
Here’s the honest assessment: Clore profitability depends entirely on your electricity cost and belief in the project. At $0.15/kWh or higher, you’re probably mining at a loss unless CLORE price increases significantly.
I mine Clore solo because I pay $0.08/kWh and I think the project has potential. But if my electricity was $0.15+, I’d probably switch to Ergo solo mining or something more established.
a top miner is the one that fits your electricity cost, not the one with the highest hashrate. That applies to both hardware and coin selection.
Troubleshooting Common Node Setup Issues
Here are problems I’ve hit while setting up Clore nodes, and how to fix them.
Problem: Node won’t sync, stuck at specific block height
Solution: Usually corrupted blockchain data. Stop the node, delete everything EXCEPT wallet.dat in the data directory, restart. It re-downloads the chain from scratch.
clore-cli stop
cd ~/.clore
rm -rf blocks chainstate
clored
Problem: Miner shows “Connection refused” when trying to connect
Check:
- Is the node actually running? (ps aux | grep clored on Linux)
- Is rpcport=8766 in clore.conf?
- Does rpcallowip include your miner’s IP?
- Is a firewall blocking port 8766?
Test the RPC connection manually:
curl --user cloreuser:YOUR_PASSWORD --data-binary '{"jsonrpc":"1.0","id":"test","method":"getblockchaininfo","params":[]}' -H 'content-type:text/plain;' http://192.168.1.50:8766/
If that returns blockchain info, RPC works — problem is in your miner config.
Problem: High stale share rate (over 2%)
Usually means:
- Node is falling behind the network (check getblockcount vs explorer)
- Network connection unstable (check peer count)
- Miner is on different network segment (use wired connection, not WiFi)
Increase node connections in clore.conf:
maxconnections=50
Restart the node.
Problem: Node uses too much RAM
Reduce database cache size in clore.conf:
dbcache=100
Default is usually 300-450 MB. Lowering it reduces RAM usage but might slow down initial sync.
When to Consider Pool Mining Instead
Solo mining Clore isn’t always the right choice. Here’s when pools make more sense.
Switch to pools if:
- Your total hashrate is under 5 GH/s (single weak GPU)
- You need predictable daily income for electricity costs
- Network hashrate jumps significantly (check daily — big farms can swing this)
- You’re testing hardware and need quick payout validation
Our bull market solo mining strategy guide covers the pool vs solo decision in detail, including when to switch based on price movements.
For what it’s worth: I run most of my hashrate solo but keep one GPU pointed at a pool just to validate the setup actually works. Getting daily small payouts from the pool confirms my cards are functioning correctly, while the solo hashrate chases the big blocks.
Frequently Asked Questions
Can I run a Clore node on a Raspberry Pi like Bitcoin nodes?
Technically yes, but it’s not ideal. The Raspberry Pi 4 with 8 GB RAM can run a Clore node, but sync times are long (12+ hours) and performance is marginal. For comparison, we covered Raspberry Pi Bitcoin nodes which work better because Bitcoin has more optimized ARM builds. Clore on Pi works, but a cheap used laptop performs significantly better for similar cost.
How much bandwidth does running a Clore full node use?
Initial sync downloads roughly 15-20 GB (current blockchain size as of early 2026). After that, ongoing bandwidth is pretty light — around 500 MB to 1 GB per day depending on transaction volume and connected peers. That’s manageable on most home internet connections. My node averages about 25 GB per month total bandwidth, which is way less than streaming video.
What happens if my node goes offline while mining?
Your miners lose connection and stop submitting shares until the node comes back online. When you restart the node, it catches up with any missed blocks (usually takes 30 seconds to 2 minutes depending on downtime). Your miners reconnect automatically once the node is responsive again. You don’t lose any blocks unless you actually found one during the offline period, which is statistically very unlikely. I’ve had my node crash three times — each time it caught up in under a minute.
Should I keep my wallet on the mining node computer?
No. The wallet.dat file that gets created contains your private keys. Keep that backed up somewhere secure and preferably not on the same machine running 24/7 as a mining node. I generate receiving addresses from the node wallet, but I keep the actual long-term storage wallet offline on a different computer with backups. If your mining node gets compromised or the hard drive fails, you don’t want to lose your coins.
Can I mine Alephium and Clore to the same node since they’re both Blake3?
No, they’re separate blockchains. You need a separate full node for each coin. They both use Blake3 as the hashing algorithm, but that’s just the proof-of-work function — the actual blockchain consensus rules, block structure, and network protocols are completely different. You can run both nodes on the same computer though. I actually do this — one Clore node and one Alephium node on the same Ubuntu machine, using different ports for RPC (8766 for Clore, 10973 for Alephium). Check our Alephium Blake3 ASIC review for more on mining Alephium specifically.