Forum Rules can be found here
Hi folks,TLDR - if you are a small miner below 3MH/s you probably want to switch to a normal pool.If you are a "big" p2pool miner with ~2MH/s or more you probably don't need to concern yourself with this. Otherwise small p2pool miners need to read this important message. As you can see from the official fundraising thread, I am the lead developer on Litecoin-0.8.2. I am also a p2pool developer. Two months ago I fixed a serious problem in p2pool's scrypt stratum that was previously causing p2pool LTC to lose some work. So it suffices to say I know a lot about Litecoin and p2pool.Problem with p2pool for small LTC Minershttp://ltc.block-explorer.com/block/f969ae9e8e5eaf5563c0a07ca3fc5d7ea3b49192179136e2b9793a58836e157bHere is a typical p2pool LTC block where there are often 500-600 payouts. This is fine for the bigger miners who receive like 0.1 LTC per block, but it becomes increasingly problematic for the smaller miners as payout amounts per block become tinier and tinier. As many of you know, spending the tiny p2pool dust can be very expensive in fees, or annoyingly time consuming if you use the free tx combining method.Bigger chunks, paid less frequently?I talked with forrestv about this dust issue, as the quantity of dust and the increasing difficulty of spending it is growing far worse. We agreed in principle today that future versions of p2pool must enforce a minimum dust payout size. What this means is if you are a small hashrate miner, you will have less frequent payouts in larger sized chunks. This can be good for you, as larger chunks are easier to spend with lower fees. This can also be bad because it will seem frustrating to have many hours of zero payouts and other hours of large chunks. Even if you logically know the expected payout is the same, humans typically don't psychologically deal with variance all that well.So what are your recommended options today?Option 1: Increase your minimum share difficulty.Currently p2pool's variable share difficulty is floating around 1.47. If you multiply that by 2^16 you get 96337.92, the equivalent share difficulty that you see in cgminer. If you hit that share, you collect ~0.01 LTC per block for a few hours. Small miners will frequently get annoyingly small dust in tiny increments like 0.01-0.05 which are expensive and inconvenient to deal with.If you edit your miner config to append /<number> to the end of your miner username, you can force the required share difficulty to be higher. If you set it to /2, then 2*2^16 = 131072 is the share difficulty. This means you will get shares less frequently, but when you do have shares, subsequent payouts will be in larger chunks. /4 would mean shares half as often as /2, with double the minimum size chunks. The /<number> can be a maximum of 10 times the floating share difficulty, so if 1.47 is the current floating share difficulty, the highest you can set it is /14.7.The trouble is ... if you are a small miner, you probably need something like /6 or higher to have minimum dust sizes that approaches the level where they are easier to spend. If you use a mining calculator plugging in your hash rate of 427KH/s and a difficulty of 6, it might tell you an expected average of 16 hours to find a share of difficulty 6. But that is only an average. In reality shares will happen within a bell curve of probability centered at 16 hours. You might have two days with no shares. You might have lucky days with three shares. These are all normal and expected, and quite frustrating.A future version of p2pool will enforce higher share difficulty and/or less frequent payouts for small miners, basically making this recommendation automatic. But you can see from the above that very high variance is scary in general to small miners.Option 2: Switch to a Normal PoolAs most humans don't understand probability and cannot psychologically handle extreme variance, most small miners are better off using traditional pools.Unfortunately, the cost to the network of hundreds of dust payouts and the cost to miners in high fees makes p2pool a very bad option for small miners. It hurts me to admit this, as decentralized trustless mining with p2pool is supposed to be good for the security of the network. Fortunately, today's Litecoin mining pools are spread out with no pool exceeding 20% of the total network hash rate. Leading pools like give-me-ltc.com or wemineltc.com have committed to discouraging more miners if they are in danger of approaching 50%.So it is my recommendation that most smaller miners use the traditional pools. It is better for the network as long as those pools don't grow too large.
Small miners are strongly advised to either accept extremely high variance (infrequent but large chunks of coins) or just switch to a traditional pool.
forrestv decided on the following details for the next hardfork version of p2pool LTC:20 second interval instead of 10 seconds. This will allow the p2pool network to be more competitive against traditional pools because currently people decrease Intensity due to fear of DOA. Miners will be able to use higher intensity and the pool as a whole would have more hashrate with the same hardware. 20 seconds also reduces the frequency of orphaned shares which are also hated by p2pool miners.Payouts will be averaged across two blocks instead of the current 12 blocks. This means valid shares will be at least six times larger in payout size, but you will have fewer payouts. Larger and fewer payouts is healthier for the network and better for miners because they have lower fees to spend the dust.Dynamic minimum share difficulty to enforce minimum dust size of 0.05 LTC. This means if you don't already have a current share, p2pool will increase the minimum difficulty for your first share to ensure that you will never get painfully small dust.All of this makes p2pool healthier for the network and less costly for miners. Small miners are strongly advised to either accept extremely high variance (infrequent but large chunks of coins) or just switch to a traditional pool.forrestv will need veteran p2pool testers soon to test the new code. Please watch this thread.
I started on my node litecoind 0.6.4rc1 with p2pool patched 'litecoindust', welcomme testers!
Quote from: General-Beck on June 18, 2013, 06:49:01 PMI started on my node litecoind 0.6.4rc1 with p2pool patched 'litecoindust', welcomme testers!NOOOO!! DO NOT RUN THAT! That is unfinished code from weeks ago.
Page created in 0.131 seconds with 27 queries.