Quote from: Blue Bear on August 25, 2017, 04:59:07 AM

Quote from: jtoomim on August 25, 2017, 04:35:34 AM

Quote from: frodocooper on August 19, 2017, 11:44:14 PM

In addition, I highly recommend adding the following two lines to your bitcoin.conf:

Code:

blockmaxsize=1000000
blockmaxweight=4000000

This enables your P2Pool node to mine full blocks. I'm not sure if btc1 changed its defaults, but on Bitcoin Core the default blockmaxsize and blockmaxweight values are 750 kB and 3 MB respectively, meaning that if you left your bitcoind to its defaults, your P2Pool node would be mining artificially smaller blocks.

Now that SegWit has been activated, using blockmaxsize=1000000 will prevent your node from ever creating blocks with more than 1 MB of data (including witnesses). The best way to ensure that your node makes the largest possible blocks is to have this in your bitcoin.conf:

Code:

blockmaxweight=4000000

WITHOUT any value for blockmaxsize. Bitcoind will not use the default value for blockmaxsize if a value for blockmaxweight is manually set.

https://github.com/bitcoin/bitcoin/blob/master/src/miner.cpp#L83

P2pool itself also has a 1 MB limit right now. I will need to check whether p2pool itself limits the block stripped size to 1 MB or the block serialized size to 1 MB.

that took care of one warning ... Undecided

Jtoomim is v17 your branch?

The message "Warning: (from bitcoind) Warning: Unknown block versions being mined! It's possible unknown rules are in effect" comes from the bitcoin client you use to run your bitcoin node. It has to do with the signaling by the miners. It's normal behavior.

I currently mine using the merge of forrestv and veqtrus (version 17.0-2-gbc2d09e). I don't get the message "Warning: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION!".