ASIC compatibility report
Device: Goldshell HS5
Firmware: 2.2.5
Stratum user agent: intminer
Works, and it mined real blocks. The node accepted 205 of 249 blocks this miner found. 247 of 249 shares were accepted.
Outcome
- TCP connections: 71, of which 68 never sent mining.subscribe
- bare connections arrive about every 18.1s
- stratum sessions: 3 (2 offering a session id to resume)
- jobs received: 699 (210 with clean_jobs)
- shares: 249 submitted, 247 accepted
- rejected: 2 x
stale-prevblk - session: 1264s
- blocks: 249 submitted, 205 accepted by the node
- blocks that lost a race: 44
(normal when blocks come quickly: two found at the same height, and only one can be the chain. The node accepted these, they just are not the chain)
Dialect
subscribe : 1 param(s), widths [8]
extranonce1 : 4 bytes
extranonce2_size : 8
submit : 5 params: 14,16,16,16,16 (249x)
difficulty : [64, 4096, 8192, 512]
methods used : mining.authorize, mining.notify, mining.set_difficulty, mining.submit, mining.subscribe
non-standard : none
Submit uses 16-hex ntime and nonce, the Sia 8-byte convention.
Environment
- datum-blake2b image (gateway
39f9c3c82df72736f0ac9417ac388885ce32340e, tooling140b8ccab213)
Notes
Hardware Version 30.40.A5
The HS5 has been running for over 24 hours on the blake2b(SC) algorithm. I have had to restart it multiple times because I was having 100 percent rejection. I had to stop and restart both Knots Blake2B and Datum Blake2B. Then restart the miner after Knots and Datum are running again. After that it mines just fine. I am still monitoring it. I am wondering if the problem is because blocks are being mined very quickly.
Worker names are hashed and passwords dropped at capture time.
Share this in the Bitcoin section of the forum:
Bitcoin - PaulsCode (a free account is needed to post)
or, if you already use GitHub: