Fix Miningcore SHA256 Vardiff
Budget: $10 – $30 USD
My SHA256 pool is online and shares are trickling in, yet a 200 TH/s rig rented through MiningRigRentals barely registers 0–30 TH/s once it connects. The same hardware points to molepool without issue, and my Scrypt pool on this very server performs flawlessly, so the fault clearly lies in my Miningcore configuration.
I suspect the culprit is the variable-difficulty block in the pool’s json—specifically the startingDiff and maxDelta values. MiningRigRentals also reports “unable to authenticate with the pool,” so an auth‐related mis-setting may be compounding the low hashrate.
Here is what I need:
• Review my current Miningcore SHA256 pool configuration (Docker-compose stack on Ubuntu).
• Tune both vardiff parameters—starting difficulty and max delta—so the rental rig shows its full 200 TH/s and share frequency looks normal.
• If the auth error is tied to a mis-handled password or extranonce setting, fix that as well.
• Provide the adjusted json (or quote the exact diff) and a short note on what changed and why, so I can replicate it on future pools.
I can supply full access to the pool’s config files and live logs, and I’m happy to run any test commands you need. Once the pool holds the rental at the expected hashrate for at least one hour and MiningRigRentals stops flagging authentication issues, I’ll consider the job complete.
I suspect the culprit is the variable-difficulty block in the pool’s json—specifically the startingDiff and maxDelta values. MiningRigRentals also reports “unable to authenticate with the pool,” so an auth‐related mis-setting may be compounding the low hashrate.
Here is what I need:
• Review my current Miningcore SHA256 pool configuration (Docker-compose stack on Ubuntu).
• Tune both vardiff parameters—starting difficulty and max delta—so the rental rig shows its full 200 TH/s and share frequency looks normal.
• If the auth error is tied to a mis-handled password or extranonce setting, fix that as well.
• Provide the adjusted json (or quote the exact diff) and a short note on what changed and why, so I can replicate it on future pools.
I can supply full access to the pool’s config files and live logs, and I’m happy to run any test commands you need. Once the pool holds the rental at the expected hashrate for at least one hour and MiningRigRentals stops flagging authentication issues, I’ll consider the job complete.