For the UAHF, I have an idea for how to deal with it. Each time we receive a share, we can query our bitcoind to see whether that share's previousblockhash refers to a valid block hash in our bitcoind's blockchain (via the getblockheader RPC). If it is, we accept the share and memoize that hash. If it isn't, we ignore that share. This should allow people to mine on either blockchain without needing to worry about people getting valid shares while mining on the other blockchain.

Unfortunately, I'm very busy right now with datacenter stuff, so I don't know when I'll have a chance to implement this.

In order to expedite this as much as possible, p2pool.org is now running this code on Mainnet, cuurently downloading the share chain.

I posted the segwit PR in November last year. Jtoomim has now included it without modifications (except for the version number change) in his 1MB fork. It has been running on vertcoin for months with great success.

Why are you testing jtoomim's fork now when the exact same code has been available since last year?

For some reason, it's not listed on the node dashboards in the "Blocks found in the last day" section, but it's a valid block. If you plug in the block/share's hash into share.html, you can see it. Example:

P2Pool.org is now running jtoomim's fork of P2Pool. The stats page on P2Pool.org is therefore now tracking jtoomimnet's stats, not mainnet's stats.

If you're mining on mainnet, your miner stats will no longer appear on P2Pool.org's stats page as long as windpath continues running jtoomim's fork. This does not mean your shares on mainnet have been lost, just that P2Pool.org is no longer keeping track of mainnet and its miners' stats. If you're looking for your miners' mainnet stats, you would have to look at the web frontend of another mainnet P2Pool node.

If your miner is pointed at P2Pool.org's node, you would now be mining on jtoomimnet. It would take some time for your miner to ramp up to its expected amount of shares on jtoomimnet, while your mainnet shares would start to fall off the mainnet sharechain. This would, in theory and in general, have limited impact on your expected earnings during your miners' transition from mainnet to jtoomimnet.

(I'm assuming that you are not running and mining at your own P2Pool node, and that you were relying on P2Pool.org's stats page for your miners' stats.)

Actually I am mining my own node. It appears to have been knocked off when the switch happened and took me a minute to get it back on line. This leads to the question: If I am running my own node, with 6 outbound connections and 0 inbound connections, am I still connected and part of the pool or am I on my own now?

Actually I am mining my own node. It appears to have been knocked off when the switch happened and took me a minute to get it back on line. This leads to the question: If I am running my own node, with 6 outbound connections and 0 inbound connections, am I still connected and part of the pool or am I on my own now?

This will not work even with bitcoin. I tried to make a solo pool. If I clear the sharechain, change the values of IDENTIFIER, PREFIX, make empty BOOTSTRAP_ADDRSAnd change PERSIST = True in PERSIST = FalseIn this case, the worker can not connect to the pool

You're using the wrong branch. The 1mb_segwit branch has the altcoin and empty sharechain fixes. The 1mb_hardforked branch does not.

Note: 1mb_segwit will work on the same sharechain as 1mb_hardforked and 1mb_lowmem. 1mb_segwit will vote for v33 shares, but until v33 happens it should be compatible with the other jtoomimnet branches. The v33 upgrade will be the same as the hardforks that forrestv has done in the past for upgrading p2pool to be compatible with bitcoin softforks (e.g. OP_CLTV).

Actually I am mining my own node. It appears to have been knocked off when the switch happened and took me a minute to get it back on line. This leads to the question: If I am running my own node, with 6 outbound connections and 0 inbound connections, am I still connected and part of the pool or am I on my own now?

As long as your P2Pool node has at least one connection to another node, inbound or outbound, you are connected to the P2Pool network and your node remains a part of the pool.

And as long as the P2Pool network is online and active (i.e., there are other active P2Pool nodes on the network), your accepted shares are safe even though your own node has lost its copy of the sharechain. The other active P2Pool nodes have your accepted shares in their copies of the sharechain. That is, unless through some catastrophic failure the entire P2Pool network loses your accepted shares or loses all copies of the sharechain, which is next to impossible under normal circumstances.

You're using the wrong branch. The 1mb_segwit branch has the altcoin and empty sharechain fixes. The 1mb_hardforked branch does not.

Note: 1mb_segwit will work on the same sharechain as 1mb_hardforked and 1mb_lowmem. 1mb_segwit will vote for v33 shares, but until v33 happens it should be compatible with the other jtoomimnet branches. The v33 upgrade will be the same as the hardforks that forrestv has done in the past for upgrading p2pool to be compatible with bitcoin softforks (e.g. OP_CLTV).

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 support3) 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 )