popov/cpuminer-opt-gpu
1
0
Fork 0
mirror of https://github.com/JayDDee/cpuminer-opt.git synced 2025-09-17 23:44:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Home (markdown)

JayDDee
2020-03-01 17:35:06 -05:00
parent 52b77fc9a8
commit e2c257adea
1 changed files with 61 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

87
Home.md

@@ -127,6 +127,28 @@ Some algorithms may work wallet mining using getwork or GBT, YMMV.
yespower-b2b generic yespower + blake2b
zr5 Ziftr
Many variations of scrypt based algos can be mine by specifying their
parameters:
scryptn2: --algo scrypt --param-n 1048576
cpupower: --algo yespower --param-key "CPUpower: The number of CPU working or available for proof-of-work mining"
power2b: --algo yespower-b2b --param-n 2048 --param-r 32 --param-key "Now I am become Death, the destroyer of worlds"
sugarchain: --algo yespower --param-n 2048 -param-r 32 --param-key "Satoshi Nakamoto 31/Oct/2008 Proof-of-work is essentially one-CPU-one-vote"
yespoweriots: --algo yespower --param-n 2048 --param-key "Iots is committed to the development of IOT"
yespowerlitb: --algo yespower --param-n 2048 --param-r 32 --param-key "LITBpower: The number of LITB working or available for proof-of-work mini"
yespoweric: --algo yespower --param-n 2048 --param-r 32 --param-key "IsotopeC"
yespowerurx: --algo yespower --param-n 2048 --param-r 32 --param-key "UraniumX"
yespowerltncg: --algo yespower --param-n 2048 --param-r 32 --param-key "LTNCGYES"
## Building
### Building on Linux
@@ -457,7 +479,7 @@ will include new estimates for the new block or stratum difficulty.
Using external data the coin can be identifed from its block number.
`
[2020-02-07 23:38:22] New block 1293839, job 1d9f
[2020-02-07 23:38:22] New block 1293839, job 1d9f, ntime 5e5c2e79
lyra2rev3: lyra2v3.mine.zergpool.com:4550
Diff: Net 50648, Stratum 26, Target 0.10156
TTF @ 2758.00 kh/s: block 2y2d, share 2m38s
@@ -489,28 +511,39 @@ Line 4:
Line 5, only displayed in single coin pools
* network hashrate estimate calculated from network difficulty and the number of blocks found during
the session.
* network hashrate estimate is calculated from network difficulty and the number of blocks found during
the mining session.
* observed network block TTF calculated from the number of blocks found during the session.
### Getwork new block report
`
[2020-02-28 10:54:02] New block 6273226, diff 118.48, ntime 5e5c2e79
Miner TTF @ 3938.69 kh/s 6m11s, net TTF @ 68.24 Mh/s 2h04m
`
The getwork new block report is similar to the stratum version escept getwork has no stratum difficulty,
no job id, and no share related estimates. All present fields have the same meaning as the stratum log.
Unlike t stratum version the network hashrate is provided by the wallet and the block TTF is calculated
by the miner.
### Share submitted report
`
[2020-02-07 23:59:03] 5 submitted by thread 15, lane 1, job 1dd6
[2020-03-01 16:52:18] 168 Submit diff 2.4496e-07, block 440815, job 3f4a
`
The main purpose of the share submitted report is to timestamp the event to measure latency.
* submit count is a simple counter that is incremented every time a share is submitted. It should always
match up with a share result counter.
* CPU thread that submitted the share, FYI Only.
* The difficulty of the submitted share.
* Lane of the CPU thread that submitted the share, only displayed when hashing multiple data streams in
parallel (N way). FYI only.
* The current block.
* The job id, stratum only, useful to troubleshoot stale shares.
* job id is displayed to help diagnose stale shares caused by latency.
### Share result report
@@ -518,10 +551,9 @@ This report is generated when the pool's reply has been received acknowledging t
`
[2020-02-07 23:59:03] 5 Accepted 5 S0 R0 B0, 400.092 sec (159ms)
Diff 0.11393 (0.0853%), Block 1044635, Job 1dd6
Diff 0.11393 (0.0853), Block 1044635, Job 1dd6
`
Line 1:
* Share result count, simple counter independant of submit counter but they should match. a mismatch indicates
@@ -545,24 +577,24 @@ Line 2:
difficulty it is higher than or equal to the target difficulty all shares are considered equal by the
pool server based on the stratum difficulty.
* (share ratio %) the percentage of the difficulty required to find a block, 100% or greater solves a block.
Also FYI only.
* (share ratio) the fraction of the difficulty required to find a block, 1.0 or greater solves a block.
Mostly FYI.
* The current block height (block number), coloured magenta when the block is found by the miner.
* The id of the job associated with the acknowleged share coloured yellow if the job was stale. This is obtained
from data collected at submit time and deoends on proper synchronization (submit count == reply count) for
correctness.
* Stratum only, the id of the job associated with the acknowleged share, coloured yellow if the job was stale.
This is obtained from data collected at submit time.
### Periodic summary report
`
[2020-02-18 23:50:16] Periodic Report 5m35s 5m35s
Share rate 0.36/min 0.36/min
Hash rate 1600.25kh/s 1602.60kh/s (1654.96kh/s)
Submitted 2 2
Accepted 2 2
[2020-03-01 16:49:10] scrypt: scryptn2.mine.zergpool.com:3435
Periodic Report 3m45s 14m58s
Share rate 9.84/min 9.68/min
Hash rate 27.03h/s 29.17h/s (22.83h/s)
Submitted 37 145
Accepted 37 145
`
Generated aproximately every 5 minutes. The timing is not precise because it is an opportunistic report.
@@ -570,13 +602,16 @@ It is produced when it is convenient in order to miminize the impact on mining.
The report contains data for the 5 minute interval in the left column, and session statistics in the right.
* Line 1: Sample time for current period and session
Actual interval usually between 5 & 6 minutes.
* Line 1: (blue) the current algorithm and URL
* Line 2: Number of shares submitted per minute.
Determines effective hash rate, also used by the pool to report hash rate.
* Line 2: Sample time for current period and session Actual interval usually between 5 & 6 minutes.
* Line 2: Number of shares submitted per minute. Determines effective hash rate, the same way pool's
calculate hash rate.
* Line 3: Effective hash rate calculated from share rate and stratum difficulty. Should closely follow the
pool's reported hash rate.
* Line 3: Effective hash rate calculated from share rate and stratum difficulty.
Effective hash rate discounts rejected shares which are reported as lost hash rate.
The effective hash rate is the real performance of the miner once luck is factored in. It is also most