Quote from: M8BWNNRFMNdak68c on August 06, 2017, 11:01:40 AM

so can you tell me if i got this right: if i now use this version: https://github.com/jtoomim/p2pool/commits/1mb_segwit and mine on my own node, the following 3 conditions are fulfilled:

1) i join the network with 1.4 PHash visible here: http://p2pool.org/stats/
2) it is not possible to create orpahn blocks,as every node will signal segwit support
3) it will be possible to mine blocks in around three weeks, when there are normal tx as well as segwit tx in the bitcoin network. ( and get fees from both )

1. Yes.

2. Only if the Bitcoin full node that your P2Pool node is connected to is itself signaling for BIP141 (i.e., setting segwit's BIP9 versionbit of bit 1), and if you haven't explicitly configured your P2Pool node to signal differently. The P2Pool code, by default, will use whatever signaling that is included in the block template that is provided by the Bitcoin full node that it is connected to. If you are running Bitcoin Core 0.13.1 or later, Bitcoin Knots 0.13.1 or later, btc1's segwit2x client, or the UASF client, you would be signaling for BIP141.

3. In theory, yes. However, jtoomim's 1mb_segwit code has not yet been fully tested to see if it can actually mine segwit blocks.

Quote from: jtoomim on August 03, 2017, 10:21:51 PM

Sorry this took so long. I haven't fully tested this to make sure it works on testnet and can make segwit blocks, but if people can help review it and maybe help test it, that would be nice.

https://github.com/jtoomim/p2pool/commits/1mb_segwit

Segwit compatibility stuff starts with the July 19th commits.

...