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

[norgan]

Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol

[PatMan]

Hey guys,

Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.

Lets hope we can get it sorted 

[norgan]

Hey guys,

Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.

Lets hope we can get it sorted 

Nice one Patman.

I still find it ironic that we see pool rate drop and blocks fewer but we seem to be getting more traction on code development. I can't help but speculate what that means for p2pool.
Will petamine add their hashing to p2pool effectively pushing us all out due to diff rising or will a change come that no only avoids this but even perhaps takes advantage of it, as in more blocks for miners on p2pool. and the even stranger thing is the number of donations made to p2pool of late.

Funny times we are seeing right now.

[jedimstr]

Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol

Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html

The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.

My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

[-ck]

So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

Higher diff is in no way harmful to slow miners, and if anything is advantageous by limiting wasted share processing (which does not contribute to your income). It's a common misconception that high diff is bad for slow miners - it only increases the variance on those miners on regular pools and on p2pool all shares are pseudoshares unless they're very high diff shares so they have absolutely zero influence on neither your payout nor your variance.

[norgan]

Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol

Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html

The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.

My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

The difference is minimal and it all depends on whether you want consistent diff or variable diff. I'm going to hold off changing my recommendations until I have a bigger sample size.
My worry was that I have a miner in my node 3 times faster than mine and I also have a smaller miner that I use. Always looking for options to optimize those. So far the differences have been pretty small.

[nreal]

I tought there was a bug in p2pool, had my username/3000000 , when i took the 3000000 of it didnt go down to 1200000 that webpage was showing - even node reboot didnt calm it down. It stayed at ~1600000 even with 2 erupters 670mh
Had to put username/1000000 and then it started to follow..

[jonnybravo0311]

Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol

Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html

The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.

My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

The difference is minimal and it all depends on whether you want consistent diff or variable diff. I'm going to hold off changing my recommendations until I have a bigger sample size.
My worry was that I have a miner in my node 3 times faster than mine and I also have a smaller miner that I use. Always looking for options to optimize those. So far the differences have been pretty small.

Read ckolivas' reply.  The slower miners don't choke on anything.  All miners on p2pool, big and small, must submit shares greater than the target share difficulty.  If you happen to have a miner of 1GH/s on a node that has 1TH/s the graphs may not look as nice, and your mining software might not report as many "accepted" shares, but it is completely irrelevant.  The only thing relevant is a share that is high enough difficulty to get you onto the share chain, or possibly crack the BTC block.  All of the rest of them are effectively just noise.  We like to see the pretty graphs and the "accepted" flashing across our screens, but those things are strictly for our own mental gratification.

[windpath]

************URGENT**********
@forrestv - This is your chance to prove to p2pool users that you actually care - I & every user here would like to see some input from you regarding this - please provide any info you can.....

BIG +1, S2's and upcoming S3's are ciritical to our success.


I'd like to start a bounty for forrestv to complete this.

I will start it with a BTC0.50 bounty offered to forrestv for a working solution for p2pool/anitminer S2 & S3 compatibility with the Ants achieving expected hashrate and shares.

Anyone is welcome to contribute to the donation address, bounty is paid to forrestv (or his designee) upon a working, distributed solution or returned in full in 30 days, I will pay return tx fees for any donation over BTC0.001, if your donation is less, consider it donated.

Bounty Address: 1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H

https://blockchain.info/address/1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H

Signed message:

Code:

forrestv p2pool antminer s2 and s3 compatibility fix.

Message signature:

Code:

G7zuvJ7/LPv7LpZveAsQWet1gAR42bnwFRVPB7NsnGqPnWkN8bqSSN1UwR+NnfDs/8LkruqZcVsTTdfcy5pcNj4=

Please contribute.


Edit: Any additional donations (over BTC0.001) will be returned to donation address or paid to Forrest or his designee on or before July 25th, 2014.

My hope is to pay Forrest for work done, lets make the bounty worthwhile.

Donated

7f9e8ad8756685ef911f3cbb2a0c4ae74b3851dbfa0f1b312154fdf689ee6b11

Confirmed BTC0.25

Total bounty currently BTC0.75

[jedimstr]

So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

Higher diff is in no way harmful to slow miners, and if anything is advantageous by limiting wasted share processing (which does not contribute to your income). It's a common misconception that high diff is bad for slow miners - it only increases the variance on those miners on regular pools and on p2pool all shares are pseudoshares unless they're very high diff shares so they have absolutely zero influence on neither your payout nor your variance.

Thanks Con

[IYFTech]

@ PatMan - emailed you some info dude 

[PatMan]

@ PatMan - emailed you some info dude  

Got it my man - good stuff  

EDIT: Everything has been sent to Bitmain - hope to get some news soon......fingers crossed  

Thanks again everyone for your input.

[sconklin321]

Wow!!! 2 blocks in 1 day!!!  I'll take that anyday!!

[norgan]

Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol

Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html

The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.

My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.

After running overnight my conclusion is the settings don't make a huge difference. regardless of diff the shares and payouts looks to be pretty stable and the hash & reject rate is right on where it was before when I had the diff set in the miner Config.

[norgan]

Wow!!! 2 blocks in 1 day!!!  I'll take that anyday!!

haha yeah not bad huh? I got a nice payout from that last one too.

[squashpile]

Norgan.. are you still using modified cgminer with --scan-time 1 --expiry 1?

If so did you notice any difference or how it works on other pools?
I just replied on reddit too, but that was before I saw all the info on this thread about pseudo.

[norgan]

Norgan.. are you still using modified cgminer with --scan-time 1 --expiry 1?

If so did you notice any difference or how it works on other pools?
I just replied on reddit too, but that was before I saw all the info on this thread about pseudo.

yes still using those, that is important for p2pool from what I have discovered and been told. Still not sure what impact that would have on other pools. Can anyone comment on the impact of these settings on other pools?

[sconklin321]

Is there a reason the second block mined today isn't showing up on my node's stats page??

http://mine.njbtcmine.net:9332

[mdude77]

Is there a reason the second block mined today isn't showing up on my node's stats page??

http://mine.njbtcmine.net:9332

Same here.  I was just about to ask that.

I suspect there's an orphan somewhere.  You'd know if the payout suddenly disappeared.

M

[norgan]

I've seen payouts before with the block reporting later. it could just be a delay in the stats?