Allow workshare hashes in coinbase ETX data #2509
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
jdowning100
requested review from
wizeguyy,
kiltsonfire and
gameofpointers
as code owners
jdowning100
force-pushed
the
workshare-hash
branch
2 times, most recently
from
5fd023d to
dc6d197
Compare
kiltsonfire
approved these changes
Feb 3, 2025
gameofpointers
approved these changes
Feb 3, 2025
jdowning100
force-pushed
the
workshare-hash
branch
from
dc6d197 to
8537603
Compare
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.
For the normal case, the ETX data will now be: 1 byte lockup byte, 32 byte workshare hash, for 33 bytes total. Pools will have to parse out the first byte of the data.