mirror of
https://github.com/skot/ESP-Miner.git
synced 2025-03-17 21:32:52 +01:00
more details
This commit is contained in:
parent
32e3d038d5
commit
e1c0dc542c
@ -1,4 +1,5 @@
|
||||
##BM1397 protocol
|
||||
## BM1397 protocol
|
||||
notes from sniffing BM1397 communication and trying to match it up with cgminer
|
||||
|
||||
It looks like this setting up the BM1397:
|
||||
```
|
||||
@ -37,7 +38,15 @@ How does this big work field break down?
|
||||
`04` -> midstates
|
||||
`00 00 00 00` -> always zero. Is this the starting nonce?
|
||||
`72 E7 07 17` -> nbits
|
||||
`A9 81 51 63` -> ntime
|
||||
`A9 81 51 63` -> ntime. if you flip the endianess, this is unixtimestamp for Thu Oct 20 2022 17:13:13 GMT. boom!
|
||||
`EE D6 E5 43` -> last 4 bytes of the merkle root
|
||||
`35 3F 14 92 56 25 54 19 4E 41 31 08 E5 D7 89 4A C8 13 50 A4 48 05 B8 0E E2 E4 83 95 F8 C1 15 8D` -> midstate computed from the first 64 bytes of the header
|
||||
`EC 07 D8 B8 AE CA DE E6 35 8C 3E E9 1C 57 5D 99 A7 52 95 DC D8 08 7B 7A D` -> ?? another midstate?
|
||||
|
||||
when the BM1397 finds a nonce that makes a hash below the difficulty (which difficulty is that?) it responds with;
|
||||
```
|
||||
AA 55 00 03 EA 0F 02 20 9C
|
||||
```
|
||||
this means the Nonce 0003ea0f was found for JobID 20
|
||||
|
||||
If the BM1397 _doesn't_ find a good nonce in the whole nonce space, it just goes off into lalaland. It's up to the miner to keepm track of what the ASIC is doing and send it more work if this happens. If you look at the hashing frequency you should be able to time this.
|
||||
|
Loading…
x
Reference in New Issue
Block a user