[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 254.

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

I have seen some very strange activity on my node the past 36 hours.

I have 1 s1 and 2 s2 mining on my node. And the max rate i can get any miner to mine at is .000240 btc and thats way low what i have seen over the past for a s2. I would usually average .025 to .03 btc hash rate.

The s1 at that slower hash rate makes since to me. But not on the S2. This is driving me crazy why it is this way. My equipment is running 2 quad core xeon processors SSD drive and on a 100 meg fiber circuit in my office. The latency for blockchain.info site is 7ms. So there defiantly not a bandwidth issue.

Any recommendations would surly be appreciated. Angry

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: icio on December 06, 2014, 02:32:46 PM

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody

It has been a rough few weeks variance/luck wise.

The one thing I know about luck is that it is bound to change Wink

I have not messed with my queue settings, but I doubt that doing so would produce this bad luck.

The reported hash rate at the pool would have to be affected and I would imagine a miner tweaking their settings would be paying attention to that.

icio

sr. member

Activity: 894

Merit: 378

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody

idonothave

full member

Activity: 238

Merit: 100

Quote from: PatMan on December 06, 2014, 06:07:09 AM

Quote from: idonothave on December 06, 2014, 05:52:07 AM

Quote from: PatMan on December 06, 2014, 05:27:13 AM

Quote from: jonnybravo0311 on December 05, 2014, 07:24:00 PM

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

ok, thank You, I will try it

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: idonothave on December 06, 2014, 05:52:07 AM

Quote from: PatMan on December 06, 2014, 05:27:13 AM

Quote from: jonnybravo0311 on December 05, 2014, 07:24:00 PM

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

idonothave

full member

Activity: 238

Merit: 100

Quote from: PatMan on December 06, 2014, 05:27:13 AM

Quote from: jonnybravo0311 on December 05, 2014, 07:24:00 PM

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

idonothave

full member

Activity: 238

Merit: 100

Quote from: jonnybravo0311 on December 05, 2014, 07:24:00 PM

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

anyway I let only BTC address as workername, it seems it is working well
node uptime 22 hours, hp 4.78THs, 8 shares 2 orphan, peers 5 in 7 out, doa 1.41 (1-3), getblc latency 0.152, I did some changes during the period so efficiency can be not accurate
after some time if see it is ok I will probably add namecoin merged mining
why global DOA is so high?

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: jonnybravo0311 on December 05, 2014, 07:24:00 PM

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: idonothave on December 05, 2014, 05:18:43 PM

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants. If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

idonothave

full member

Activity: 238

Merit: 100

Quote from: IYFTech on December 05, 2014, 05:10:52 AM

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: jonnybravo0311 on December 05, 2014, 04:05:34 PM

Quote from: windpath on December 04, 2014, 04:45:59 PM

...

Hey windpath,

While I don't often use your node to mine (since I run my own node locally and also on a nearby VPS for when I travel), I do indeed use your services to do things like see payout history, compare my miners' actual hash rate to what p2pool thinks they have, etc. I know you've done a lot of work and I've personally found great value in the services you've provided. So, I thought I would be the first one to send you a tip/donation.

Thanks for all the work you've done.

Thanks buddy I appreciate it!

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: windpath on December 04, 2014, 04:45:59 PM

Just an update folks...

For those of you that had supported CoinCadence's p2pool node by placing an ad or visiting an advertiser, thanks!

While the ads were bringing in a trickle of revenue, they are just not worth it for me to keep running (and I can't stand looking at banner ads either Wink

), soo...

Since bitcoin can bring so much to the table we thought we would try integrating with bitcoin micro-payment services (ChangeTip and CoinBase to start) and see how things go.

If you use the CoinCadence p2pool node, and like what you see consider sending a tip, if there is a feature your dying for send the suggestion with with a bigger tip Grin

...

Also, today we released a new Bitcoin Transaction Volume section on CoinCadence.com, it is in response to the great feedback we got on Reddit about some data mining I did on the blockchain.

You can see the post here:
TIL: Where the Bitcoins at… Mysteries of the Blockchain

The first iteration on the site only contains transaction volume data, more to come...

Cheers!

Hey windpath,

While I don't often use your node to mine (since I run my own node locally and also on a nearby VPS for when I travel), I do indeed use your services to do things like see payout history, compare my miners' actual hash rate to what p2pool thinks they have, etc. I know you've done a lot of work and I've personally found great value in the services you've provided. So, I thought I would be the first one to send you a tip/donation.

Thanks for all the work you've done.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: Prelude on December 05, 2014, 10:09:33 AM

Quote from: jonnybravo0311 on December 03, 2014, 06:29:57 PM

Quote from: jcumins on December 03, 2014, 06:22:48 PM

Ok I am wondering how does one determine what miner or if there pool found the block.

I have not figured that out yet.

2 ways...

First is to look at your logs and you'll see the message that the block was found.

Code:

2014-04-26 04:18:51.302213 GOT BLOCK FROM MINER! Passing to bitcoind!

Second is to look at your payout. If you found the block you get a 0.125BTC reward for it.

The reward for the block finder is 0.5%? I could've sworn I had read 5%. 0.5% does make more sense, though.

Yup, you can verify it by looking at the code, too. 1/200 is given to address that finds the block, 99/200 is given to everyone else. From data.py:

Code:

amounts = dict((script, share_data['subsidy']*(199*weight)//(200*total_weight)) for script, weight in weights.iteritems()) # 99.5% goes according to weights prior to this share
this_script = bitcoin_data.pubkey_hash_to_script2(share_data['pubkey_hash'])
amounts[this_script] = amounts.get(this_script, 0) + share_data['subsidy']//200 # 0.5% goes to block finder

chinesebob

newbie

Activity: 64

Merit: 0

Quote from: IYFTech on December 05, 2014, 05:10:16 AM

Quote from: chinesebob on December 04, 2014, 11:09:10 PM

Quote from: IYFTech on December 01, 2014, 08:28:40 PM

Quote from: norgan on December 01, 2014, 08:27:36 PM

Quote from: -ck on December 01, 2014, 08:25:06 PM

Quote from: IYFTech on December 01, 2014, 08:23:26 PM

Might be worth while asking ckolivas if the S3 binary he done to fix the stale shares filtering can also be used in the C1? I don't have a C1, but it might be compatible......

If S3 binaries run on the C1, my binary is compatible.

Are the S3 binaries still needed with the latest firmware? I'm getting ~4% rejected and ~1.5% stale on my S3's with p2pool

Yes, I use it with the latest firmware:

http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer

Are there any other differences with this binary and the one bundled with the S3 firmware?
Any chance the S3 update from 20141126 has this update?
Is there a way I can check to see if it has the fix or not?

According to their support site, the only difference is: "Modify the previous version cannot restore factory Settings bug." I have no need to restore factory settings at present, so I won't install it Wink

You can & should still use ckolivas's cgminer S3 binary with any/all firmware releases to ensure optimal efficiency with p2pool, until they can be bothered to fix the problem. You can also send ckolivas a donation as a thank you for his fixing Bitmains laziness..... Wink

Thanks, what I meant to ask is, are then any differences in the ckolivas cgminer binary compared to the bitmain provided binary other than the previously mentioned stale share fix. I think you won't think you have a need to factory reset until you have a need to factory reset. I have put them all back on the October firmware, and installed the ckolivas cgminer, all are back and running fine now, and I think you're right, a donation is in order!

Prelude

legendary

Activity: 1596

Merit: 1000

Quote from: jonnybravo0311 on December 03, 2014, 06:29:57 PM

Quote from: jcumins on December 03, 2014, 06:22:48 PM

Ok I am wondering how does one determine what miner or if there pool found the block.

I have not figured that out yet.

2 ways...

First is to look at your logs and you'll see the message that the block was found.

Code:

2014-04-26 04:18:51.302213 GOT BLOCK FROM MINER! Passing to bitcoind!

Second is to look at your payout. If you found the block you get a 0.125BTC reward for it.

The reward for the block finder is 0.5%? I could've sworn I had read 5%. 0.5% does make more sense, though.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: idonothave on December 05, 2014, 01:15:19 AM

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc...... Wink

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: chinesebob on December 04, 2014, 11:09:10 PM

Quote from: IYFTech on December 01, 2014, 08:28:40 PM

Quote from: norgan on December 01, 2014, 08:27:36 PM

Quote from: -ck on December 01, 2014, 08:25:06 PM

Quote from: IYFTech on December 01, 2014, 08:23:26 PM

Might be worth while asking ckolivas if the S3 binary he done to fix the stale shares filtering can also be used in the C1? I don't have a C1, but it might be compatible......

If S3 binaries run on the C1, my binary is compatible.

Are the S3 binaries still needed with the latest firmware? I'm getting ~4% rejected and ~1.5% stale on my S3's with p2pool

Yes, I use it with the latest firmware:

http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer

Are there any other differences with this binary and the one bundled with the S3 firmware?
Any chance the S3 update from 20141126 has this update?
Is there a way I can check to see if it has the fix or not?

According to their support site, the only difference is: "Modify the previous version cannot restore factory Settings bug." I have no need to restore factory settings at present, so I won't install it Wink

You can & should still use ckolivas's cgminer S3 binary with any/all firmware releases to ensure optimal efficiency with p2pool, until they can be bothered to fix the problem. You can also send ckolivas a donation as a thank you for his fixing Bitmains laziness..... Wink

chinesebob

newbie

Activity: 64

Merit: 0

The GHS on my S3s went down to the double digits after loading the recent firmware update from Bitmain. I have no idea if it's only an issue when running on p2pool or if it's across the board, I don't have any other kind of pools configured. In any case I'd recommend some caution if you're looking at the 20141126 firmware.

idonothave

full member

Activity: 238

Merit: 100

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

chinesebob

newbie

Activity: 64

Merit: 0

Quote from: IYFTech on December 01, 2014, 08:28:40 PM

Quote from: norgan on December 01, 2014, 08:27:36 PM

Quote from: -ck on December 01, 2014, 08:25:06 PM

Quote from: IYFTech on December 01, 2014, 08:23:26 PM

Might be worth while asking ckolivas if the S3 binary he done to fix the stale shares filtering can also be used in the C1? I don't have a C1, but it might be compatible......

If S3 binaries run on the C1, my binary is compatible.

Are the S3 binaries still needed with the latest firmware? I'm getting ~4% rejected and ~1.5% stale on my S3's with p2pool

Yes, I use it with the latest firmware:

http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer

Are there any other differences with this binary and the one bundled with the S3 firmware?
Any chance the S3 update from 20141126 has this update?
Is there a way I can check to see if it has the fix or not?

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 254. (Read 2591928 times)