As far as I know I only get paid for accepted shares, so what are these stale shares and how can I avoid them?
Stale shares are the shares that were sent after a block was already solved, that is to say, they were sent late and were no longer valid. To avoid stale shares, best lớn have a reasonably fast mining rig (so you won”t take too long to calculate a share, probably not a problem for most machines), reliable mạng internet connection (stable, not necessarily fast), but also an up-to-date mining software (if you are mining with some really old miner it might not communicate in the most efficient manner with the pool).Bạn đang xem: Stale shares là gì
Bạn vẫn xem: Stale shares là gì
In short – update your miner every now và then, make sure your mạng internet is running okay, and don”t mine on really weak rigs.
Bạn đang xem: Stale shares là gì
share Improve this answer Follow answered Oct 7 “11 at 22:28
ThePiachuThePiachu 42.3k2020 gold badges130130 silver badges337337 bronze badges add a phản hồi | 23A stale mô tả occurs when you find a share and submit it khổng lồ the mining pool after the pool has already moved on to the next block. The percentage of stale shares should be very low if everything”s working correct, around 2 out of 1,000 shares or so.
When the long polling notification goes out, all miners that tư vấn long polling request new work units at about the same time. This generates a massive burst of load as the pool has khổng lồ manages lots of network traffic and do several SHA-256 operations for each share it issues. If the pool is slow to lớn issue you a new work unit, the window in which you can generate stale shares increases.
The long polling and subsequent chia sẻ request process requires a few network operations. Latency between the miner và the pool can slow this process down. Picking a pool with a controller near you (network wise) can reduce this part of the stale nói qua window as well.
Xem thêm: Iso Là Gì? Dùng Để Làm Gì? Những Tiêu Chuẩn Iso Phổ Biến Nhất Hiện Nay
I probably shouldn”t admit it, but I was actually responsible for one such bug. My first implementation of long polling in the leveehandbook.net client rushed as quickly as possible to send out the notifications of a new block being discovered khổng lồ miners — so quickly that some miners could request new work units before the client had finished processing the new block and they got work units based on the old block. Any shares they submitted based on those work units would be reported as stale.