Skip to content
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

Worker Specific Hashrate Tracking Extension #113

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

GitGab19
Copy link
Collaborator

This PR adds an extension to directly send a user_identity field inside a SubmitSharesExtended. The user_identity field is limited to a maximum of 32 bytes-length to not increase too much the additional bandwidth consumption for extended shares submissions.

This PR follows #112.

@GitGab19
Copy link
Collaborator Author

GitGab19 commented Dec 18, 2024

After yesterday's call, I noticed that there were some misunderstandings about this PR. So I just pushed a new commit to clarify this point of discussion.

Please @Fi3 @TheBlueMatt review the last commit: 9260a15

@GitGab19 GitGab19 force-pushed the extend-submit-shares-extended branch from 9260a15 to 445048c Compare January 30, 2025 20:11
### Usage Guidelines

- **TLV fields MUST be placed at the end of the message payload.** This ensures compatibility with existing Stratum V2 messages.
- **Order of TLV fields is not significant.** Since all extensions are negotiated beforehand, the recipient MUST scan for TLV fields using their Type identifiers rather than relying on a fixed order.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add that in the extension order matter. If an extension add more the one field you will have first field of ext A is T1 second of ext A is T2 ecc ecc
I think that is better to specify such thing here rather than in every extension to avoid confusion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I will add this clarification in a new commit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Fi3 added in 74f53a5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants