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.

Sign up for GitHub

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

Jump to bottom

Signed (verified) custom job token #551

Closed
pavlenex opened this issue Apr 22, 2023 · 1 comment
Closed

Signed (verified) custom job token #551

pavlenex opened this issue Apr 22, 2023 · 1 comment
Labels
sv2 pool

Comments

@pavlenex
Copy link
Collaborator

Originally proposed by Fi3

When a downstream (JnClient) sends a SetCustomMiningJob to the pool, the pool must verify that the job token is the JnServer signature of the merkle root obtained from the proposed job with extranonce 0.
@pavlenex pavlenex added this to the MVP3 milestone May 5, 2023
@pavlenex pavlenex removed this from the MVP3 milestone Jan 16, 2024
@pavlenex
Copy link
Collaborator Author

I think this one can be closed in favor of #1053 since to me they seem like a duplicate.

@pavlenex pavlenex closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sv2 pool
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pavlenex