I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

It was only released two hours ago, so it's not surprising that few nodes have updated. Changing those values would prevent a smooth transition. Everything will be fine, if it goes at all similarly to how the last hardfork did.

P2Pool release 15.0 - commit hash: 86bbdac7eaaa03438e71ee9dcb11898c7b2b8bdf

HARDFORK - Upgrade URGENTLY required in the next few days.

Windows binary: http://u.forre.st/u/ovqxauzj/p2pool_win32_15.0.zip
Windows binary signature: http://u.forre.st/u/wynjbvpn/p2pool_win32_15.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/15.0
Source tarball: https://github.com/forrestv/p2pool/tarball/15.0

Changes:
* BIP65/block version 4 compatibility
* Requires Bitcoin >=0.11.2 (for BIP65 compatibility)

BIP65 will take effect in the next week and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP65 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.

So, please upgrade to 15.0 now and also tell everyone else to.

For Linux systems, run_p2pool.py is marked executable and has a Python shebang, so you can directly run it.

notbatman: P2Pool tries to obtain its version number by executing git and, if that fails, examining the name of the directory it's in. However, neither of those worked on your system, so it just used the (hex-encoded) name of the directory it's in. It's not a problem.

TTravis: You don't actually need to run make. It's not even mentioned in the README. It's only there for assisting development. Just run ./run_p2pool.py.

The primary P2Pool repository has moved from https://github.com/forrestv/p2pool to https://github.com/p2pool/p2pool. GitHub redirects should ensure that everything continues to work, but efforts should be made to use the new URL instead of the old one.

If the fork to 8MB blocks happens, P2Pool will require changes to support 8MB blocks and its own fork to get everyone using the changes. That said, it's a ways off and the changes should be pretty straightforward.

It's limited to prevent DoS attacks on P2Pool by e.g. making a bunch of fake transactions and then forcing them to be relayed across the entire P2Pool network. With this limit, an attacker can only force every other P2Pool node to download, at most, 50kB per share the attacker mines.

Given that 100kB transactions are possible, it should probably be 100kB, not 50kB, but it doesn't have much of an effect otherwise, since 50kB/share is comparable to the maximum transaction throughput allowed by Bitcoin (500kB/block).

K1773R, your "hackish fix" will result in your shares being orphaned if it ever results in differing behavior. The contents of the generate_transaction function are used to determine consensus, so if your version acts different, other nodes will see your shares as invalid.

Hey, I've been watching. You are trying the recent P2Pool commit that blocks pre-v14 peers, right? If that's confirmed to help, I'll make a P2Pool release with it.

Some P2P network thrashing is normal after a fork since you have the unupgraded nodes madly trying to find peers and download the (invalid to them) sharechain. Normally, there are less unupgraded nodes, but this fork was rushed, so I think that that contributed to it.

However, some are reporting high bitcoind CPU usage - P2Pool P2P network activity shouldn't be affecting bitcoind, so I'm not sure about that. Is that happening for Bitcoin users without P2Pool? It might be some similar post-BIP66 effect.

Please try the latest commit. It doesn't allow connections to v13 nodes.

We are now exclusively switched to v14.0. All v13 miners have been excluded following BIP66 taking effect.

I think the commit I just pushed should remove them.

Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

No, not yet. You can watch http://bitcoin.sipa.be/ver-2k.png for the red line crossing 2.95 or run:


which will return 950 or higher when BIP66 takes effect.

jtoomim, did you see my last response to you? The situation is dire, but nowhere near as dire as you think. All non-14.0 miners can be separated from once BIP66 takes effect, so people who have upgraded will be at no disadvantage.

Hmm, thank you for reporting this. Some ... interesting things ... got merged in in pull request #210. Can you make an issue on GitHub? I'll look into it soon. For now, I don't recommend anyone besides Bitcoin users to use 14.0.

Depends on the averaging period. Meuh6879 is using the "Hour" graph.

Thank you for your efforts, windpath!

If the current trend continues (see http://bitcoin.sipa.be/ver-2k.png), BIP66 will take effect in 1.6 days. We are at 63% converted. It looks like at least a substantial fraction of P2Pool's hashrate won't make it in time... I'm a bit surprised that with the warning being displayed, things aren't moving faster. Also a bit angry that some of the alternative frontends hide the warnings.

That's the point at which the automatic switchover would take place, but it's possible to manually trigger it too. I'll do that once BIP66 takes effect, if necessary.

Monday is likely too late. I'm sorry about providing this update with so little time to spare; it really is very urgent. If all goes according to the plan, anyone upgrading on Monday or later will be on the unupgraded side of the hardfork doing useless (unpaid) work.

CoinCadence has a substantial proportion of the P2Pool hashrate. Upgrading now or soon would help everyone.

That should be normal. The patch accepted from midnightmagic throttles the prints from different workers. I'm not sure why it's printing blanks, though - I'll look into it.