Updated Console Logs (markdown)

JayDDee
2020-05-20 12:57:01 -04:00
parent 475b72b0e2
commit af8f921f80

@@ -142,19 +142,26 @@ Line 4, only displayed in single coin pools
* network hashrate estimate is calculated from network difficulty and the number of blocks found during
the mining session.
### Getwork new block, work report
### GBT/Getwork new block, work report
`[2020-02-28 10:54:02] New block 6273226, diff 118.48, ntime 5e5c2e79`
`[2020-02-28 10:54:02] New block 6273226, Net Diff 118.48, Ntime 5e5c2e79`
` Miner TTF @ 3938.69 kh/s 6m11s, net TTF @ 68.24 Mh/s 2h04m`
` Miner TTF @ 3938.69 kh/s 2h04m, Net TTF @ 68.24 Mh/s 6m11s`
The getwork new block report is similar to the stratum new block log with a few differences. There is no
stratum difficulty and no job id. "New job" is replaced with "New work". All present fields have the same
meaning as the stratum log but some are calculated differently. New work is detected by a change of the ntime field of the block header data. Unlike the stratum version the network hashrate is provided by the wallet
and is not an estimate. The block TTF is calculated from network hashrate and network difficulty and is
therefore considered correct.
The GBT or getwork new block report is similar to the stratum new block log with a few differences. There is no
stratum difficulty and no job id. "New job" is replaced with "New work". New work is detected by a change of
the ntime field of the block header data.
All present fields have the same meaning as the stratum log but some are calculated differently. Unlike the
stratum version the network hashrate is not an estimate. It is accurate as it is provided by the server using
the getmininginfo method.
There is no target diff and no share TTF. The block TTF is displayed for the miner and network based on the
network difficulty and miner's reference hash rate and the network hash rate, respectively. It is considered
statistically accurate.
## Share submitted report