From c9dec9e90cc797992b37e6fda954032b03a9fb81 Mon Sep 17 00:00:00 2001 From: plebhash Date: Sat, 26 Oct 2024 21:24:54 -0300 Subject: [PATCH] wip clarify DeclareMiningJob.Success + DeclaraMiningJob.Error --- 06-Job-Declaration-Protocol.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/06-Job-Declaration-Protocol.md b/06-Job-Declaration-Protocol.md index 0698814..590720a 100644 --- a/06-Job-Declaration-Protocol.md +++ b/06-Job-Declaration-Protocol.md @@ -100,6 +100,12 @@ More specifically, the `SipHash 2-4` variant is used. Aside from the preimage (w ### 6.3.5 `DeclareMiningJob.Success` (Server -> Client) +A response sent by JDS acknowledging some Custom Job declaration via `DeclareMiningJob`. + +xxx todo xxx clarify `new_mining_job_token` with regards to: +- async mining (`SetCustomMiningJob`) +- potential JDS signature + | Field Name | Data Type | Description | | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | request_id | U32 | Identifier of the original request | @@ -107,6 +113,10 @@ More specifically, the `SipHash 2-4` variant is used. Aside from the preimage (w ### 6.3.6 `DeclareMiningJob.Error` (Server->Client) +A response sent by JDS rejecting some Custom Job declaration via `DeclareMiningJob`. + +This should be a trigger for fallback into some other Pool+JDS or solo mining. + | Field Name | Data Type | Description | | ------------- | --------- | ------------------------------------------------------ | | request_id | U32 | Identifier of the original request |