Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

--notify-work explanation #2695

Closed
daniel-lucio opened this issue Oct 18, 2016 · 2 comments
Closed

--notify-work explanation #2695

daniel-lucio opened this issue Oct 18, 2016 · 2 comments
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@daniel-lucio
Copy link

could you elaborate when/how to use this parameter?
@NikVolf
Copy link
Contributor

NikVolf commented Oct 18, 2016

@daniel-lucio
when provided with url, parity will make a HTTP POST request each time new mining job is available. The payload will be json-encoded parameters of the mining job.

using
--notify-work http://your-mining-service1.com

@keorn keorn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Oct 18, 2016
@NikVolf NikVolf added M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer. and removed Z1-question 🙋‍♀️ Issue is a question. Closer should answer. labels Oct 18, 2016
@daniel-lucio
Copy link
Author

Nice!, like a proxy, all my ethminer points to my parity, and my parity points to the pool :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@NikVolf @daniel-lucio @keorn @rphmeier