Stale shares là gì

When I mine at a pool, only a part of my shares are accepted. There is a small percentage which is marked as stale.

Bạn đang xem: Stale shares là gì

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 bloông xã was already solved, that is lớn say, they were sent late and were no longer valid. To avoid stale shares, best to have a reasonably fast mining rig (so you won"t take too long to lớn calculate a nói qua, probably not a problem for most machines), reliable 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).

In short - update your miner every now & then, make sure your mạng internet is running okay, và don"t mine on really weak rigs.

Improve this answer
answered Oct 7 "11 at 22:28

42.3k20trăng tròn gold badges130130 silver badges337337 bronze badges
Add a bình luận |
A stale giới thiệu occurs when you find a nói qua và submit it to lớn the mining pool after the pool has already moved on lớn the next bloông xã. The percentage of stale shares should be very low if everything"s working correct, around 2 out of 1,000 shares or so.

Several factors affect the stale giới thiệu rate. The three most important are long polling, pool load, & miner-to-pool latency.

Any shares found based on old work units after the pool controller receives a new bloông chồng will be stale. Long polling is a technique that allows the pool khổng lồ notify all of its miners when there"s a change in the blochồng chain so they can immediately request new work units. If your pool or mining software doesn"t support long polling, you will finish out the old work units, generating stale shares.

Xem thêm: #1【 Fct Là Gì Và Một Số Vấn Đề Cơ Bản Liên Quan Tới Fct, Cách Tính Thuế Nhà Thầu Mới Nhất Hiện Nay

When the long polling notification goes out, all miners that support long polling request new work units at about the same time. This generates a massive burst of load as the pool has to manages lots of network traffic và do several SHA-256 operations for each tóm tắt it issues. If the pool is slow khổng lồ issue you a new work unit, the window in which you can generate stale shares increases.

The long polling and subsequent nội dung request process requires a few network operations. Latency between the miner & the pool can slow this process down. Picking a pool with a controller near you (network wise) can reduce this part of the stale giới thiệu window as well.

In addition, some pools have sầu had bugs in their software that produced stale shares. The pool checks if the cốt truyện is stale by seeing if it has a record of the work unit and clearing all work unit records when the chain changes. So if something goes wrong with the work unit tracking process, that will result in a stale share being reported.

For example, if the pool erroneously issues the same work unit khổng lồ two miners, the first one lớn submit the chia sẻ will get credit. The pool will remove sầu the record when the nói qua is found because otherwise you could submit the same mô tả more than once. This will result in you getting a stale nói qua report.

I probably shouldn"t admit it, but I was actually responsible for one such bug. My first implementation of long polling in the client rushed as quickly as possible to skết thúc 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 bloông xã & they got work units based on the old block. Any shares they submitted based on those work units would be reported as stale.