-
Notifications
You must be signed in to change notification settings - Fork 127
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
MG understands SubmitSolution
as a valid JD message
#1003
MG understands SubmitSolution
as a valid JD message
#1003
Conversation
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
3e17dec
to
d3514de
Compare
SubmitSolution
as a valid JD message
It appears to me that you are sending a The submitted solution should contain the transactions of DeclareMiningJob, so you have to take a real. Also, to check that JDS submit solution works, you have to to prevent submit solution from JDC (by patching the JDC not doing so), and clearly the JDS connected to a bitcoin node. There is also the possibility to use your signet, mine some non empty blocks and use those blocks for the purpose. What you are trying to do is tricky, ping me if you need help |
I found #1002 while working on #912, and while working there I did follow the message flow indicated above. But the MG behavior that I'm describing on #1002 happens independently of these messages are not related to it. So I intentionally left these messages out of the flow. We just need an atomic way to get MG to parse a The messages listed above should be ignored on the context of this issue. |
todo: try with #949 |
250b4d7
to
d3514de
Compare
d3514de
to
1b7d768
Compare
f7ac98b
to
6a17642
Compare
6a17642
to
53ee8a9
Compare
close #1002