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

[Blue Bear]

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

[1714209922]

1714209922

[1714209922]

1714209922

[jtoomim]

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]

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 ... 
Jtoomim is v17 your branch?

[veqtrus]

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.

[jtoomim]

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.

[Cryptonomist]

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

[MrBitter]

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

[Acejam]

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

[Cryptonomist]

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.

[tubexc]

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 ?

[Meuh6879]

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

[Blue Bear]

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

[veqtrus]

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.

[veqtrus]

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

Unless you provide us some details about the software you use we won't be able to help you. OS? From source or not?

[veqtrus]

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

ForrestV talked with me and will be making a release soon.

[Blue Bear]

Unless you provide us some details about the software you use we won't be able to help you. OS? From source or not?

OS is Windows 10 Professional

Downloaded v17 from https://github.com/p2pool/p2pool/tree/17.0

followed directions in readme file to Reset Python27 however was unable to successfully install twisted. (as I said earlier I am not a coder I am a hardware guy) Everything else seemed to install ok.

I also noted that the run_p2pool application file is not present in v17 I am not sure if it is something that came from the v16 sig files but when I try to run the run_p2pool.py file it does nothing ...

Honestly I think I was lucky getting v16 to run.

At first I thought I would be able to replace the v16 files with the new v17 files ... that did not work.

Then I tried to configure from scratch. Still didn't work ... I am missing a step or two some where ...

I went back to the instructions for v16 they seam Identical ...

what steps have  I missed?

[jtoomim]

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 ?

Safer? It depends on how the November fork plays out. It will be safer to use whichever node the other people you want to transact with are using.

btc1 will follow Segwit2x. Bitcoin Core will not.

Currently, 90.9% of the network hashrate is signaling support for Segwit2x (https://coin.dance/blocks). Segwit2x also has the support of Bitpay, Coinbase, and every other major Bitcoin company that has registered an opinion on the matter except for Blockstream. Blockstream, plus a number of smaller companies (Échange de Montréal, Bitbrains, Bitstop) oppose it (https://coin.dance/poli).

Personally, I think Segwit2x will be the dominant chain. The data seem to be in its favor. I could be wrong, though.

The blockchain downloaded by btc1 and Bitcoin Core will be compatible until November. If you want to switch, all you need to do is stop one bitcoind and start the other. After the November fork, though, it will require you to resync your blockchain in order to switch between the two.

veqtrus's code (v17 shares) is incompatible with btc1, and only works with Bitcoin Core. My code will work with either btc1 or Bitcoin Core, though it will give you a warning message if you try to use Core.

[tubexc]

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 ?

Safer? It depends on how the November fork plays out. It will be safer to use whichever node the other people you want to transact with are using.

btc1 will follow Segwit2x. Bitcoin Core will not.

Currently, 90.9% of the network hashrate is signaling support for Segwit2x (https://coin.dance/blocks). Segwit2x also has the support of Bitpay, Coinbase, and every other major Bitcoin company that has registered an opinion on the matter except for Blockstream. Blockstream, plus a number of smaller companies (Échange de Montréal, Bitbrains, Bitstop) oppose it (https://coin.dance/poli).

Personally, I think Segwit2x will be the dominant chain. The data seem to be in its favor. I could be wrong, though.

The blockchain downloaded by btc1 and Bitcoin Core will be compatible until November. If you want to switch, all you need to do is stop one bitcoind and start the other. After the November fork, though, it will require you to resync your blockchain in order to switch between the two.

veqtrus's code (v17 shares) is incompatible with btc1, and only works with Bitcoin Core. My code will work with either btc1 or Bitcoin Core, though it will give you a warning message if you try to use Core.

Thanks.That will help me planing my node creation project although is on a mini laptop.But i hope it works.

[Blue Bear]

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 ?

Safer? It depends on how the November fork plays out. It will be safer to use whichever node the other people you want to transact with are using.

btc1 will follow Segwit2x. Bitcoin Core will not.

Currently, 90.9% of the network hashrate is signaling support for Segwit2x (https://coin.dance/blocks). Segwit2x also has the support of Bitpay, Coinbase, and every other major Bitcoin company that has registered an opinion on the matter except for Blockstream. Blockstream, plus a number of smaller companies (Échange de Montréal, Bitbrains, Bitstop) oppose it (https://coin.dance/poli).

Personally, I think Segwit2x will be the dominant chain. The data seem to be in its favor. I could be wrong, though.

The blockchain downloaded by btc1 and Bitcoin Core will be compatible until November. If you want to switch, all you need to do is stop one bitcoind and start the other. After the November fork, though, it will require you to resync your blockchain in order to switch between the two.

veqtrus's code (v17 shares) is incompatible with btc1, and only works with Bitcoin Core. My code will work with either btc1 or Bitcoin Core, though it will give you a warning message if you try to use Core.

Jtoomim

Respectfully I believe your assumption that support for Segwit2x as the dominate chain is wrong. In slushpool the strongest support goes to Bitcoin with only 10% signaling for for the fork. I don't know but the source you are showing as evidence may only be getting their information from like minded people and not from the community as a whole. As for the exchanges signaling their support , I know that Coinbase was not going to support it to begin with and then rethought it from a economic point of view in that they can make money off of the split from people moving their coin from one branch to another after the split.

I think people are people and will move in their own self interest which is why it has taken so long just to get segwit to activation in the first place. People do not like to feel uncomfortable expressly when their money is involved. The new chain will have to prove itself before people will jump into the pool. Look at how long it took Bitcoin to increase in value over $10.00 per coin. Consider Litecoin, Darkcoin, Dogcoin, Ethereum and all the rest. Ethereum is one of the newest and has been preforming better that Litecoin which has been around longer. What has happened to the others?

I think is a good move on your part to support both sides until you know which way the coin will land. I believe you may have blinders on though.

Respectfully,

BB

 

[veqtrus]

Unless you provide us some details about the software you use we won't be able to help you. OS? From source or not?

OS is Windows 10 Professional

Downloaded v17 from https://github.com/p2pool/p2pool/tree/17.0

followed directions in readme file to Reset Python27 however was unable to successfully install twisted. (as I said earlier I am not a coder I am a hardware guy) Everything else seemed to install ok.

I also noted that the run_p2pool application file is not present in v17 I am not sure if it is something that came from the v16 sig files but when I try to run the run_p2pool.py file it does nothing ...

Honestly I think I was lucky getting v16 to run.

At first I thought I would be able to replace the v16 files with the new v17 files ... that did not work.

Then I tried to configure from scratch. Still didn't work ... I am missing a step or two some where ...

I went back to the instructions for v16 they seam Identical ...

what steps have  I missed?

I wrote a guide for vtc but it may help you with btc too if you want to run from source. Also use the master branch which includes a necessary commit.