Bitcoin Forum
January 20, 2019, 02:02:08 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 [787] 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2567595 times)
jtoomim
Hero Member
*****
Offline Offline

Activity: 818
Merit: 1001


View Profile WWW
August 23, 2017, 11:46:40 PM
Last edit: August 24, 2017, 12:43:39 AM by jtoomim
 #15721

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
1547949728
Hero Member
*
Offline Offline

Posts: 1547949728

View Profile Personal Message (Offline)

Ignore
1547949728
Reply with quote  #2

1547949728
Report to moderator
1547949728
Hero Member
*
Offline Offline

Posts: 1547949728

View Profile Personal Message (Offline)

Ignore
1547949728
Reply with quote  #2

1547949728
Report to moderator
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1547949728
Hero Member
*
Offline Offline

Posts: 1547949728

View Profile Personal Message (Offline)

Ignore
1547949728
Reply with quote  #2

1547949728
Report to moderator
Comandante77
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
August 24, 2017, 12:14:06 AM
 #15722

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
Hero Member
*****
Offline Offline

Activity: 818
Merit: 1001


View Profile WWW
August 24, 2017, 12:48:42 AM
Last edit: August 24, 2017, 01:42:38 AM by jtoomim
 #15723

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
jtoomim
Hero Member
*****
Offline Offline

Activity: 818
Merit: 1001


View Profile WWW
August 24, 2017, 01:56:47 AM
 #15724

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
frodocooper
Moderator
Sr. Member
*
Offline Offline

Activity: 320
Merit: 320


View Profile
August 24, 2017, 04:40:10 AM
Last edit: August 24, 2017, 06:12:26 AM by frodocooper
 #15725

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

Activity: 818
Merit: 1001


View Profile WWW
August 24, 2017, 05:59:53 AM
 #15726

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
frodocooper
Moderator
Sr. Member
*
Offline Offline

Activity: 320
Merit: 320


View Profile
August 24, 2017, 06:18:31 AM
 #15727

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
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
August 25, 2017, 02:10:22 AM
 #15728


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
Legendary
*
Offline Offline

Activity: 2702
Merit: 1068


Linux since 1997 RedHat 4


View Profile
August 25, 2017, 02:19:59 AM
 #15729

...
Would anyone care to enlighten me as to why I am getting these warnings?
Read just about any post in the last 2 pages?

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
Blue Bear
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
August 25, 2017, 03:22:53 AM
 #15730


[/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.
Blue Bear
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
August 25, 2017, 04:13:51 AM
 #15731


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
jtoomim
Hero Member
*****
Offline Offline

Activity: 818
Merit: 1001


View Profile WWW
August 25, 2017, 04:35:34 AM
 #15732

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Blue Bear
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
August 25, 2017, 04:59:07 AM
 #15733

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?
veqtrus
Member
**
Offline Offline

Activity: 107
Merit: 10


View Profile WWW
August 25, 2017, 06:01:46 AM
 #15734

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.

P2Pool donation button | Bitrated user: veqtrus.
jtoomim
Hero Member
*****
Offline Offline

Activity: 818
Merit: 1001


View Profile WWW
August 25, 2017, 09:45:11 AM
 #15735

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.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Cryptonomist
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
August 25, 2017, 09:46:24 AM
 #15736

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





MrBitter
Sr. Member
****
Offline Offline

Activity: 256
Merit: 250



View Profile
August 25, 2017, 01:20:38 PM
 #15737

can I run p2pool in the background, if yes then how? (Linux version)
Have user interface?
Acejam
Sr. Member
****
Offline Offline

Activity: 257
Merit: 251


View Profile
August 25, 2017, 02:01:24 PM
 #15738

The p2pool cluster at p2pool.io has been updated to support v17 shares.
Cryptonomist
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
August 25, 2017, 02:02:45 PM
 #15739

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
Hero Member
*****
Offline Offline

Activity: 501
Merit: 500


View Profile
August 25, 2017, 03:22:43 PM
 #15740

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 ?
Pages: « 1 ... 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 [787] 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!