Bitcoin Forum
September 23, 2017, 07:19:03 AM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
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 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2463029 times)
jtoomim
Hero Member
*****
Offline Offline

Activity: 730


View Profile WWW
August 20, 2017, 01:50:27 AM
 #15721

I'm working on adding fork-friendliness to p2pool now. It's a bit more complicated than I thought at first. You can't just check to see if a share's parentblock is in bitcoind's blockchain and mark the share invalid if not, because orphaned blocks are a thing. Instead, I will be trying to keep a penalty score for each share, where each share's penalty is the previous share's penalty plus 0 if the parentblock is found in the blockchain else the work done if the parentblock is not in the blockchain (i.e. orphan or invalid). P2pool will then look for the share with the greatest (work - penalty). That description is slightly oversimplified, but I hope it gets the main idea across.

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

Posts: 1506151143

View Profile Personal Message (Offline)

Ignore
1506151143
Reply with quote  #2

1506151143
Report to moderator
1506151143
Hero Member
*
Offline Offline

Posts: 1506151143

View Profile Personal Message (Offline)

Ignore
1506151143
Reply with quote  #2

1506151143
Report to moderator
1506151143
Hero Member
*
Offline Offline

Posts: 1506151143

View Profile Personal Message (Offline)

Ignore
1506151143
Reply with quote  #2

1506151143
Report to moderator
Be very wary of relying on JavaScript for security on sites such as blockchain.info and brainwallet.org. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1506151143
Hero Member
*
Offline Offline

Posts: 1506151143

View Profile Personal Message (Offline)

Ignore
1506151143
Reply with quote  #2

1506151143
Report to moderator
jtoomim
Hero Member
*****
Offline Offline

Activity: 730


View Profile WWW
August 20, 2017, 09:06:35 AM
 #15722

I will be upgrading all of my nodes to 1mb_segwit tomorrow. I suggest that anyone mining on jtoomimnet switch to the 1mb_segwit branch ASAP.

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

Activity: 4


View Profile
August 20, 2017, 11:55:47 AM
 #15723

Dear community! And esp MR Jtoomim!
I bet i'm not alone in willing to have a BCH (or BCC) sort of fork of P2pool. Is it real? I am not a coding person, but BCH is not far from the original BTC and maybe it is not so big work to do?
dimkov
Jr. Member
*
Offline Offline

Activity: 41


View Profile
August 20, 2017, 12:12:54 PM
 #15724

Dear community! And esp MR Jtoomim!
I bet i'm not alone in willing to have a BCH (or BCC) sort of fork of P2pool. Is it real? I am not a coding person, but BCH is not far from the original BTC and maybe it is not so big work to do?
Join in the keke51. The complexity of the network BCH falls, the price increases. Ideal conditions for mining BCH. Really need P2pool BCH.
Cryptonomist
Newbie
*
Offline Offline

Activity: 18


View Profile
August 20, 2017, 02:53:37 PM
 #15725


Ok, thank you. This solved the problem.

I've got another question about p2pool. I'm fairly new to mining using p2pool, so the current situation with the different forks is a bit confusing. As I understand it from the posts on this forum and the output of jtoomim's 1mb_segwit p2pool, jtoomim's fork follows segwit2x, which will be a hardfork of the bitcoin blockchain in november. I'm in favor of segwit but not of segwit2x. So I would rather not mine on a p2pool fork that supports segwit2x. As I understand it the current version of forrestv p2pool's does not support segwit. That's the version I use currently for mining. However I see that veqtrus wrote a commit that supports segwit but not segwit2x. So my question is the folowing. Is there a plan in the foreseeable future to merge forrestv's version and veqtrus's commit, so that I just need to do a git pull to have a a p2pool version that supports segwit?  Or, is forrestv's version going to merge with jtoomim's version, so that I will be forced to chose for segwit2x anyway?

Thank you.
jtoomim
Hero Member
*****
Offline Offline

Activity: 730


View Profile WWW
August 20, 2017, 07:27:50 PM
 #15726

jtoomimnet (via the 1mb_segwit branch) follows segwit for the next two months. I am working on code that will make jtoomimnet split into a segwit chain and a segwit2x chain automatically once the fork happens. This code will also be required for supporting Bitcoin Cash, which is my immediate goal.

Supporting Bitcoin Cash is likely to require some p2pool performance improvements as well, as the current codebase struggles with 1MB blocks, much less 8MB. I hope to have Bitcoin Cash working by the end of the weekend as long as you have a high-end server. I'll try to get the needed performance improvements afterwards.

Quote
I will be forced to chose for segwit2x anyway?
It is not my goal to force anyone to do anything. As long as you are aware of the risks of mining on a minority chain, you are welcome to do so. I don't want people to mine on the minority chain due to ignorance, but as long as people know what they're doing, it's fine with me.

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

Activity: 33


View Profile
August 20, 2017, 07:31:24 PM
 #15727

isent it posible to compile an P2Pool exe File for windows ?  Huh
jtoomim
Hero Member
*****
Offline Offline

Activity: 730


View Profile WWW
August 20, 2017, 07:55:12 PM
 #15728

Not with pypy. Until I get the performance good enough so that regular CPython will work for p2pool without high DOA rates on common CPUs, pypy will be necessary, and making EXEs will not be a good idea.

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

Activity: 730


View Profile WWW
August 20, 2017, 10:09:46 PM
 #15729

Sigh, more p2pool drama between me and veqtrus:

https://www.reddit.com/r/Bitcoin/comments/6uweb7/p2pool_upgrade_for_segwit_compatibility/

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

Activity: 730


View Profile WWW
August 21, 2017, 09:44:13 PM
 #15730

I goofed and set one of my nodes' bitcoinds to prune its blockchain. Apparently p2pool requires that the genesis block be unpruned, and will fail to start if pruning is enabled. Oops. ml.toom.im:9334 will be down for a couple more hours as I resync the blockchain. It's up to block 415543 so far, so it shouldn't be too much longer. If anyone was mining onto ml.toom.im:9334, sorry.

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

Activity: 730


View Profile WWW
August 22, 2017, 12:36:22 AM
 #15731

Support for v33 (Segwit) shares on jtoomimnet is at around 97% over the last few hours. Anyone still in the 3% who hasn't upgraded will be forked off very soon.

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

Activity: 107


View Profile WWW
August 23, 2017, 06:50:29 AM
 #15732

People who do not want to use jtoomimnet should use the segwit PR against the main repo as segwit will activate in less than a day.

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

ForrestV seems to be inactive.

P2Pool donation button | Bitrated user: veqtrus.
Cluster2k
Legendary
*
Offline Offline

Activity: 1556


View Profile
August 23, 2017, 11:50:34 AM
 #15733

Node address (Original code): http://btc.coinpool.pw:9332
Node address (Forked code): http://btc-fork.coinpool.pw:9334

To connect to me: run_p2pool.py -n btc-fork.coinpool.pw:9335
CPU: i7-3770 @ 3.40GHz
RAM: 16GB
Pipe: 1Gbit Hetzner Germany, DC#19
Using: Pypy 5.7.1 @ Ubuntu 16.04

Both nodes has integrated pull request with adaptive variable difficulty so are suitable for mining by many different ASICs at one time.

Also i've implemented scanner for public P2Pool nodes (both original and forked ones!) at https://p2pool.coinpool.pw/

I recommend using this pool, the guy is very skilled and honest.

Do not send bitcoins to me: 16b8s7pBJ9rUmsExNW25qD5VUqVqRPZuXu
100% solar powered bitcoin generation
sawa
Legendary
*
Offline Offline

Activity: 1024



View Profile
August 23, 2017, 01:30:25 PM
 #15734

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

veqtrus
Member
**
Offline Offline

Activity: 107


View Profile WWW
August 23, 2017, 01:42:56 PM
 #15735

Bitcoin Core 0.13.1+ will do.

P2Pool donation button | Bitrated user: veqtrus.
Comandante77
Newbie
*
Offline Offline

Activity: 11


View Profile
August 23, 2017, 02:53:40 PM
 #15736

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

Activity: 107


View Profile WWW
August 23, 2017, 03:22:24 PM
 #15737

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.

P2Pool donation button | Bitrated user: veqtrus.
Comandante77
Newbie
*
Offline Offline

Activity: 11


View Profile
August 23, 2017, 03:56:31 PM
 #15738

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

Activity: 730


View Profile WWW
August 23, 2017, 06:55:08 PM
 #15739

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

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

Activity: 730


View Profile WWW
August 23, 2017, 07:15:29 PM
 #15740

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

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
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 »
  Print  
 
Jump to:  

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!