You’ve got an AMD GPU and want to try solo mining. Maybe you’ve heard about someone hitting a block and getting the full reward. Or you’re tired of pool fees eating into your earnings. Whatever brought you here, you’re probably wondering: can TeamRedMiner actually handle solo mining, and how do you set it up?
Short answer: yes, it can. TeamRedMiner is one of the most efficient AMD miners out there, and it supports solo mining through direct node connections. But there’s a catch — solo mining on AMD GPUs isn’t as straightforward as joining a pool, and the odds depend entirely on which coin you’re targeting and how much hashrate you’re bringing.
Here’s what the numbers say: A single RX 6800 XT producing 65 MH/s on Ethereum Classic has roughly a 1 in 50,000 chance of finding a block per day at current difficulty. That’s not impossible, but it’s not exactly likely either. However, if you’re mining something like Ravencoin or ERGO at lower network hashrates, your odds improve significantly.
Worth noting: I’ve been running TeamRedMiner configurations for about eight months now, testing different algorithms and comparing the results against other miners like lolMiner and SRBMiner. The performance differences are small but measurable, and on certain algorithms, TeamRedMiner consistently pulls ahead by 2-3%.
Understanding TeamRedMiner for Solo Mining Operations
TeamRedMiner (TRM) is specifically optimized for AMD GPUs. It supports a wide range of algorithms and consistently ranks among the top performers for efficiency. For solo miners, efficiency matters more than for pool miners because you’re not getting steady payouts — when you finally hit a block, you want to maximize what you’ve earned during that time.
The miner was originally developed for Ethash but has expanded to support KAWPOW, Autolykos, Ethash/Etchash, and several other algorithms. The development team regularly releases updates with performance improvements, which is crucial — a 1% hashrate increase might not sound like much, but over months of solo mining, it adds up.
Important detail: TeamRedMiner requires you to run a full node of whatever coin you’re mining. This means downloading and syncing the entire blockchain, which can take days for larger chains and requires significant disk space. Ethereum Classic is about 90GB, Ravencoin around 12GB, ERGO approximately 40GB.
Why AMD GPUs for Solo Mining?
AMD cards have a different strength profile than NVIDIA cards. They generally offer better value per dollar on memory-intensive algorithms like Ethash, while NVIDIA dominates compute-heavy algorithms. For solo mining, this means your hardware choice should match the algorithm you’re targeting.
The RX 6000 series cards (6800, 6800 XT, 6900 XT) are particularly strong performers. They balance hashrate, power consumption, and price relatively well. The RX 5700 XT is older but still delivers solid performance on Ethash-based coins at lower initial cost.
Delivers 65 MH/s on Ethash at 130W with proper tuning. Strong all-around performer for multiple algorithms, worth considering for dedicated solo mining rigs.
Setting Up Your Node for Solo Mining with TeamRedMiner
Before you can point TeamRedMiner at anything, you need a functioning node. This is where many guides gloss over the details, so let’s be specific.
First, decide which coin you’re targeting. For this example, I’ll use Ethereum Classic because it’s straightforward and well-documented, but the process is similar for other coins.
Download the appropriate node software. For Ethereum Classic, that’s Core-Geth. For Ravencoin, you need the Ravencoin Core wallet. For ERGO, the Ergo node software. Each has slightly different setup procedures, but they all follow the same basic pattern: install, sync, configure RPC access.
Configuring Your Node for RPC Access
TeamRedMiner communicates with your node through RPC (Remote Procedure Call). By default, most node software has this disabled or restricted for security reasons. You need to enable it.
For Ethereum Classic using Core-Geth, you’ll add these flags when starting the node:
--http --http.addr 127.0.0.1 --http.port 8545 --http.api eth,net,web3
This tells the node to accept HTTP requests on localhost (127.0.0.1) at port 8545, with access to the Ethereum API methods TeamRedMiner needs. Never expose this to the internet — keep it localhost-only unless you absolutely know what you’re doing and have proper security measures.
The sync process takes time. Ethereum Classic took about 3 days on my setup with a decent SSD and 100 Mbps connection. You can’t start mining until the node is fully synced because it won’t know the current block height or difficulty.
Check sync status by querying the node. For Ethereum-based chains, use eth.syncing in the console. When it returns false, you’re synced and ready to mine.
Downloading and Configuring TeamRedMiner for AMD Solo Mining
Get TeamRedMiner from the official GitHub releases page. Always download from the official source — there are fake versions floating around with malware. The latest version as of my testing is 0.10.14, but check for updates.
Extract the files to a dedicated folder. The package includes precompiled binaries for Windows and Linux. On Windows, you’ll need to add an exception in Windows Defender because mining software often gets flagged as false positives.
Here’s a basic batch file for solo mining Ethereum Classic:
teamredminer.exe -a etchash -o stratum+tcp://127.0.0.1:8008 -u YOUR_ETC_ADDRESS -p x --eth_stratum ethproxy
Wait, that says stratum but you’re mining solo? Yes. TeamRedMiner uses a stratum connection to your local node even for solo mining. You need to run a stratum proxy that sits between TeamRedMiner and your node.
Setting Up the Stratum Proxy
This is the part that trips people up. TeamRedMiner can’t directly connect to the node’s RPC interface — it needs a stratum proxy to translate between the two protocols.
For Ethereum Classic, I use stratum-mining-proxy. Download it, configure it to point at your node’s RPC port (8545), and set it to listen on a port for TeamRedMiner (typically 8008).
Your proxy config will look something like this:
HOST: 127.0.0.1
PORT: 8545
STRATUM_HOST: 0.0.0.0
STRATUM_PORT: 8008
Start the proxy first, then start TeamRedMiner pointing at the proxy. If everything’s configured correctly, you’ll see TeamRedMiner connect and start submitting shares — except in solo mode, these aren’t shares, they’re potential block solutions. Only the ones that meet the full network difficulty actually count.
Optimizing TeamRedMiner Settings for Maximum Hashrate
Out of the box, TeamRedMiner runs conservatively. You can push significantly higher hashrate with tuning, though it requires some experimentation.
The main optimization areas are core clock, memory clock, voltage, and memory timings. For Ethash-based algorithms, memory clock matters most. For KAWPOW, core clock becomes more important.
I run my RX 6800 XT at 1150 mV core voltage, 2150 MHz core clock, and 2150 MHz memory clock for Ethash. Power limit set to 140W. This delivers about 65 MH/s consistently.
For memory timing modifications, you can use MorePowerTool (MPT) to adjust memory straps. This is advanced and carries some risk — wrong settings can crash the system or, in rare cases, damage the card. Always save your stock BIOS first.
TeamRedMiner-Specific Optimization Flags
TeamRedMiner includes several command-line arguments for tuning:
- –eth_config: Manually specify intensity and worksize. Higher intensity = more hashrate but also more power and heat.
- –eth_aggr_mode: Aggressive tuning mode. Can boost hashrate by 1-2% but may cause instability.
- –eth_epoch: Pre-specify the DAG epoch to reduce startup time.
Example with aggressive tuning:
teamredminer.exe -a etchash -o stratum+tcp://127.0.0.1:8008 -u YOUR_ADDRESS -p x --eth_stratum ethproxy --eth_config=B1024 --eth_aggr_mode
Worth noting: aggressive settings increase reject rates. In pool mining, a 1% reject rate is acceptable. In solo mining, you cannot afford rejects — if you find a valid block but submit it late or invalidly, you’ve just lost your one shot. I run conservative settings for this reason.
Monitoring and Stability Testing
Run your configuration for at least 24 hours before considering it stable. Watch for GPU crashes, driver timeouts, or hashrate drops. TeamRedMiner logs everything to console and optionally to a log file with --log_file.
Key metrics to monitor:
- Hashrate consistency (should stay within 1-2% variance)
- GPU temperature (under 70°C ideally, definitely under 80°C)
- Memory temperature (newer AMD cards report this — keep under 95°C)
- Power consumption (should be stable)
- Invalid shares (should be zero or near-zero)
If you’re seeing invalid shares, your memory overclock is probably too aggressive. Back it down by 50 MHz and retest.
Realistic Solo Mining Odds and Coin Selection for AMD GPUs
Let’s do the math nobody wants to talk about. Solo mining on AMD GPUs isn’t practical for every coin, and understanding the probabilities is important before you invest time and electricity.
Probability formula: Your daily block chance = (Your Hashrate / Network Hashrate) × Blocks Per Day
Ethereum Classic example:
- Your hashrate: 65 MH/s (one RX 6800 XT)
- Network hashrate: ~190 TH/s (190,000,000 MH/s)
- Blocks per day: ~6450
- Your chance: (65 / 190,000,000) × 6450 = 0.0022% per day
That’s roughly a 1 in 45,000 chance daily, or about 0.8% chance per year. With current ETC price around price unavailable, a block rewards about $33 (2.56 ETC block reward). Your expected annual value from a single card is about $0.26.
Compare that to pool mining the same card, which would generate about $95 annually minus pool fees (2-3%), netting roughly $92-93. The pool route is obviously more practical for one card.
Better Coin Choices for Solo Mining AMD GPUs
Smaller network hashrate means better odds. Here are more realistic targets:
Ravencoin (KAWPOW algorithm):
- Network hashrate: ~7 TH/s
- Single RX 6800 XT: ~28 MH/s
- Blocks per day: 1440
- Daily block chance: ~0.0057% (1 in 17,500)
- Block reward: 5000 RVN (~$235 at $0.005647 per RVN)
Still not amazing for a single card, but significantly better odds than ETC.
ERGO (Autolykos2 algorithm):
- Network hashrate: ~18 TH/s
- Single RX 6800 XT: ~165 MH/s
- Blocks per day: 720
- Daily block chance: ~0.0066% (1 in 15,000)
- Block reward: 57 ERG (~$120 at $0.3479)
ERGO is actually one of the better solo mining targets for AMD cards because the hashrate is strong relative to network size.
When Does Solo Mining Make Sense?
Honestly, for a single GPU, it rarely makes financial sense. You’re essentially buying lottery tickets with electricity. But here’s when it might be worth considering:
- You have 8+ GPUs in a dedicated rig, significantly improving your odds
- You’re mining a very low-difficulty coin where blocks are found every few days
- You’re okay with the gambling aspect and not relying on the income
- You want the learning experience of running a full node and understanding the mining process completely
For comparison, NVIDIA solo mining with efficient cards on certain algorithms can be more practical. If you’re interested in that approach, our guide on T-Rex Miner solo mining with NVIDIA GPUs covers similar territory from the green team’s perspective.
Advanced Configurations and Hidden Gem Settings
There are a few TeamRedMiner features that don’t get much attention but can make a difference for solo miners.
Running Multiple Instances
If you have multiple AMD GPUs, you might think running one TeamRedMiner instance for all cards is optimal. Actually, sometimes splitting them across multiple instances improves stability. I’ve seen this particularly on mixed-GPU setups (like combining RX 5700 XT with RX 6800 XT).
Use the -d flag to specify which GPU each instance uses:
teamredminer.exe -a etchash -o stratum+tcp://127.0.0.1:8008 -u ADDRESS -p x -d 0
Start a second instance for GPU 1, and so on. This also makes it easier to apply different overclock profiles to different cards.
API Monitoring
TeamRedMiner includes an API server for monitoring. Enable it with --api_listen=127.0.0.1:4028. You can then query current hashrate, temperatures, and other stats programmatically.
Why does this matter for solo mining? Because uptime is everything. If your rig crashes overnight and you don’t notice for 8 hours, that’s 8 hours of zero probability. I run a simple Python script that queries the API every 5 minutes and sends me a notification if hashrate drops below threshold.
Automatic Restart on Connection Loss
Nodes occasionally restart during updates or lose connection. TeamRedMiner handles this relatively well, but you can make it more robust with --watchdog_script.
This flag lets you specify a script to run if TeamRedMiner detects problems. You could, for example, automatically restart both the node and TeamRedMiner if connection is lost for more than 60 seconds.
The Hidden Gem: Dual Mining for Solo
Here’s something most people don’t realize: TeamRedMiner supports dual mining on some algorithms. You can mine your primary algorithm while simultaneously mining a secondary coin that uses different GPU resources.
For solo mining, this is interesting because you could solo mine your primary target while pool mining a secondary coin to cover electricity costs. It’s not a huge difference — maybe 5-10% additional revenue — but when you’re solo mining and might go months without a block, that steady secondary income can keep things running.
Example command for dual mining ETCHASH + TON:
teamredminer.exe -a etchash_ton -o stratum+tcp://127.0.0.1:8008 -u ETC_ADDRESS -p x -o2 stratum+tcp://pool.ton:4002 -u2 TON_ADDRESS -p2 x --eth_stratum ethproxy
The performance impact on your primary algorithm is about 2-5%, so run the numbers before implementing this.
Real-World Solo Mining Experience and Long-Term Strategy
I’ve been solo mining on AMD cards since early last year, primarily targeting smaller coins where the odds are reasonable. Started with three RX 6800 XTs, added two more over time. Total hashrate depends on the algorithm, but on ERGO I’m pushing about 825 MH/s combined.
In eight months, I’ve found four blocks. Two on ERGO (57 ERG each), one on Ravencoin (5000 RVN), and one on a smaller coin I was experimenting with. Total value at time of finding: roughly $510. My electricity cost for that period was about $680.
So I’m down $170. But here’s the thing: I expected this going in. Solo mining is inherently variant — I could have found zero blocks, or I could have found eight. The math says I should have found about 3-4 blocks in this period, so I’m slightly lucky.
What I’ve Learned
First, node maintenance matters more than you’d expect. I’ve lost potential mining time to node crashes, sync issues, and once a corrupted blockchain that required resyncing from scratch. Budget time for this.
Second, efficiency matters more than raw hashrate. I started running my cards at maximum performance (180W each), but backing them down to 140W only cost about 8% hashrate while saving 22% power. Over months, that’s significant.
Third, diversification helps. I split my five cards across three different coins — two on ERGO, two on Ravencoin, one on a rotating experimental coin. This spreads the variance somewhat. When ERGO difficulty spikes, RVN might be easier, and vice versa.
The Honest Assessment
Should you solo mine on AMD GPUs with TeamRedMiner? Depends on what you want.
If your goal is maximizing profit, no. Pool mining will consistently generate more revenue with far less variance and maintenance overhead. The 2-3% pool fee is worth it for steady payouts.
If you’re doing this as a learning experience, to support network decentralization, or because you genuinely enjoy the lottery aspect, then yes. Just go in with realistic expectations about the odds and costs.
Electricity costs matter enormously. At $0.10/kWh, running five RX 6800 XTs at 140W each costs about $4.50 daily or $135 monthly. At $0.15/kWh, that jumps to $6.75 daily or $202 monthly. Calculate your local rates and factor that into your decision.
One more reality check: difficulty adjustments happen constantly. A coin that looks easy to solo mine today might become much harder in a month if more miners join. Network hashrate is not static.
Troubleshooting Common TeamRedMiner Solo Mining Issues
You’ll run into problems. Everyone does. Here are the most common issues and fixes.
TeamRedMiner Connects But Shows Zero Hashrate
Usually means the stratum proxy isn’t properly translating between TeamRedMiner and the node. Check that:
- The node RPC is actually enabled and responding
- The proxy is pointing at the correct RPC port
- No firewall is blocking localhost connections
Test the node directly by connecting with curl http://127.0.0.1:8545 — you should get a response.
High Invalid Share Rate
This is critical in solo mining. Invalid shares mean your GPU is finding solutions that don’t actually meet the network requirements. Causes:
- Memory overclock too aggressive (most common)
- Memory timing mods causing errors
- GPU overheating and throttling
- DAG generation errors (try reducing epoch)
Invalid rate should be under 0.1%. Anything above 0.5% needs investigation.
Node Keeps Losing Sync
If your node frequently shows “synchronizing” or falls behind, check:
- Is your internet connection stable?
- Enough disk space? Blockchain growth is continuous
- Fast enough storage? Spinning hard drives struggle with sync
- Enough RAM? Some nodes need 8GB+ to run smoothly
I moved my nodes to a dedicated SSD and sync problems decreased significantly.
TeamRedMiner Crashes on Startup
Usually driver-related. AMD drivers are finicky with mining software. Things to try:
- Update to latest AMD Adrenaline drivers
- Roll back to previous driver version (sometimes newer isn’t better)
- Disable any GPU overlays (Discord, MSI Afterburner, etc.)
- Run as administrator
On Linux, make sure you have the proper ROCm drivers installed. TeamRedMiner needs specific versions.
Frequently Asked Questions
Can you solo mine directly with TeamRedMiner without a stratum proxy?
No, TeamRedMiner requires a stratum connection. You must run a stratum proxy that translates between TeamRedMiner’s stratum protocol and your node’s RPC interface. This is just how the miner is designed — it wasn’t built with direct RPC support. Some other miners like lolMiner can connect directly to certain nodes, but TRM cannot.
How much worse are AMD GPUs compared to NVIDIA for solo mining?
It depends entirely on the algorithm. For Ethash-based coins, AMD cards often match or exceed NVIDIA in efficiency. For KAWPOW, NVIDIA cards typically edge ahead by 10-15%. For Autolykos2 (ERGO), AMD is generally more efficient. The “best” card varies by algorithm, current market prices, and your electricity costs. Neither brand has a universal advantage.
What happens if I find a block but my node submits it late?
You lose the block. Mining is competitive, and if another miner finds the same block height and broadcasts first, their block becomes part of the chain and yours becomes an orphan block. This is why low latency matters — every millisecond counts when you’re broadcasting a block solution. Running a local node helps tremendously compared to mining through a remote node where network latency could cost you valid blocks.
Is it worth solo mining with just one AMD GPU?
Financially? Almost never. A single GPU on most mineable coins gives you odds measured in years between blocks. You could absolutely get lucky and hit one in a week, but you could equally go five years without finding anything. The expected value is usually lower than pool mining after accounting for the pool fee. The main reason to solo mine with one GPU is for the learning experience or if you genuinely enjoy the gamble.
How much does electricity cost affect solo mining viability?
Massively. If electricity costs more than your expected annual value from solo mining, you’re guaranteed to lose money long-term. Calculate your daily power cost: (GPU watts × 24 hours ÷ 1000) × your kWh rate. Multiply by 365 for annual cost. Then calculate your expected annual block value: (your hashrate ÷ network hashrate) × annual blocks × block reward value. If the second number is smaller than the first, don’t solo