Whoever the anonymous donor is, thanks for stepping up!  Seeing the S3 binaries updated from their current 4.6.1 version will be nice .

You constantly hear negative press about how company X screwed over everyone, so seeing that someone put up 10BTC to fund development work is extremely refreshing.  Thanks again to whoever donated the coin to kano!!!

No clue... I'm seeing the same thing.  All predicted payouts are off.  Look at the top 2 miners... their combined expected payout is over 34BTC.

ssh into your S5
cd /usr/bin
mv cgminer cgminer.old
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
Reboot

You might want to change the AntPool from P2P to Single Coin.  AntPool is by no stretch of the imagination p2pool.

Also, when I wrote my review of NastyPool, the formatting is quite strange.  I'm not sure if it's intentional, or because I put links into the review text, but the result is rather odd.  Check out the screenshot to see what I mean:



Clicking on the green text opens up a popup:



To actually see the review, I've got to click the very tiny little "View" link at the bottom.

By the way, can you incorporate Edit functionality to the reviews?

I created an account on BlockGen and wrote a 5 star review of NastyPool.  The formatting ended up a bit strange, so to see the entire review, you've got to go here: http://blockgen.net/review/56

Setting the queue to 0 means the miner doesn't have a whole bunch of stale work to complete when p2pool tells it to start fresh.  You are not speeding up p2pool, you are having your miner work on relevant data in a timely fashion.  By default, the Ants set the queue to some absurdly high numbers.  The release of cgminer by ck sets it to 1 by default.

I'm not sure why your hash rate would drop by 90%, but the queue setting is not the cause.

Um... you do realize that Android is Java, right?

If you're going to solo mine, just point the miners to solo.ckpool.org.  Not really worth trying to solo mine directly to the coin daemon, so there's really no need for the --btc-address parameter.  If you really want to do it yourself, then you'd be better off setting up your own instance of ckpool; however, unless you're well connected you run a high risk of submitting an orphaned block, and seeing that 25BTC go down the drain would really suck.

I swear I read from ck/kano that the Bitmaintech fork of cgminer tossed stale work... and that was one of the reasons to use the binary from them instead of Bitmain's.

For BTC pools: Discus Fish (i.e. f2pool) and AntPool should probably be added since they represent the top 2 pools by hash rate.

Do you just not understand?  You WILL NOT EVER earn 0.0042BTC per day at current difficulty from a PPS pool charging you a 4% fee.  Period.

Why are you so stressed out and obsessed with that 0.004 value?  GET OVER IT!

trendax and OgNasty, it's my pleasure.  I'm a big proponent of p2pool mining.  I've been running my own node for over a year, and have spent many hours helping others in the p2pool threads.  OgNasty and nonnakip are the only ones who have actually stepped up and done something to address the shortcomings experienced in your typical p2pool setup.  Small miners now have a chance to contribute to the decentralized nature of p2pool without suffering the terrible variance mining on a standard node provides.

And with that, let's take a look at the numbers from this past week:

4/17 - 4/24
NastyPoP - 0.05554895BTC
NastyP2P - 0.05281205BTC
Expected - 0.0321BTC
Luck - 165.47%

P2Pool was considerably luckier this week than it was the week prior and both my S3s performed better than expected.  The edge went to NastyPoP this week, but just barely.  Again, you can see the inherent variance in standard p2pool mining as my block payouts ranged from 0.01BTC down to 0.001BTC, since my S3 decided to go on a share finding strike .

OP updated

What is your native language, ToQcHista?  Many people have very clearly given you answers to your questions, myself included, in many threads.  Perhaps you should be asking your questions in whatever language it is you do understand, because it appears we're having a communications barrier.

As for the answer to your latest question, the screenshot provides the answer, so I'm not sure what more you need.  You changed your BTC payout address.  You must now wait 3 days.  Pretty clear, don't you think?

Also, unless you're planning to compile and build the latest bleeding edge, you'll want to get the code from the latest release branch instead of from the main: https://github.com/bitcoin/bitcoin/releases/tag/v0.10.0.  If you want to help test the latest release candidate: https://github.com/bitcoin/bitcoin/releases/tag/v0.10.1rc3

It won't have any effect on the installation.  It will, however, have plenty of effect on the operation.  As kano points out, you cannot mine until all of the coin daemons are fully synched to their respective blockchains.  Depending on your hardware and your bandwidth, this process could take quite some time (days).

The queue setting is the one that will make the difference.  The others won't help you.  Also, you should use --submit-stale since by default the cgminer binaries in the Ants all throw away stale work, which is a very bad thing for p2pool.

I'm not sure if kano/ck have built a cgminer binary for the S5... if they have, then I'd suggest using theirs.

Zero transaction blocks (well, technically they're reported as 1 transaction because of the block reward distribution) have zero transaction fees.  How could they have any fees since there are no transactions in the block?  In a block that actually does have transactions - like that last one p2pool found 353366 - there were 0.02990026BTC of fees.  Those fees are combined with the 25BTC block reward and distributed to all miners according to the shares the miners have on the payout list.

The transactions are inserted into the block by the node on which you're mining.  Each node runs its own copy of the Bitcoin Core.  If a node has setup their configuration to do something like setting a max block size of 10kb, or their mintxfee to something like 100BTC, then if they happen to find a share that satisfies the network difficulty the chances are exceptionally good the block will contain no transactions other than the block reward.

Like I said, ask this question in the AntPool thread.  They can answer what those values represent.

By the way, on p2pool in the past 24 hours, my S3 earned 0.00910886BTC.  Why?  Luck.  P2Pool found more than the expected number of blocks.  There are also plenty of times on p2pool where that S3 earned 0BTC in 24 hours.  It's the way things work.  If you look at my thread here you can see that my S3 mining on p2pool from 12/26/2014 - 4/17/2015 has earned 0.50613334BTC.  Expected earnings (i.e. what a mining calculator tells you that you should have made) for that same time is 0.5553BTC.  This means during that time I've earned about 91% of what a mining calculator told me I should expect to earn.

Take a look at this post in particular in my thread: https://bitcointalk.org/index.php?topic=891298.msg10095504#msg10095504.  That one clearly shows how 2 identical miners can perform very differently.

Who cares?  The shares are completely irrelevant until one of them exceeds the target network difficulty.  To answer your question, yes, the pool does save your best share.  For example, we lost power at my house a few nights ago.  My rPi didn't automatically restart cgminer (yeah, I should probably fix that), so my 5 U2s are not currently mining.  Yet, here is what is shown from ckpool:

Crazy school girl wielding a large bloody knife.  Yup, I'm pretty sure she's well acquainted with making sacrifices

You'd do better asking this question in the AntPool thread.  I don't know if that shows what your expected 24 hour earnings are, or what you've earned in the previous 24 hours.