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

[forrestv]

Looking into this. More news soon.

[JayCoin]

P2Pmining.com is getting the same error, but most all of my users DOA rate as dropped from ~5% to less than 1%.

[forrestv]

I need as many people as possible to upgrade to commit 0dbb9da28511

Windows build: http://u.forre.st/u/olaxgozi/p2pool_win32_0.11.1-34-g0dbb9da.zip

After a while, everyone's mining will begin working again.

[ChanceCoats123]

Upgrading now.

[JayCoin]

p2pmining.com is now upgraded

[echris1]

static page also shows 40% pool stale rate, upgrading now, might want to send out an announcement on that mailing list I get every now and then (forget where that was exactly, some sort of digest)

[ChanceCoats123]

Got that right away.

[forrestv]

Trying a different approach - get commit 68c11d56a46f388 (current master HEAD) instead! It reverts completely to the old behavior and doesn't drop peers.

Windows: http://u.forre.st/u/oirgpput/p2pool_win32_0.11.1-39-g68c11d5.zip

You will get some errors occasionally, but they should only be like:

Code:

2012-05-18 00:52:25.520715 > exceptions.ValueError: unknown share type: 6

[JayCoin]

While I was upgrading I noticed that in bitcoin/networks.py that the SANE_TARGET_RANGE=(2**256//2**32 - 1 , 2**256//2**32 - 1)

I changed it in my code to a little bigger range than that.  Is that to default everyone to difficulty 1 pseudo shares?

[forrestv]

New version! Pull from git or use http://u.forre.st/u/ocpualfo/p2pool_win32_0.11.1-41-g0dbcc28.zip

[forrestv]

JayCoin: I was paranoid about non-difficulty-1 shares possibly triggering bugs in miners, so I fixed the difficulty to 1 (or .9998.., rather, whatever it is)

[forrestv]

Anyone using previously posted versions needs to stop using them.

[qdi]

ubuntu , p2poll script (forrestv-p2pool-fb1e69b, May  4 ) and cgminer work, but i see stderr

Code:

2012-05-18 10:30:18.272093  Local: 1095MH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-5%) Expected time to share: 25.0 minutes
2012-05-18 10:30:18.272126  Shares: 167 (21 orphan, 2 dead) Stale rate: ~13.8% (9-20%) Efficiency: ~134.4% (124-142%) Current payout: 0.2010 BTC
2012-05-18 10:30:18.272164  Pool: 283GH/s Stale rate: 35.8% Expected time to block: 7.3 hours
2012-05-18 10:30:21.297343 P2Pool: 17326 shares in chain (17331 verified/17542 total) Peers: 10 (0 incoming)
2012-05-18 10:30:21.297453  Local: 1088MH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-5%) Expected time to share: 25.2 minutes
2012-05-18 10:30:21.297485  Shares: 167 (21 orphan, 2 dead) Stale rate: ~13.8% (9-20%) Efficiency: ~134.4% (124-142%) Current payout: 0.2010 BTC
2012-05-18 10:30:21.297522  Pool: 283GH/s Stale rate: 35.8% Expected time to block: 7.3 hours
2012-05-18 10:30:22.330398 > Traceback (most recent call last):
2012-05-18 10:30:22.330501 >   File "/home/zzz/p2pool/p2pool/p2p.py", line 205, in handle_shares
2012-05-18 10:30:22.330534 >     self.node.handle_shares([p2pool_data.load_share(share, self.node.net, self) for share in shares], self)
2012-05-18 10:30:22.330565 >   File "/home/zzz/p2pool/p2pool/main.py", line 265, in handle_shares
2012-05-18 10:30:22.330592 >     set_real_work2()
2012-05-18 10:30:22.330619 >   File "/home/zzz/p2pool/p2pool/main.py", line 183, in set_real_work2
2012-05-18 10:30:22.330647 >     best, desired = tracker.think(get_height_rel_highest, pre_current_work.value['previous_block'], pre_current_work.value['bits'])
2012-05-18 10:30:22.330676 >   File "/home/zzz/p2pool/p2pool/data.py", line 403, in think
2012-05-18 10:30:22.330703 >     if not self.attempt_verify(share):
2012-05-18 10:30:22.330729 > --- <exception caught here> ---
2012-05-18 10:30:22.330755 >   File "/home/zzz/p2pool/p2pool/data.py", line 353, in attempt_verify
2012-05-18 10:30:22.330781 >     share.check(self)
2012-05-18 10:30:22.330807 >   File "/home/zzz/p2pool/p2pool/data.py", line 247, in check
2012-05-18 10:30:22.330833 >     raise p2p.PeerMisbehavingError('''Share can't follow NewShare''')
2012-05-18 10:30:22.330859 > p2pool.p2p.PeerMisbehavingError: Share can't follow NewShare
2012-05-18 10:30:22.342614 Requesting parent share b065dc22 from 72.130.76.188:9333
2012-05-18 10:30:22.527558 New work for worker! Difficulty: 0.999985 Share difficulty: 378.072338 Total block value: 50.087675 BTC including 161 transactions
2012-05-18 10:30:24.350461 P2Pool: 17327 shares in chain (17331 verified/17542 total) Peers: 10 (0 incoming)
2012-05-18 10:30:24.350575  Local: 1095MH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-5%) Expected time to share: 24.9 minutes
2012-05-18 10:30:24.350608  Shares: 167 (21 orphan, 2 dead) Stale rate: ~13.8% (9-20%) Efficiency: ~134.1% (124-142%) Current payout: 0.2010 BTC
2012-05-18 10:30:24.350645  Pool: 281GH/s Stale rate: 35.7% Expected time to block: 7.3 hours
2012-05-18 10:30:26.743911 New work for worker! Difficulty: 0.999985 Share difficulty: 376.485795 Total block value: 50.088675 BTC including 163 transactions
2012-05-18 10:30:27.378712 P2Pool: 17328 shares in chain (17332 verified/17543 total) Peers: 10 (0 incoming)

[forrestv]

ubuntu , p2poll script and cgminer work, but i see stderr

qdi, git pull and try again.

[qdi]

ubuntu , p2poll script and cgminer work, but i see stderr

qdi, git pull and try again.

working fine

[rav3n_pl]

What about "desired versions"?
Red is good or blue? I see on graph that after reset I get all red, now some blue is popping in. Same thing in your. Just change to hour.
http://forre.st:9332/static/graphs.html
http://91.235.254.37:9332/static/graphs.html

[mdude77]

Got that right away.

I got that too on upgrading.  Looked like there was something wrong with some local shares.  After that it loaded the rest just fine and is now up and running.  Hope it stops the local rejects.

Having a rough time here with p2pool.  I get random communication problems with p2pmining.com, so my local p2pool is my backup.  Was averaging 10% rejects on my local and higher on p2pmining because of the comm problems.

M

[rav3n_pl]

It is now 50/50 new/old versions.

Pool rate: 439GH/s (38% stale) Share difficulty: 655 O_o
Why so much orphans?

[ChanceCoats123]

Just got on the latest version. I went to bed before forrestv put out the "final" patched version so I was on the wrong one all night. Oh well. Only 30% stales. 

Hopefully this latest will be the ticket. I noticed we're already at 471gh for the pool. We've never been this high before. Maybe there was an issue before that was cutting the hashrate.

[Aseras]

yeah always nice to wake up to 80% orphan shares....

so what happened the "killswitch" for the older versions take out the new versions too?