mirror of https://github.com/zcash/zips.git
Explain link between worker names and job IDs
This commit is contained in:
parent
437100c81c
commit
2a7d10c053
|
@ -57,6 +57,11 @@ Response::
|
|||
``mining.authorize()``
|
||||
----------------------
|
||||
|
||||
A miner MUST authorize a worker in order to submit solutions. A miner MAY
|
||||
authorize multiple workers in the same session; this could be for statistical
|
||||
purposes on the particular server being used. Details of such purposes are
|
||||
outside the scope of this specification.
|
||||
|
||||
Request::
|
||||
|
||||
{"id": 2, "method": "mining.authorize", "params": ["WORKER_NAME", "WORKER_PASSWORD"]}\n
|
||||
|
@ -139,6 +144,8 @@ Request::
|
|||
``WORKER_NAME`` (str)
|
||||
A previously-authenticated worker name.
|
||||
|
||||
Servers MUST NOT accept submissions from unauthenticated workers.
|
||||
|
||||
``JOB_ID`` (str)
|
||||
The id of the job this submission is for.
|
||||
|
||||
|
@ -256,6 +263,12 @@ Does a 256-bit target waste bandwidth?
|
|||
- For the current Equihash parameters (200/9), the Equihash solution dominates
|
||||
bandwidth usage.
|
||||
|
||||
Why does ``mining.submit`` include ``WORKER_NAME``?
|
||||
|
||||
- ``WORKER_NAME`` is only included here for statistical purposes (like
|
||||
monitoring performance and/or downtime). ``JOB_ID`` is used for pairing
|
||||
server-stored jobs with submissions.
|
||||
|
||||
|
||||
Reference Implementation
|
||||
========================
|
||||
|
|
Loading…
Reference in New Issue