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

veqtrus

member

Activity: 107

Merit: 10

Quote from: tubexc on August 25, 2017, 10:22:43 AM

Hello and good afternoon to all p2poolers !
Just some illuminating questions :
Is btc1 wallet safer than btc core wallet for running a p2pool node (anti fraud or something) ?
I will be forced to synchronize everything again to the btc1 wallet ?

You do seem like you don't know what you are doing.

Blue Bear

newbie

Activity: 31

Merit: 0

Quote from: Cryptonomist on August 25, 2017, 04:46:24 AM

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!".

Ok I figured out the problem ...

I have not upgraded to v17 ... I am still running v16.

I have beat my head against the wall trying to get v17 to work

I would welcome any help you coders can provide to a poor hardware guy ...

thought it would be a simple cut and paste of the new files ...

what I get for thinking I guess ....

Meuh6879

legendary

Activity: 1512

Merit: 1012

Can someone push a binary on the main page ? >>> http://p2pool.in/

tubexc

hero member

Activity: 496

Merit: 500

Hello and good afternoon to all p2poolers !
Just some illuminating questions :
Is btc1 wallet safer than btc core wallet for running a p2pool node (anti fraud or something) ?
I will be forced to synchronize everything again to the btc1 wallet ?

Cryptonomist

newbie

Activity: 27

Merit: 0

Quote from: MrBitter on August 25, 2017, 08:20:38 AM

can I run p2pool in the background, if yes then how? (Linux version)
Have user interface?

I suppose you want to run the process without the need to keep open the terminal? In that case you can use "screen". For example "screen -d -m -S p2pool ~/p2pool/run_p2pool.py". This will run the process in a seperate screen with the name p2pool. You can switch to the screen by using "screen -r p2pool", and detach from it using first Ctrl + A and subsequently Ctrl + D. Don't use Ctrl + C when you have retached the screen because that will terminate the process.

If you want a GUI or so, I don't think there is one (I might be wrong. I run mine on Ubuntu Server so I only use command line). If you want statistics of your miners and stuff like that, you can get those from within your browser by going to http://(ip adress of node on local network):9332/. More info can be found on http://p2pool.in/

I hope this answers your question.

Acejam

full member

Activity: 124

Merit: 251

The p2pool cluster at p2pool.io has been updated to support v17 shares.

MrBitter

sr. member

Activity: 255

Merit: 250

can I run p2pool in the background, if yes then how? (Linux version)
Have user interface?

Cryptonomist

newbie

Activity: 27

Merit: 0

Quote from: Blue Bear on August 24, 2017, 11:59:07 PM

Quote from: jtoomim on August 24, 2017, 11:35:34 PM

Quote from: frodocooper on August 19, 2017, 06: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!".

jtoomim

hero member

Activity: 818

Merit: 1006

No, Blue Bear, v17 is veqtrus's code. My code is v33. It's on a completely separate and independent share chain, so you won't see v33 shares unless you're using my code.

veqtrus

member

Activity: 107

Merit: 10

Quote from: jtoomim on August 24, 2017, 11:35:34 PM

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.

If you bothered to properly review my code you would know I fixed it.

Blue Bear

newbie

Activity: 31

Merit: 0

Quote from: jtoomim on August 24, 2017, 11:35:34 PM

Quote from: frodocooper on August 19, 2017, 06: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?

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: frodocooper on August 19, 2017, 06: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.

Blue Bear

newbie

Activity: 31

Merit: 0

Quote from: Blue Bear on August 24, 2017, 10:22:53 PM

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.
[/quote]

well did some more digging at found v17 from forrestv and implemented it still getting the warnings ... Sad

Blue Bear

newbie

Activity: 31

Merit: 0

[/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.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Blue Bear on August 24, 2017, 09:10:22 PM

...
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

newbie

Activity: 31

Merit: 0

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?

frodocooper

sr. member

Activity: 351

Merit: 410

Quote from: jtoomim on August 24, 2017, 12:59:53 AM

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.

jtoomim

hero member

Activity: 818

Merit: 1006

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

sr. member

Activity: 351

Merit: 410

Quote from: jtoomim on August 23, 2017, 07:48:42 PM

... 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

hero member

Activity: 818

Merit: 1006

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.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 28. (Read 2591916 times)