Specifications/zkSNARK_NiceHash_v1.0.txt at master · nicehash/Specifications · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
-------------------------------------------------------------------------
			        NiceHash presents
=========================================================================
		zkSNARK mining protocol modification v1.0
=========================================================================

I. Introduction & Concept
II. Specifications (RFC)
III. Contact


I. Introduction & Concept
-------------------------

This specification is placing additional restriction for nonce length provided by the pools.


II. Specifications (RFC)
-------------------------

To prevent duplicate shares and properly distribute work load, NiceHash adds additional byte
to nonce prefix for the miners, which sets nonce prefix to the expected 2 bytes. Pools MUST
provide nonce prefix of length exactly 1 byte to be compatible with NiceHash.

Pool traffic:
-> subscribe
{
    "id":1,
    "jsonrpc":"2.0",
    "method":"mining.subscribe",
    "params":["NiceHash","1.0.0"]
}
<- subscribe response
{
    "id":1,
    "jsonrpc":"2.0",
    "result":[null,"7c",1],
    "error":null
}

Miner traffic:
-> subscribe
{
    "id": 0,
    "jsonrpc":"2.0",
    "method": "mining.subscribe",
    "params": ["iceriver/1.0.0", "1.0.0"]
}
<- subscribe response
{
    "id":0,
    "jsonrpc":"2.0",
    "error":null,
    "result":[null,"7cb1",2]
}


In the provided traffic example, the pool provides nonce prefix "7c" which is 1 bytes long.
NiceHash prepends additional 1 byte, "b1", prior sending nonce prefix to the miners to match
the expected 2 bytes long nonce prefix.

III. Contact
-----------

www.nicehash.com
info@nicehash.com