In Slush Pool’s 11+ year history as of 2021, luck has been the most frequent topic of questions. If you find yourself confused by the concept of “luck” in mining, you’re not alone. They still just need to run a single hash computation, but it represents more shares the higher the difficulty was in producing it. This is how the pool is able to validate the work of larger miners without linearly scaling the pool’s own work. 1 proof of work) every 2-3 seconds on average, but that 1 hash accounts for 10,000 shares for the larger miner and 100 shares for the smaller one. To illustrate further, suppose that we have a large miner with share difficulty 10,000 and a smaller miner with share difficulty 100.
![cgminer rejected low difficulty share cgminer rejected low difficulty share](https://i.imgur.com/LgGThoG.jpg)
Rather, one hash computation which has an output below the share difficulty target produces many shares. How shares are valuedīefore we move on, something else to understand about shares is that they aren’t produced one at a time. The goal in setting this share target is for miners to be submitting shares about once every 2-3 seconds, providing a good balance between measuring your hashrate accurately and minimizing computational intensity for the pool to verify the work of all its miners. lower target for the hash output value) than a miner with 15 TH/s. For example, a miner with 100 PH/s will have a higher share difficulty (i.e. Since shares only exist to be a practical unit for pools to measure miners’ hashrate, the share difficulty target can be adjusted for each individual miner based on their hashrate. One thing to note is that there is no single share difficulty target for all the miners in a pool. Short-term variance in hashrate measured on the pool, smoothed out in scoring hashrate In this sense, pools and share difficulty targets are like mini versions of the bitcoin network and its network difficulty target. Variance is a part of mining at every scale. The same way that sometimes miners find 2 blocks in a matter of seconds, and other times no blocks for 30+ minutes. Sometimes you’ll “find” shares faster than expected based on your hashrate and share difficulty target, and sometimes slower. This also explains why your pool hashrate fluctuates somewhat even when you have perfect uptime. In other words, public mining pools couldn’t exist without shares, as they wouldn’t have an efficient way of measuring the hashrate of each miner connected to the pool in order to fairly distribute the rewards.
![cgminer rejected low difficulty share cgminer rejected low difficulty share](https://i.imgur.com/7Vp0hyn.png)
To verify the shares, the pool must compute the hash… meaning that, without shares, pools would have to redo ALL the hashes that miners do just to be sure that miners are actually doing the work in the first place. This is why it’s advisable to connect to the nearest pool stratum server to your geographic location.)įrom this description, can you see why shares are so important? (Note: “stale” or “rejected” shares can occur when you submit shares after the block for those shares has already been found, something which typically occurs in the few milliseconds immediately following a block find.
![cgminer rejected low difficulty share cgminer rejected low difficulty share](https://image.slidesharecdn.com/legacy-190126105921/95/brutal-refactoring-lying-code-the-churn-and-other-emotional-stories-from-legacy-land-22-638.jpg)
Getting the same result verifies that the proof of work is valid. To verify the validity of the shares you submitted, the pool simply repeats the same hash computation that you did to produce the shares in the first place. Hash outputs 99: doesn’t meet target, nothing sent to the poolĪnytime your ASICs produce shares, they are sent to the pool to earn mining rewards.U3 is 50G then D = 50 * 2.Share difficulty example: Dice rolls below “99” (share difficulty) can produce shares, while they still have to be below “4” to produce blocks Recommended difficulty is calculated as: D=H*2.3, H is the hashrate, G is unit.Į.g: S9 is 14T then D = 14000 2.3 = 32200, set to d=32200 In command line, it's: cgminer -o stratum+tcp://cn.ss.btc.com:1800 -u USER_NAME -p d=4096. No matter how low the hashrate is, the pool will never assign a difficulty less than 1024. md=1024 means that the miner's minimum difficulty is 1024.
#Cgminer rejected low difficulty share password#
If your miners are extremely high or low, configuring a suitable difficulty will improve the efficiency.ĭifficulty parameters: d=4096 or d=4096,md=1024, Type these parameters into your password bar in the miner background system.ĭ=4096 means that the initial difficulty will be 4096 after its connection.
#Cgminer rejected low difficulty share how to#
How to configure the difficulty of miners?