Fix Miningcore Hashrate Bug
Budget: $30 – $250 USD
I run a Bitcoin pool on Miningcore backed by Redis and the only metric still misbehaving is hashrate. Every miner—whether it’s the Bitaxe unit that should show 1.2 TH/s or the Pi-5 CPU miner that should read 1.1 MH/s all report different numbers.
So far I have double-checked each miner’s configuration files, but that change alone had no effect. Because the discrepancy affects all miners and is constant, I’m convinced the issue sits somewhere inside Miningcore’s hashrate logic, the share-to-hash conversion, or the way the Redis cache feeds the API endpoint.
I have tested my port diff settings with a friends pool and all ports are configured correctly. Its a miningcore and redis issue.
If you know your way around C#, Redis, Stratum and Miningcore internals, this should be quick work.
So far I have double-checked each miner’s configuration files, but that change alone had no effect. Because the discrepancy affects all miners and is constant, I’m convinced the issue sits somewhere inside Miningcore’s hashrate logic, the share-to-hash conversion, or the way the Redis cache feeds the API endpoint.
I have tested my port diff settings with a friends pool and all ports are configured correctly. Its a miningcore and redis issue.
If you know your way around C#, Redis, Stratum and Miningcore internals, this should be quick work.