-
Notifications
You must be signed in to change notification settings - Fork 152
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
Fix stratum message order #498
Conversation
On Braiins pool, before:
after:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Would you be able to test this on a few other pools as well?
Next to Braiins only ckpool, no difference there. Would be good to have someone check Public and Ocean as well. I haven't set those up yet. Can anyone enlighten me on what happens if the pool doesn't acknowledge the version mask, as seen in the first log? |
Sidenote: should it actually continue hashing if a setup message failed? At least it should flag it somewhere that the init didn't completely succeeded so the user can be warned. |
Ocean before:
After:
Error on |
Public Pool is also fine. Before:
After:
Fun observation: it never responds with id 4 of the
|
Here are a couple more... is this looking good?
|
LGTM, they all respond with the version mask set, which is the response on the mining.configure. There might need to a bit better handing of setup message errors, f.e. the antpool with the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Missing TODO from #84, it should start with
mining.configure
.