As a separate issue, I now realize that current P2Pool doesn't allow *expressing* support for SegWit, due to line 372 in
work.py, which veqtrus's changes don't touch:
version=max(self.current_work.value['version'], 0x20000000),
If anyone can confirm that fixing that is as simple as changing it to
version=max(self.current_work.value['version'], 0x20000002),
, then I will publish a new P2Pool release with that change.
This is wrong. I changed p2pool to signal
whatever BIP9 compatible fork a client supports in the
CSV commit.
How to get out of this situation? Now for my node I use veqtrus patches from the segwit1+empty_block_fix1 branch of a
https://github.com/veqtrus/p2pool.git repository.
When my node's hashrate was raised and the amount of v17 shares was increased above then 50%, the message with a link to p2pool.in appeared on another nodes. But there is no announcement about a new version. Owners of other nodes will not do anything.
What to do if the main developers can not agree?