You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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.
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):The object in the
params
list here is just the object returned from the regulargetwork
.The text was updated successfully, but these errors were encountered: