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

[norgan]

Bitmain announce their new p2pool software......check it out:

https://bitcointalk.org/index.php?topic=855548.new#new

yeah very interesting!

[1713468756]

1713468756

[1713468756]

1713468756

[jonnybravo0311]

Bitmain announce their new p2pool software......check it out:

https://bitcointalk.org/index.php?topic=855548.new#new

yeah very interesting!

I've read through the tidbits Bitmain has provided in their announcement.  I just don't see it.  What they've done:

• Kept it in Python - guess it was easier than re-writing in C
• Provided a vardiff - um... that was done a long time ago
• Somehow solved the frequent restarts - yeah... sure.  That's code magic I'd like to see.
• Addressing the "small miner variance" - I posited on how they accomplished that in the announcement thread

[PatMan]

I don't think they've fully grasped the whole p2pool idea from what I've read so far from Bitmain - but I'm sure it'll all come out when they upload it to git - if they ever do. It will either make them or break them I think.

Oh, bought the SP20's by the way.....nice 

[raskul]

I don't think they've fully grasped the whole p2pool idea from what I've read so far from Bitmain - but I'm sure it'll all come out when they upload it to git - if they ever do. It will either make them or break them I think.

Oh, bought the SP20's by the way.....nice 

i've never had any problems with any of the SP-Tech rigs, they mine on ANY mining method with 0 rejected shares and perform particularly well with p2pool and DGM. I alternate my hash between p2pool and DGM, for variance.
Can't wait for my SP20 to arrive next week

[jonnybravo0311]

I don't think they've fully grasped the whole p2pool idea from what I've read so far from Bitmain - but I'm sure it'll all come out when they upload it to git - if they ever do. It will either make them or break them I think.

Oh, bought the SP20's by the way.....nice 

i've never had any problems with any of the SP-Tech rigs, they mine on ANY mining method with 0 rejected shares and perform particularly well with p2pool and DGM. I alternate my hash between p2pool and DGM, for variance.
Can't wait for my SP20 to arrive next week

Jealous of you both.  I've got 9 S3s running here and haven't been able to justify replacing them with SP20s.  I WANT to do it because I love the SP-Tech gear, from the build quality of the units to the stability and rock-solid performance.  But the S3s have already paid for themselves and are mining pure profit at this point.  Makes it hard to pull the trigger.

[raskul]

I don't think they've fully grasped the whole p2pool idea from what I've read so far from Bitmain - but I'm sure it'll all come out when they upload it to git - if they ever do. It will either make them or break them I think.

Oh, bought the SP20's by the way.....nice 

i've never had any problems with any of the SP-Tech rigs, they mine on ANY mining method with 0 rejected shares and perform particularly well with p2pool and DGM. I alternate my hash between p2pool and DGM, for variance.
Can't wait for my SP20 to arrive next week

Jealous of you both.  I've got 9 S3s running here and haven't been able to justify replacing them with SP20s.  I WANT to do it because I love the SP-Tech gear, from the build quality of the units to the stability and rock-solid performance.  But the S3s have already paid for themselves and are mining pure profit at this point.  Makes it hard to pull the trigger.

i should have also said, i'm happy with my S3's and had pondered using their PSU for the SP20 and selling them on.. in the end I just bought a new PSU, so i'll keep the S3's running, they are like the baby pet of the family and the spondoolies gear; the top dog! 

[PatMan]

I still have a few S3's running myself, but got rid of my S2's to subsidise the SP20 purchases. I felt very let down by Bitmains lack of support for the S2 owners - not only because they left it so late to honour their promise of p2pool compatible firmware, but also the about-turn of the upgrade option, the S4 coupon was a bit of a slap in the face too. (I couldn't even give that away!)

The BTC price hike was perfect timing too, I ended up paying less than BTC2 per unit shipped - so I'm a happy chappy    Just gotta wait for them now......

[raskul]

I still have a few S3's running myself, but got rid of my S2's to subsidise the SP20 purchases. I felt very let down by Bitmains lack of support for the S2 owners - not only because they left it so late to honour their promise of p2pool compatible firmware, but also the about-turn of the upgrade option, the S4 coupon was a bit of a slap in the face too. (I couldn't even give that away!)

The BTC price hike was perfect timing too, I ended up paying less than BTC2 per unit shipped - so I'm a happy chappy    Just gotta wait for them now......

i'm the cautious type. as a rule i've never bought batch 1 of any miner. I lost out bigtime because of this with the kfc jupiter as, when I came around to buying batch 2, they were sold out and i never did get a jup but I think i've probably saved myself from more headaches by being cautious this way. then again, it's not a foolproof way of deciding what to buy. I paid for b3 h*shf*st, but that's been my only real loss.

I have to say though, bitmain rigs, for me have been slightly hit and miss, not on the hardware side but on the pool side, they don't seem to be very good with DGM pools, which is my preferred method of mining, and for variance, I also mine p2pool, and also support for p2pool has come late from bitmain.

here's what I get mining DGM with bitmain miners... If i switch all my S3 over to the pool at once, it just falls over with 100% rejects. I have to ramp in one miner at a time and wait until it's stable and showing full hashrate at pool before I can ramp in the next. I also find that if I point too many (6 or more separate miners), the whole lot will begin to give lots of rejects (over 1/3rd).

Now, I know this is most likely caused due to pool stability + hardware compatibility with DGM but I have no problems with other h/w brands.

i mine on mmpool DGM pool (*reminisces of bitparking days!*) and i've never been able to point my full 20TH/s all at once, as the bitmaintech just falls over - funnily enough, never any rejects from my sp-tech rigs. I know that Meni R had input into the design of SP-t manufacturing, so perhaps Bitmain could consult with him for future equipment, to ensure their h/w is good on DGM pools?

just a thought.

[bicer]

...
Maybe this will help https://bitcointalk.org/index.php?topic=766190.0

He runs one of the relay nodes

My bad 

[norgan]

...
Maybe this will help https://bitcointalk.org/index.php?topic=766190.0

He runs one of the relay nodes

My bad 

Yeah it has stabilized quite a bit now with >98% efficiency.

[jedimstr]

The latest block that paid out 330410 isn't showing on my node's list.  Usually this type of thing is due to a block that was orphaned in p2pool but valid on the Bitcoin network.

The difference for this one is that Coincadence (http://minefast.coincadence.com/p2pool-stats.php) usually shows when this happens on the right most column, but for 330410, it's listed as valid(green checkmark). I double checked other people's nodes and none of them show this block.  

So not to look a gift horse in the mouth but... Anyone have any ideas why this one wouldn't show? Is it actually orphaned on p2pool's network even though Coincadence shows it's not?

[MissouriMiner]

The latest block that paid out 330410 isn't showing on my node's list.  Usually this type of thing is due to a block that was orphaned in p2pool but valid on the Bitcoin network.

The difference for this one is that Coincadence (http://minefast.coincadence.com/p2pool-stats.php) usually shows when this happens on the right most column, but for 330410, it's listed as valid(green checkmark). I double checked other people's nodes and none of them show this block.  

So not to look a gift horse in the mouth but... Anyone have any ideas why this one wouldn't show? Is it actually orphaned on p2pool's network even though Coincadence shows it's not?

I see the block in my log file, but not in the UI.  I agree this is odd.

2014-11-17 05:07:35.767992 GOT BLOCK FROM PEER! Passing to bitcoind! 7b853c9b bitcoin: https://blockchain.info/block/00000000000000001747b51ad4fc5590668ac17752bf6aa14cac12637b853c9b

[IYFTech]

Payment shows up on my wallet UI, no problem.

[MissouriMiner]

Payment shows up on my wallet UI, no problem.

We are talking about the P2Pool nodes.

[IYFTech]

Payment shows up on my wallet UI, no problem.

We are talking about the P2Pool nodes.

Doh! 

Sorry, still waiting for the coffee to kick in......

[windpath]

The latest block that paid out 330410 isn't showing on my node's list.  Usually this type of thing is due to a block that was orphaned in p2pool but valid on the Bitcoin network.

The difference for this one is that Coincadence (http://minefast.coincadence.com/p2pool-stats.php) usually shows when this happens on the right most column, but for 330410, it's listed as valid(green checkmark). I double checked other people's nodes and none of them show this block.  

So not to look a gift horse in the mouth but... Anyone have any ideas why this one wouldn't show? Is it actually orphaned on p2pool's network even though Coincadence shows it's not?

It was most likely DOA when submitted to whatever node found it, but met the minimum bitcoin difficulty so was submitted to bitcoin, propagated and accepted

If it is accepted by bitcoind and confirmed we will show it as valid, those shown as orphan are actually orphaned.

I keep the 3 popular front ends live on my node as well, none of them saw it:

http://minefast.coincadence.com:9332/static/original/
http://minefast.coincadence.com:9332/static/node-status/
http://minefast.coincadence.com:9332/static/extended/

I'm able to find these and show them here:

http://minefast.coincadence.com/p2pool-stats.php

By scanning bitcoind blocks for the share hash (the share hash is the last 8 characters of the block hash)..

For block 330410:
Share Hash: 7b853c9b
Block Hash: 00000000000000001747b51ad4fc5590668ac17752bf6aa14cac12637b853c9b

[IYFTech]

Who just added 2Ph? 

[windpath]

Who just added 2Ph?  

AntPool?

We will be able to spot the address (assuming it's a single address) on my node after the next block is found...

Here is the current top 27 miners (by % of current share chain)



Edit: We had a similar spike back in October, the ~2PH/s did not stick around long, could be p2pool is a fail-over for a large mine??

[jedimstr]

The latest block that paid out 330410 isn't showing on my node's list.  Usually this type of thing is due to a block that was orphaned in p2pool but valid on the Bitcoin network.

The difference for this one is that Coincadence (http://minefast.coincadence.com/p2pool-stats.php) usually shows when this happens on the right most column, but for 330410, it's listed as valid(green checkmark). I double checked other people's nodes and none of them show this block. 

So not to look a gift horse in the mouth but... Anyone have any ideas why this one wouldn't show? Is it actually orphaned on p2pool's network even though Coincadence shows it's not?

It was most likely DOA when submitted to whatever node found it, but met the minimum bitcoin difficulty so was submitted to bitcoin, propagated and accepted

If it is accepted by bitcoind and confirmed we will show it as valid, those shown as orphan are actually orphaned.

I keep the 3 popular front ends live on my node as well, none of them saw it:

http://minefast.coincadence.com:9332/static/original/
http://minefast.coincadence.com:9332/static/node-status/
http://minefast.coincadence.com:9332/static/extended/

I'm able to find these and show them here:

http://minefast.coincadence.com/p2pool-stats.php

By scanning bitcoind blocks for the share hash (the share hash is the last 8 characters of the block hash)..

For block 330410:
Share Hash: 7b853c9b
Block Hash: 00000000000000001747b51ad4fc5590668ac17752bf6aa14cac12637b853c9b

Thanks, I misunderstood what the checkmark showed in your stats... I knew you were scanning bitcoind history for p2pool DOA/valid Bitcoin blocks, but thought you were identifying those cases with the "not" symbol.  So those listed with that symbol in your stats, they're actually fully DOA on both networks. 

Ever thought of adding another column then since you have the data to identify DOA on P2pool but valid BTC blocks?

[PatMan]

Who just added 2Ph?  

AntPool?

Edit: We had a similar spike back in October, the ~2PH/s did not stick around long, could be p2pool is a fail-over for a large mine??

Looks like you're right - whoever it was has gone again......

Edit: Has anyone sifted through the changes made by Bitmain in their p2pool git repo yet? Any thoughts? I'm shite with python code, so it's over my head I'm afraid.....