Alexander Blair
Alexander Blair
Whatever you're connecting to isn't handing you a block template in time. Make sure you set one of your pools to default: true.
This can only split on full miners, it's not able to split partial miners, so low counts of miners can break this splitting.
You're using a non-supported pool. Supported pools send over the raw BT along with several data paramaters about nonces.
If you changed the user agent, this would break. The UA is used to identify inbound proxy connections.
Difficulty shifts by the upstream pool, which causes a new JobID. The blob doesn't change, but the difficulty target does, which causes downstream changes, as it would. As for the...
This works correctly, but it depends on how many miners you have connected as well. It will only slice off full miners, so if you have 100% identical rigs, and...
This already supports multithreading, --workers= lets you limit the number of threads generated. The idea is that it will natively spawn 1 thread per CPU.
API Spec: Miners Ordered by IP Miners Grouped by Worker (Password) Miners Grouped by Address Miner Details (Hashes, Hashrate, Avg hash time, Last hash, Best Share?)
This is occurring because the MM proxy does not properly update the reserved_offset, as we use this in nodejs-pool based pools, it's corrupting the coinbase tx_extra. You can patch this...
Yeah, the quick and simple way if you're using a semi-stock nodejs is to just patch MM to properly increase the offset by a number of bytes, MM always inserts...