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

[rav3n_pl]

If I read all properly, the current share chain version (desired) is v4, p2pool version is v5.
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?

[twmz]

An update to p2pool.info is uploading now that works with the final version of bitcoind 0.7.  Note, as a side effect, I have stopped displaying subsidies.  The new version of bitcoind makes is way to painful to look at the details of every transaction in a block (which is required for looking for subsidies), so I removed that functionality. 

Since the age of regular subsidies appears to be long past, I guess that no one will care that this functionality is gone, but I thought I would mention it in case anyone noticed and wondered what was going on.

[iongchun]

If I read all properly, the current share chain version (desired) is v4, p2pool version is v5.
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?

As you can see from the OP, the current p2pool release is 3.1, with desired share version 3,
which is still the largest part in current p2pool network.
It is not compatible with Bitcoin v0.7.

The desired share version jumped from 3 to 4 about three weeks ago, and was tagged as p2pool version 4.0.
It is not announced (updated in OP) yet, but everyone pulled from the git repository in the past three weeks use this version,
with different further changes. It is the second largest part in current p2pool network.
It is compatible with Bitcoin v0.7.

[forrestv]

P2Pool release 5.0 tag: 5.0 hash: 11b050873e2a77869fdf4f86d2a9cb14e6dd2966

Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0

Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support

Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).

[kjj]

P2Pool release 5.0 tag: 5.0 hash: 11b050873e2a77869fdf4f86d2a9cb14e6dd2966

Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0

Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support

Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).

Doh!  Is there any compelling need to switch to version 5 of p2pool?  I just rolled out my stuff using version 4 and bitcoind-0.7.0 yesterday.

[forrestv]

kjj: No, not really; you'll eventually start getting spammed warnings about needing to upgrade to v5 when 50% of everyone else upgrades to v5, but there's nothing essential there as long as you are actually running Bitcoin 0.7.0.

[mdude77]

What link?

I'm a windows guy.

https://github.com/forrestv/p2pool/zipball/master

That's what gave me 'forrestv-p2pool-4.0-0-g2adf77e.zip'

Now when I go there I get 'forrestv-p2pool-5.0-2-gb1e5a50'.

Upgrading...

M

[rav3n_pl]

What link?

I'm a windows guy.

https://github.com/forrestv/p2pool/zipball/master

That's what gave me 'forrestv-p2pool-4.0-0-g2adf77e.zip'

Now when I go there I get 'forrestv-p2pool-5.0-2-gb1e5a50'.

Upgrading...

M

Now you can use zip form #1 post
https://bitcointalk.org/index.php?topic=18313.msg231846#msg231846

[Ed]

Could someone help me please with following problem?
LAN and WAN miners have problem with p2pool - some time after start mining (with <1% DOA) DOA is go to 100%.
local host miner working with no problem, <1% DOA

can you give me some ideas?

[rav3n_pl]

They are your miners? It looks like bad miner config for me.
It may be also connections form far away and ping kill all joy.

[Ed]

They are your miners?

one at local host (127.0.0.1) same PC as p2pool
one at LAN same private IP net
one at WAN directed to assigned by router IP

okayIt looks like bad miner config for me

all config, all miners are identical

It may be also connections form far away and ping kill all joy.

LAN <1ms
WAN <10ms
no lost packets

[rav3n_pl]

Hardware failure then. Overheating or something.

[Aseras]

what version of bitcoin and p2pool are you running. There was a bug that caused this in an earlier version when bitcoind would stop responding to p2pool.

[Ed]

what version of bitcoin and p2pool are you running. There was a bug that caused this in an earlier version when bitcoind would stop responding to p2pool.

first time seen problem at 3.xx version
upgraded to 4.xx with no luck
and now last versions p2pool and bitcoind with same problem

Hardware failure then. Overheating or something.

LAN and WAN miners has deepbit as backup pool, when DOA is go to 100% I am manually close port, then
they automatically switch to deepbit and working with DOA 0.45%

ps
my second trouble they do not want automatically switch to backup when DOA is go to 100%

[rav3n_pl]

What OS, miner, hardware?

[rav3n_pl]

Pool rate: 400GH/s (7.5% stale) Share difficulty: 930
WTF?
Share diff is hittin roof! Last time it was ~900 on 450-500GH.
Some change in latest code?

[gyverlb]

Pool rate: 400GH/s (7.5% stale) Share difficulty: 930
WTF?
Share diff is hittin roof! Last time it was ~900 on 450-500GH.
Some change in latest code?

Maybe this time there are less stales which makes the rate used to compute the share difficulty higher?

[Krak]

Pool rate: 400GH/s (7.5% stale) Share difficulty: 930
WTF?
Share diff is hittin roof! Last time it was ~900 on 450-500GH.
Some change in latest code?

Probably more separate miners not volunteering a higher share difficulty.

[mdude77]

Pool rate: 400GH/s (7.5% stale) Share difficulty: 930
WTF?
Share diff is hittin roof! Last time it was ~900 on 450-500GH.
Some change in latest code?

btc difficulty did just go through it's bi monthly increase..

M

[jiyu_shi]

what's the matter?

win7 x64, Bitcoin-qt 0.7, p2pool_win32_5.0