Compatibility Report ePIC SC200

Bitcoin
1

ASIC compatibility report

Device: ePIC SC200
Firmware: 4.0.0
Stratum user agent: epic-miner v4.0.0

Works, and blocks were accepted. 29 of 29 shares from this miner were accepted, and the node accepted 123 of 139 blocks. The block figures are for the whole gateway and are larger than this miner’s share count, so something else was mining at the same time and the blocks cannot be credited to this miner.

Outcome

  • TCP connections: 1
  • stratum sessions: 1 (1 offering a session id to resume)
  • jobs received: 79 (27 with clean_jobs)
  • shares: 29 submitted, 29 accepted
  • session: 460855s
  • blocks: 139 submitted, 123 accepted by the node
    (more blocks than shares, which one miner cannot produce: the block count covers every miner on this gateway, not just this one, so another was mining at the same time)
  • blocks the node did not accept: 16
    (normal when blocks come quickly: two found at the same height, and only one can be the chain)

Dialect

subscribe        : 2 param(s), widths [17, 8]
extranonce1      : 4 bytes
extranonce2_size : 8
submit           : 5 params: 27,16,16,16,16   (29x)
difficulty       : [1024, 2048]
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 e0437de68bdb045150327f8ab891df3b42c2538a, tooling d28515094899)

Notes

The web interface to miner has a dropdown for coin type, but only SIA coin is available to pick. This is the newest firmware from manufacturer’s webpage and has a 2022 date.

2

I went looking for the setting to switch to testnet4 and upon not finding, saw I had updates available for both Bitcoin Knots Blake2b and Datum Gateway Blake2b on Umbrel (thanks Paul!). I will first re-run my report, before switching over to testnet4 for more testing.

3

Here is my updated report, after updating my Umbrel node to the newest Bitcoin Knots Blake2b and Datum Gateway Blake2b. This has extra details, added by Paul’s updates.

ASIC compatibility report

Device: ePIC SC200
Firmware: 4.0.0
Stratum user agent: epic-miner v4.0.0

Works, and blocks were accepted. 54 of 57 shares from this miner were accepted, and the node accepted 128 of 144 blocks. The block figures are for the whole gateway and are larger than this miner’s share count, so something else was mining at the same time and the blocks cannot be credited to this miner.

Outcome

  • TCP connections: 2
  • stratum sessions: 2 (2 offering a session id to resume)
  • jobs received: 161 (55 with clean_jobs)
  • shares: 57 submitted, 54 accepted
  • rejected: 3 x stale-prevblk
  • session: 801s
  • blocks: 144 submitted, 128 accepted by the node
    (more blocks than shares, which one miner cannot produce: the block count covers every miner on this gateway, not just this one, so another was mining at the same time)
  • blocks that lost a race: 16
    (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        : 2 param(s), widths [17, 8]
extranonce1      : 4 bytes
extranonce2_size : 8
submit           : 5 params: 27,16,16,16,16   (57x)
difficulty       : [1024, 2048]
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, tooling 140b8ccab213)

Notes

New report, after updating to newest Bitcoin Knots Blake2b and Datum Gateway Blake2b on Umbrel.

Worker names are hashed and passwords dropped at capture time.