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

GetWork notifications over Websocket #1032

Closed
termoose opened this issue Feb 15, 2018 · 2 comments · Fixed by #1410
Closed

GetWork notifications over Websocket #1032

termoose opened this issue Feb 15, 2018 · 2 comments · Fixed by #1410
Milestone

Comments

@termoose
Copy link

Continuously polling getwork for changes (over HTTP or Websocket) is not really desirable and is the only way to get new work for miners at the moment.

I propose having a notifywork method on the websocket RPC, similar to notifyblocks. This starts a subscription on messages that could look something like this (suggestion):

{
	"jsonrpc": "1.0",
	"method": "latestwork",
	"params": [{
		"data": "block_header",
		"target": "some_target"
	}]
}

The object in the params list here is just the object returned from the regular getwork.

@davecgh
Copy link
Member

davecgh commented Mar 2, 2018

This is a good idea. However, it will require some infrastructure changes in terms of allowing notifications of when block templates are available to propagate and result in sending such notifications.

@dnldd
Copy link
Member

dnldd commented Apr 22, 2018

Taking this on

@davecgh davecgh added this to the 1.3.0 milestone Apr 30, 2018
@davecgh davecgh modified the milestones: 1.3.0, 1.4.0 Aug 8, 2018
@davecgh davecgh modified the milestones: 1.4.0, 1.5.0 Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants