-
Notifications
You must be signed in to change notification settings - Fork 854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This..... dosent work. #169
Comments
jobRebroadcastTimeout does not update correctly the mining difficulty if the mining difficulty in THE SAME BLOCK changes with time. |
so if the mining difficulty is adjusted with time, like in some adjusted darkgravitywave algorithm that scale difficulty down with TIME ( for example, progressively lower difficulty if there is a long stale tip..... ) ..... the pool dosent brodcast that info, and the miners keeps trying to mine a higher difficulty block, and if a block is found, the difficulty bits dosent match the pow difficulty bits. |
When a new block is found, the pool sends a new getblocktemplate and checks the new difficulty for the next block. jobrebrodcast timeout should also do this. Or a new option could be added for coins that changes difficulty in the same block over time. |
.on('broadcastTimeout', function(){
|
RESULT : 2019-03-09 12:38:56 [Pool] [lightningcash gold] (Thread 8) No new blocks for 30 seconds - updating transactions & rebroadcasting work ReferenceError: rpcdata is not defined |
Further debugging gives this : 2019-03-09 13:02:32 [Pool] [lightningcash gold] (Thread 5) No new blocks for 30 seconds - updating transactions & rebroadcasting work |
The text was updated successfully, but these errors were encountered: