Remove difficulty check for work_generate #94
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deprecated since v22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Network difficulty is deprecated since node v22. The proxy will now default to SEND difficulty fffffff800000000 if the difficulty is not specified for the work_generate command.
The previous version will work fine too because the v22 node will still return default values as network_current.
The user typically defines the difficulty when requesting pow, for example, the RECEIVE-difficulty which is 64x lower.
Also disables the watch_work since that is deprecated in v22. Though it will not do any harm to send along the parameter. Will be removed completely at a later stage.