Quote from: kano on June 05, 2017, 06:08:53 PM

Quote from: jtoomim on June 05, 2017, 04:12:18 PM

Quote from: frodocooper on June 02, 2017, 03:22:41 AM

Speaking of BIP148, are there any contingency plans in place for P2Pool handling the fork? As far as I'm aware, both mainnet and jtoomimnet are currently not compatible with segwit. So when BIP148 activates and in the off-chance that it replaces the legacy non-segwit chain, or if circumstances post-BIP148 manage to trigger the 95% segwit threshold on the legacy chain we P2Pool miners would be hung out to dry.

BIP148 states that all miners must signal for SegWit after August 1st. Currently, p2pool is capable of signaling for SegWit, so p2pool is compatible with this phase. If a majority of miners are following BIP148, then SegWit (BIP141) will enter into the LOCKED_IN state for two weeks, followed by the ACTIVE period two weeks after that. If 100% of miners follow BIP148, then the signaling phase will last 2 weeks. (If 10% follow, then 20 weeks, etc.) This plus the LOCKED_IN period means that we will have at least 4 weeks after August 1st before p2pool becomes incompatible with ~~the Bitcoin~~ some minority alt-coin based on Bitcoin chain.

It should take a week or less to merge and test SegWit support into jtoomimnet and/or mainnet's code. We'll be fine.

Corrected a typo there ...

If the majority of miners follow BIP148 there will be no chain split since it is a soft fork.