You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2020. It is now read-only.
Nodejs-pool and Node-cryptonote-pool uses the time when the block template was created as the timestamp when sending jobs to miners and is not updated after some time passes. Pool code should be modified to adjust the timestamp to when the block is actually found. This would help reduce the number of delays in lwma-4 difficulty algorithm
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Rejactor pool code to update block timestamp to when block is found
Refactor pool code to update block timestamp to when block is found
Nov 17, 2018
Pools and miners already have the ability to select the timestamp because they can have their own nodes who create the timestamp. It allows them to assign a more accurate timestamp like BTC et al instead of the incorrect timestamps they currently assign.
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Nodejs-pool and Node-cryptonote-pool uses the time when the block template was created as the timestamp when sending jobs to miners and is not updated after some time passes. Pool code should be modified to adjust the timestamp to when the block is actually found. This would help reduce the number of delays in lwma-4 difficulty algorithm
The text was updated successfully, but these errors were encountered: