• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

P2Pool So many orphaned blocks as found today have never been

S

sawa

Member
https://github.com/dashpay/p2pool-dash/issues/43


Developers, during the day almost all found blocks is orphaned:

794315 XnwuwfPhuFANd9Bz8fPEt9G3wZSgJS9126 http://crypto.mine.nu:7903/static/c...9f50dd835621237b09c85ced27b452230ab1e4dac19b5
794249 XhstnrgjTeVKWddgPoZZJunAaAeran2QH7 http://crypto.mine.nu:7903/static/c...639ec9f3192d7581d18db6e1f5eadbfccaacbafc8fefd
794042 XcADs7dYBgZwp7GY4r25GV9Bzx6BdVj6DY http://crypto.mine.nu:7903/static/c...af4f43ff173987fde9410fc5f9865f34a5b410ed0f92f
793988 XnwuwfPhuFANd9Bz8fPEt9G3wZSgJS9126 http://crypto.mine.nu:7903/static/c...4dc738858a29f214e24c061f9194bc4eea23e42fb86b5
793913 XhXMahooTgty7jLQAbbRLLHBWeJWy4F1Lv http://crypto.mine.nu:7903/static/c...2b91a259d3cd5af4bba44eacc02aa11bf9ca73c3f9c2b

Maybe we ran into the same problem as the jtoomim fork on the BTC p2pool? Large blocks were rejected.
jtoomim fixed this problem with this patches:
jtoomim/p2pool@b2f6613
jtoomim/p2pool@498bf97


Another orphan. This is uniquely associated with the transition to the latest version of the wallet

10 minutes ago | Thu Dec 28 2017 04:19:23 GMT+0600 | 794391 | 000000000000001760587fc7c94532b8148bd43fe447c711fc75f74439689bbc
 
I think some tech geeks should take a look into it asap - all p2pool nodes generated blocks were rendered useless...seriously I don't want to switch back to nicehash...
 
Ah, hopefully that's the case, and after this series of orphan blocks we won't see any more bad luck at least for next 3 months ;)
 
Seems the situation continues as of now. I have also looked at "antpool" which now has 1PH rate (25-33% of hashrate of entire network) and their blocks found seem normal. I am now a bit worrying if these extremely large pool would finally overtake all smaller pools like p2pool - looks like it is the curse of centralization?
 
We've been following the threads on this topic... Just trying to stay out of the way so that the issue can get resolved.

However, we are getting a lot of pissed off miners o our 7 P2Pool nodes because they are not getting payouts for what appears to be "Found" blocks.

Any updates?
 
Try increasing the number of dashd daemon connections
To increase the connection, you can run the following command in the Linux terminal:
Code: 
dash-cli addnode 82.200.205.30 onetry && \
dash-cli addnode 185.25.60.199 onetry && \
dash-cli addnode 109.87.19.9 onetry && \
dash-cli addnode 108.61.229.222 onetry && \
dash-cli addnode 164.132.200.123 onetry && \
dash-cli addnode 69.162.67.3 onetry && \
dash-cli addnode 76.102.55.12 onetry && \
dash-cli addnode 104.225.220.19 onetry && \
dash-cli addnode 146.66.207.128 onetry && \
dash-cli addnode 93.184.160.140 onetry && \
dash-cli addnode 45.32.154.91 onetry && \
dash-cli addnode 185.60.135.146 onetry && \
dash-cli addnode 91.197.223.88 onetry && \
dash-cli addnode 104.225.217.12 onetry && \
dash-cli addnode 193.169.129.29 onetry && \
dash-cli addnode 185.17.134.38 onetry && \
dash-cli addnode 213.174.7.18 onetry && \
dash-cli addnode 5.9.143.40 onetry && \
dash-cli addnode 95.213.242.194 onetry && \
dash-cli addnode 83.239.114.42 onetry && \
dash-cli addnode 213.170.103.10 onetry && \
dash-cli addnode 18.195.20.0 onetry && \
dash-cli addnode 178.64.174.58 onetry && \
dash-cli addnode 94.242.222.27 onetry && \
dash-cli addnode 27.68.131.10 onetry && \
dash-cli addnode 104.207.156.161 onetry && \
dash-cli addnode 43.229.77.46 onetry && \
dash-cli addnode 88.98.228.14 onetry && \
dash-cli addnode 222.185.244.242 onetry && \
dash-cli addnode 37.29.116.122 onetry && \
dash-cli addnode 46.191.226.84 onetry && \
dash-cli addnode 77.75.14.8 onetry && \
dash-cli addnode 83.143.51.50 onetry && \
dash-cli addnode 94.228.255.132 onetry && \
dash-cli addnode 46.188.44.20 onetry && \
dash-cli addnode 185.136.89.182 onetry && \
dash-cli addnode 62.152.54.44 onetry && \
dash-cli addnode 185.38.163.63 onetry && \
dash-cli addnode 31.131.23.68 onetry && \
dash-cli addnode 95.79.102.209 onetry && \
dash-cli addnode 163.172.216.135 onetry && \
dash-cli addnode 5.19.171.173 onetry && \
dash-cli addnode 194.67.204.96 onetry && \
dash-cli addnode 173.212.233.248 onetry && \
dash-cli addnode 82.117.166.77 onetry && \
dash-cli addnode 213.174.7.26 onetry && \
dash-cli addnode 178.238.236.130 onetry && \
dash-cli addnode 85.192.167.85 onetry && \
dash-cli addnode 83.136.86.133 onetry && \
dash-cli addnode 78.107.58.201 onetry && \
dash-cli addnode 89.223.27.250 onetry && \
dash-cli addnode 85.214.73.33 onetry && \
dash-cli addnode 78.94.185.115 onetry && \
dash-cli addnode 77.249.213.25 onetry && \
dash-cli addnode 90.188.4.86 onetry && \
dash-cli addnode 195.154.39.159 onetry && \
dash-cli addnode 80.64.104.164 onetry && \
dash-cli addnode 188.40.110.58 onetry && \
dash-cli addnode 176.56.24.155 onetry && \
dash-cli addnode 5.134.216.210 onetry && \
dash-cli addnode 78.46.177.112 onetry && \
dash-cli addnode 188.0.182.10 onetry && \
dash-cli addnode 193.108.117.202 onetry && \
dash-cli addnode 31.13.217.61 onetry && \
dash-cli addnode 95.47.137.96 onetry && \
dash-cli addnode 213.110.128.16 onetry && \
dash-cli addnode 185.49.69.160 onetry && \
dash-cli addnode 81.169.139.77 onetry && \
dash-cli addnode 82.199.145.145 onetry && \
dash-cli addnode 5.8.101.60 onetry && \
dash-cli addnode 63.135.175.51 onetry && \
dash-cli addnode 104.207.147.90 onetry && \
dash-cli addnode 62.210.69.84 onetry && \
dash-cli addnode 18.221.229.215 onetry && \
dash-cli addnode 89.212.142.123 onetry && \
dash-cli addnode 94.156.218.28 onetry && \
dash-cli addnode 198.91.88.177 onetry && \
dash-cli addnode 89.191.157.237 onetry && \
dash-cli addnode 85.238.102.203 onetry && \
dash-cli addnode 24.96.71.8 onetry && \
dash-cli addnode 198.40.48.24 onetry && \
dash-cli addnode 194.204.21.105 onetry && \
dash-cli addnode 45.63.7.168 onetry && \
dash-cli addnode 194.186.241.98 onetry && \
dash-cli addnode 81.169.157.154 onetry && \
dash-cli addnode 66.168.24.71 onetry && \
dash-cli addnode 212.58.112.196 onetry && \
dash-cli addnode 173.44.45.108 onetry && \
dash-cli addnode 122.11.58.176 onetry && \
dash-cli addnode 45.32.3.69 onetry && \
dash-cli addnode 186.31.33.251 onetry && \
dash-cli addnode 208.113.166.44 onetry && \
dash-cli addnode 128.199.76.158 onetry && \
dash-cli addnode 100.38.97.189 onetry && \
dash-cli addnode 123.207.101.189 onetry && \
dash-cli addnode 72.74.85.38 onetry && \
dash-cli addnode 97.77.64.18 onetry && \
dash-cli addnode 104.156.229.181 onetry && \
dash-cli addnode 96.231.104.39 onetry && \
dash-cli addnode 208.84.223.121 onetry && \
dash-cli addnode 222.185.244.244 onetry && \
dash-cli addnode 169.239.181.107 onetry && \
dash-cli addnode 154.0.172.35 onetry && \
dash-cli addnode 163.44.193.160 onetry && \
dash-cli addnode 104.238.141.83 onetry && \
dash-cli addnode 103.82.242.56 onetry && \
dash-cli addnode 69.27.173.228 onetry && \
dash-cli addnode 41.87.209.199 onetry && \
dash-cli addnode 175.138.41.27 onetry && \
dash-cli addnode 219.89.81.149 onetry && \
dash-cli addnode 52.67.66.249 onetry && \
dash-cli addnode 67.242.212.128 onetry && \
dash-cli addnode 101.100.174.138 onetry && \
dash-cli addnode 31.13.217.62 onetry && \
dash-cli addnode 84.95.250.20 onetry && \
dash-cli addnode 190.52.135.28 onetry
 
still seeing 9 out of 10 blocks orphaned.... any updates from anyone on this issue being resolved?
 
It seems that the network is divided into 2 segments. In one, the blocks do not linger, but in the other - the brakes. All nodes of the p2pool are in the slow segment.
I do not see a solution to this problem.
We can state the fact: one more p2pool has died.
 
looks like mass pool desertion from the Dash pools on crypto.office-on-the.net.... <10% of payments for 3-4 days is just too much I guess
 
No orphaned blocks for about a week but I think the problem has resurfaced... block no. 801675
Can anyone confirm?
 
You must log in or register to reply here.
Back
Top