[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[sawa]

https://github.com/veqtrus/p2pool/releases/tag/16.1-segwit

What wallet do you recommend to use with this version of the p2pool?

[veqtrus]

https://github.com/veqtrus/p2pool/releases/tag/16.1-segwit

What wallet do you recommend to use with this version of the p2pool?

Bitcoin Core 0.13.1+ will do.

[Comandante77]

Hi, everybody.

Here's the situation - some time ago I've installed p2pool for solo mining DASH and it worked just fine. But some time after that something happened. Nothing was changing in conf etc. But till now if I run pool in solo, I'm getting the following thing:

Code:

 Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.251514 P2Pool: 1060 shares in chain (1387 verified/1387 total) Peers: 0 (0 incoming)
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.251975  Local: 31329MH/s in last 55.2 seconds Local dead on arrival: ~81.1% (77-85%) Expected time to share: 0.0 seconds
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.252226  Shares: 404 (0 orphan, 327 dead) Stale rate: ~80.9% (76-85%) Efficiency: ~36.1% (29-44%) Current payout: (1.8038)=1.8038 DASH
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.252481  Pool: 1577kH/s Stale rate: 47.2% Expected time to block: 55.7 years
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.571851 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 90dd0986 prev 575e0abe age 17.96s DEAD ON ARRIVAL
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.697558 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS a9e748db prev 575e0abe age 18.08s DEAD ON ARRIVAL
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.863956 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 5d288c96 prev 575e0abe age 18.25s DEAD ON ARRIVAL
Aug 11 15:19:39 dashpool after.local[727]: 2017-08-11 15:19:39.988701 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 5fc91ae9 prev 575e0abe age 18.38s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.123384 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 0902d48c prev 575e0abe age 18.51s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.249917 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS bf7845c9 prev 575e0abe age 18.64s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.408505 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 6492991e prev 575e0abe age 18.80s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.552668 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS e2edb1d8 prev 575e0abe age 18.94s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.689154 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS d84ac688 prev 575e0abe age 19.08s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.850690 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 64fce7db prev 575e0abe age 19.24s DEAD ON ARRIVAL
Aug 11 15:19:40 dashpool after.local[727]: 2017-08-11 15:19:40.979945 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS a4cd6355 prev 575e0abe age 19.37s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.116009 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 6224f00e prev 575e0abe age 19.50s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.246567 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 04d2b59a prev 575e0abe age 19.63s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.411804 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS d7361036 prev 575e0abe age 19.80s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.568153 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 2509fd36 prev 575e0abe age 19.96s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.716456 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS bbf91a93 prev 575e0abe age 20.10s DEAD ON ARRIVAL
Aug 11 15:19:41 dashpool after.local[727]: 2017-08-11 15:19:41.883776 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 281ce72c prev 575e0abe age 20.27s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.017621 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS e247025f prev 575e0abe age 20.40s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.157962 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS e8303b3d prev 575e0abe age 20.55s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.324268 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS f91f830e prev 575e0abe age 20.71s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.466992 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 538524ce prev 575e0abe age 20.85s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.610814 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 6bcbc613 prev 575e0abe age 21.00s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.744709 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 7f9d0c70 prev 575e0abe age 21.13s DEAD ON ARRIVAL
Aug 11 15:19:42 dashpool after.local[727]: 2017-08-11 15:19:42.927852 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 22a08792 prev 575e0abe age 21.32s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.124296 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 12fce71b prev 575e0abe age 21.51s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.276714 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 55f77119 prev 575e0abe age 21.66s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.436520 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 7229c0cf prev 575e0abe age 21.82s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.570993 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS e2c6f0a9 prev 575e0abe age 21.96s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.712225 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 80c5c28f prev 575e0abe age 22.10s DEAD ON ARRIVAL
Aug 11 15:19:43 dashpool after.local[727]: 2017-08-11 15:19:43.895698 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 226fc843 prev 575e0abe age 22.28s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.040242 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS bfefcc77 prev 575e0abe age 22.43s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.183415 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 7885b237 prev 575e0abe age 22.57s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.390041 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 92d7da13 prev 575e0abe age 22.78s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.538710 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 938f539f prev 575e0abe age 22.93s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.698683 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 2894f0d7 prev 575e0abe age 23.09s DEAD ON ARRIVAL
Aug 11 15:19:44 dashpool after.local[727]: 2017-08-11 15:19:44.879845 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 08da9fa0 prev 575e0abe age 23.27s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.018241 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 2d310f17 prev 575e0abe age 23.41s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.156301 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 5ff3cf3d prev 575e0abe age 23.54s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.323289 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS adf7ec0c prev 575e0abe age 23.71s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.468251 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 990a2f39 prev 575e0abe age 23.86s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.631328 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 0d7b6052 prev 575e0abe age 24.02s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.808860 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 87284a14 prev 575e0abe age 24.20s DEAD ON ARRIVAL
Aug 11 15:19:45 dashpool after.local[727]: 2017-08-11 15:19:45.960083 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS a5548ebd prev 575e0abe age 24.35s DEAD ON ARRIVAL
Aug 11 15:19:46 dashpool after.local[727]: 2017-08-11 15:19:46.102473 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS f416ec3a prev 575e0abe age 24.49s DEAD ON ARRIVAL
Aug 11 15:19:46 dashpool after.local[727]: 2017-08-11 15:19:46.241812 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 7ce4963b prev 575e0abe age 24.63s DEAD ON ARRIVAL
Aug 11 15:19:46 dashpool after.local[727]: 2017-08-11 15:19:46.411909 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS 1742df38 prev 575e0abe age 24.80s DEAD ON ARRIVAL
Aug 11 15:19:46 dashpool after.local[727]: 2017-08-11 15:19:46.552309 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS c21a495c prev 575e0abe age 24.94s DEAD ON ARRIVAL
Aug 11 15:19:46 dashpool after.local[727]: 2017-08-11 15:19:46.726894 GOT SHARE! XwXLJZTQg34FEhHECL4ykkoDP9gxuL3BxS  

Pool going down after few seconds.

What does it mean?

Pool and miners are not on one lan segment. Ping between them smth about 10ms.

Whats wrong?

[veqtrus]

Here's the situation - some time ago I've installed p2pool for solo mining DASH and it worked just fine. But some time after that something happened. Nothing was changing in conf etc. But till now if I run pool in solo, I'm getting the following thing:

When solo mining using P2Pool if you stop mining for an extended time period the share difficulty will become too low and your miners will send shares too fast for P2Pool to handle.

[Comandante77]

When solo mining using P2Pool if you stop mining for an extended time period the share difficulty will become too low and your miners will send shares too fast for P2Pool to handle.

  Yes, this happened right after I've stopped miners for maintance for smth about 9 hours.
  But, I've tried to use fresh installation of wallet and p2pool on another server and I've got the same result.

  How I should fix this problem?

  Thanks in advance.

[jtoomim]

Comandante77, I fixed this bug in the 1mb_hardforked, lowmem, and 1mb_segwit branches on my github. The main commit that addressed this issue is this one:

https://github.com/jtoomim/p2pool/commit/428bbe4211c39fe3175a9464fb253a699b792e5e

The problem is that p2pool has to guess what a reasonable pseudoshare difficulty is when it doesn't know how much hashrate the node has (i.e. on startup), and if you are running a node with a lot of hashrate, it can guess terribly wrong. If the difficulty is too low, your node will get flooded with shares, and the hashrate that your node sees will be limited by your node's CPU power in processing shares instead of being limited by your miners' actual hashrate. This makes your node think its hashrate is low, which makes it lower the pseudoshare difficulty, which makes the problem worse.

I fixed it by setting the initial pseudoshare difficulty to equal 1/100th or 1/1000th of the p2pool minimum real share difficulty, which results in about 1 share every 30ms to 300ms if you have the full pool on your node (i.e. you're solo mining).

[jtoomim]

The p2pool fork mechanism works like this:

• If share 8640 is the most recent share, then fetch shares 864 through 1728. Look at each share, and calculate the expected number of hashes needed to find that share (i.e. the work done by that share). Look at whether that share was voting for an upgrade or not.
• If more than 60% of the hashrate for those shares voted for an upgrade, then upgraded shares are now allowed on the network, and this node will follow an upgrade if another node initiates the switch.
• If more than 95% of the hashrate for those shares voted for an upgrade, then this node will initiate the switch to upgraded shares.

8640 shares normally takes 72 hours to mine. This means that in order to fork, the hashrate generally needs to have been upgraded 64.8 hours before the desired forking time. As far as I can tell, it is now too late for p2pool mainnet to smoothly upgrade to support SegWit. If veqtrus wishes to keep p2pool's mainnet alive and supporting SegWit, he will need to create a version that forks without using the voting mechanism, or which uses a different voting mechanism.

jtoomimnet's hashrate began voting for v33 (segwit-supporting) shares about 64 hours ago. Currently, the critical forking window is showing 23.72% support for v33 shares and climbing rapidly. Segwit's activation on Bitcoin is still about 8 hours away. I expect that jtoomimnet will reach the 60% threshold in about 2 or 3 hours, and will reach the 95% threshold in about 6 hours. jtoomimnet will probably fork just fine without any further action on my part or anyone else's. I may manually initiate a v33 share after the 60% threshold is exceeded or configure my nodes to generate a bunch of low-difficulty shares in order to speed things up if it looks like activating in time is otherwise uncertain.

To use jtoomimnet, run these commands:

Code:

git clone https://github.com/jtoomim/p2pool.git
cd p2pool
git checkout lowmem

Using pypy is instead of regular Python2.7 is strongly recommended. Instructions for installing pypy on Ubuntu or Debian can be found here: https://bitcointalk.org/index.php?topic=18313.msg21025074#msg21025074

[jtoomim]

39.2% so far, 6.4 hours remaining.

I'm going to go ahead and make a bunch of min-diff shares to get some headroom.

[jtoomim]

61.2% 63.8% of shares in the critical window (from Sunday) on jtoomimnet now support v33. Creation of a v33 share on jtoomimnet would now be legal. I'm going to let it keep going for a while as is. If it looks uncertain that it will reach 95% before Segwit is active on Bitcoin, I'll trigger the v33 share creation manually. (This only needs to be done on one node -- all other nodes will follow. No software upgrades are necessary at this point unless there are unknown bugs in the code.)

Edit: we've crossed 65%, which means that everyone on jtoomimnet should now be able to see the upgrade progress in their console output.

[veqtrus]

While Forrest has merged the segwit PR it is important that Don't mine segwit txs for now is included as well to remain compatible with the old share format which doesn't handle segwit txs.

[jtoomim]

94.031%... almost there.

Edit: It looks like 94.0-94.5% is the most we got on Sunday. We didn't get above 95% until rather late on Sunday evening. I'm going to go ahead and make a v33 share and manually trigger it now.

Edit2: looks like there's a problem. It seems the share unpacker is not handling the segwit section properly. Investigating now.

Edit3: It looks like the rest of p2pool is working fine, it's just that my manually created share isn't propagating properly. Looking into why.

Edit4: Found the bug. It will require that all 1mb_segwit users do a git pull once I push the changes to my repo. Give me a couple of minutes.

[Comandante77]

Comandante77, I fixed this bug in the 1mb_hardforked, lowmem, and 1mb_segwit branches on my github. The main commit that addressed this issue is this one:

https://github.com/jtoomim/p2pool/commit/428bbe4211c39fe3175a9464fb253a699b792e5e
I fixed it by setting the initial pseudoshare difficulty to equal 1/100th or 1/1000th of the p2pool minimum real share difficulty, which results in about 1 share every 30ms to 300ms if you have the full pool on your node (i.e. you're solo mining).

  After these manipulations pool is seems to work. But some thing are strange, Expected time to block ~200years.

 

Code:

Version: 5fd602d-dirty

Pool rate: 990kH/s (19% DOA+orphan) Share difficulty: 0.000244

Node uptime: 4.2 minutes Peers: 0 out, 0 in

Local rate: 115GH/s (14% DOA) Expected time to share: 0.0 seconds

Shares: 278 total (0 orphaned, 68 dead) Efficiency: 92.75%

Payout if a block were found NOW: 1.80534499 DASH to XcpNdXxdGJp56etznM2kNJJi1RDperBeg3. Expected after mining for 24 hours: 421000 DASH per block.

Current block value: 3.61068987 DASH Expected time to block: 190.7 years

[jtoomim]

Ok, the fix is live. If you're using 1mb_segwit, please perform a git pull ASAP. I will wait 30 minutes or so, then I will manually generate a v33 share again. If you have not updated by then, you will get forked off the network.

Edit: v33 share is coming in about 2 more minutes. This *will* cause anybody who hasn't done a git pull in the last 30 minutes to get forked off the network. Please update ASAP.

Edit2: v33 share is done. Anyone who has not done a git pull will be forked off. They will also see frequent error messages and suck up a lot of bandwidth as they repeatedly try to download the v33 shares. Things seem to be working properly for nodes that are running the most recent code.

Edit3: In order to avoid wasting the bandwidth of people on the old 1mb_segwit code, I am incrementing the protocol version number to 3301. That commit was added to 1mb_segwit about 2 minutes ago. In a little while, I will add some code that causes p2pool nodes to refuse to connect to any nodes with a protocol version less than 3301 in order to avoid the repeated share transmission from hogging up bandwidth. Do another git pull.

[jtoomim]

Comandante77, your node appears to be functioning correctly. The estimates of time to block and DASH per block will be really wonky for a few days, but the issue is just due to the hashrate estimates not being very smart when the hashrate of the pool and your node change dramatically, and is not a problem with revenue generation or block creation. It's just cosmetic. Give it a few days and it will become more reasonable.

[frodocooper]

... In a little while, I will add some code that causes p2pool nodes to refuse to connect to any nodes with a protocol version less than 3301 in order to avoid the repeated share transmission from hogging up bandwidth...

Here's to hoping that "little while" would be as soon as possible. My v3301 node is eating up 10x more bandwidth than before: a consistent and relentless average of 500 kB/s in, 500 kB/s out compared to the pre-v3301 average of 50 kB/s in, 50 kB/s out.

Edit: Bandwidth usage seems to have dropped back to normal levels.

[jtoomim]

I added enough so that it will /eventually/ automatically disconnect from version <= 3300 peers. That will happen whenever the shares in the critical window are > 95% v33.  If you want to accelerate the process, you can do so by setting

Code:

MINIMUM_PROTOCOL_VERSION = 3301

in p2pool/networks/bitcoin.py. No harm will come from you doing this now. I want to keep my nodes accepting connections from version 3300 peers for a while longer in case someone upgraded in the 30 minute window in between me fixing the critical bug with parsing v33 shares and me adding v3301 to the protocol version.

Edit: Okay, I just pushed that change to the repo. git pull.

[frodocooper]

I added enough so that it will /eventually/ automatically disconnect from version <= 3300 peers. That will happen whenever the shares in the critical window are > 95% v33.  If you want to accelerate the process, you can do so by setting

Code:

MINIMUM_PROTOCOL_VERSION = 3301

in p2pool/networks/bitcoin.py. No harm will come from you doing this now. I want to keep my nodes accepting connections from version 3300 peers for a while longer in case someone upgraded in the 30 minute window in between me fixing the critical bug with parsing v33 shares and me adding v3301 to the protocol version.

Edit: Okay, I just pushed that change to the repo. git pull.

Got it. Thanks, jtoomim. Everything seems to be back to normal now.

[Blue Bear]

2017-08-24 21:07:56.307000 > ########################################
2017-08-24 21:07:56.308000 > >>> Warning: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v17 with 72% support)
2017-08-24 21:07:56.309000 > An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.
2017-08-24 21:07:56.310000 > ########################################
2017-08-24 21:07:56.310000 > ########################################
2017-08-24 21:07:56.311000 > >>> Warning: (from bitcoind) Warning: Unknown block versions being mined! It's possible unknown rules are in effect
2017-08-24 21:07:56.311000 > ########################################


Would anyone care to enlighten me as to why I am getting these warnings?

[kano]

...
Would anyone care to enlighten me as to why I am getting these warnings?

Read just about any post in the last 2 pages?

[Blue Bear]

[/quote]
Read just about any post in the last 2 pages?
[/quote]
Last 2 pages look like a train wreck in progress. I just want to make sure I am on the right tracks to avoid the wreck.

what I see here is Jtoomim pulling a good portion of the pool the way he wants to go regardless of the consequences. Appearing to shout down anyone who might caution what he is doing.
On the github site of the pool forrestv is implementing most of the recommendations that veqtrus is putting out.

I just updated the Master P2pool code onto my computer for my node and am still getting the errors ...

This has me wondering if I need to rebuild my node from scratch (which I don't relish the idea of) to get back to basics.