It seems that the network hashrate for randomx is incorrect, based on how many miners are active on DRAGONX and their local hashrates. Since the full node is confused about the network hashrate, the Mining GUI in SDX reports a bad estimation of "time to mine a block". The bug is not in the SDX mining GUI, all it is doing is dividing two numbers, network hashrate and local hashrate.
Local hashrate seems to be reported correctly, which can be seen by changing the number of mining threads on a mining node and seeing how it changes.
It seems that the network hashrate for randomx is incorrect, based on how many miners are active on DRAGONX and their local hashrates. Since the full node is confused about the network hashrate, the Mining GUI in SDX reports a bad estimation of "time to mine a block". The bug is not in the SDX mining GUI, all it is doing is dividing two numbers, network hashrate and local hashrate.
Local hashrate seems to be reported correctly, which can be seen by changing the number of mining threads on a mining node and seeing how it changes.
After a few layers of RPC wrappers the function GetNetworkHashPS() in src/rpc/mining.cpp is the function which calculates network hashrate (nethash).
Nethash is a function of two variables, the averaging window and a block height. By default the RPC getmininginfo uses an averaging window of 120 blocks.
The function finds the chain work of the two block heights (block height X and X-120) and then divides by the time difference of those two blocks.
After a few layers of RPC wrappers the function `GetNetworkHashPS()` in src/rpc/mining.cpp is the function which calculates network hashrate (nethash).
Nethash is a function of two variables, the averaging window and a block height. By default the RPC `getmininginfo` uses an averaging window of 120 blocks.
The function finds the chain work of the two block heights (block height X and X-120) and then divides by the time difference of those two blocks.
It seems that the network hashrate for randomx is incorrect, based on how many miners are active on DRAGONX and their local hashrates. Since the full node is confused about the network hashrate, the Mining GUI in SDX reports a bad estimation of "time to mine a block". The bug is not in the SDX mining GUI, all it is doing is dividing two numbers, network hashrate and local hashrate.
Local hashrate seems to be reported correctly, which can be seen by changing the number of mining threads on a mining node and seeing how it changes.
After a few layers of RPC wrappers the function
GetNetworkHashPS()in src/rpc/mining.cpp is the function which calculates network hashrate (nethash).Nethash is a function of two variables, the averaging window and a block height. By default the RPC
getmininginfouses an averaging window of 120 blocks.The function finds the chain work of the two block heights (block height X and X-120) and then divides by the time difference of those two blocks.