rename target message fields, aligning with spec cleanup - #845
Draft
plebhash wants to merge 2 commits into
Draft
Conversation
stratum renamed `SetTarget.maximum_target` to `target` and `UpdateChannel.maximum_target` to `max_target`, so that each field matches the spec's split between operating values set by the server and caps requested by the client. Local bindings that hold the requested cap follow the field name. stratum-mining/sv2-spec#228
…get-fields Only here so Integration Tests resolve stratum-core against the companion stratum PR instead of main. Drop this commit once that PR merges, then update stratum-core to stratum's new main HEAD.
This file contains hidden or 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
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.
companion stratum-mining/stratum#2368
aligned with stratum-mining/sv2-spec#228
draft for now, I'll make it ready for review whenever we decide to merge the spec change