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

[GUIDE]Updating Darkcoind / P2Pool After Reverting RC3 Masternode Payments Fork June 21st

Looks like my pool, and most others are now showing the latest p2pool block found (as shown by the node scanner) 90075.

The idea of adding nodes which we know are on the correct fork sounds like a good idea. But not a solution as it could connect to some "bad" p2pool / nodes also..
 
mattmct said:
Surely a new version of the p2pool is needed, which only connects to other p2pools which are running the latest software, with the latest darkcoind on the correct fork.

It's crazy that we can be running the latest darkcoind on the correct fork, redindexed etc, but still getting the wrong chain because we're connecting to messed up nodes with the wrong fork.
Click to expand...
It is the p2pool sharechain that is forked, not blockchain. The other pools can't affect your blockchain. Everything will be fine as long as most pools are on the correct sharechain. We will just get some errors in the logfile and the global hashrate will be lower.
 
Posted this on bitcointalk

The following p2pools are on the wrong share-chain. There are probably more pools that I have not found yet.

http://69.164.207.41:7903/static/
http://64.231.8.35:7903/static/
http://62.210.178.13:7903/static/
http://109.74.203.79:7903/static/
http://95.85.9.5:7903/static/
http://23.92.31.161:7903/static/
http://212.83.168.86:7903/static/
http://5.135.161.150:7903/static/
http://192.99.3.15:7903/static/
https://www.crypthash.fr/p2p_dark/static/
http://202.171.65.10:7903/static/
http://p2poolcoin.com:7903/static/
http://ca.p2poolcoin.com:7903/static/
http://85.25.194.238:7903/static/
http://157.56.161.215:7903/static/
http://p2pool.e-pool.net:7903/static/
http://drk.mynetfixes.com:7903/static/
http://p2phash.com:7903/static/

You need to update the wallet and p2pool code. Delete the "data" directory and restart the pool to get the correct chain.
 
dstorm said:
You need to update the wallet and p2pool code. Delete the "data" directory and restart the pool to get the correct chain.
Click to expand...

I have update the wallet and it would seem that I am on the correct chain, what change to the code do I have do to in thecode of my P2Pool please?

Thanks!
 
fabioganga said:
I have update the wallet and it would seem that I am on the correct chain, what change to the code do I have do to in thecode of my P2Pool please?

Thanks!
Click to expand...
If you have block 92131 in the "recent blocks" list you don't need to do anything.
 
I am having gentx errors again since the sporck. Do others have similar problems? Or a solution maybe?
I am running latest darkcoind (91105) and latest p2pool (fac408d-dirty). /data was deleted and a --reindex was done.
Any held is appreciated as these errors seems to have a negative impact on p2pool efficiency.
 
fydel said:
I am having gentx errors again since the sporck. Do others have similar problems? Or a solution maybe?
I am running latest darkcoind (91105) and latest p2pool (fac408d-dirty). /data was deleted and a --reindex was done.
Any held is appreciated as these errors seems to have a negative impact on p2pool efficiency.
Click to expand...
I have same issue on my pool :(
Using latest darkcoind and p2pool (fac408d-dirty) too.
Code: 
2014-07-03 18:09:37.667014 Requesting parent share bfee4f13 from 23.239.28.247:42400
2014-07-03 18:09:37.889686 > Share check failed: 0000000066f7d0dab55a481c0cdcd9e16c46341701674c70c11e5a127f461073 -> 00000005b0bd4546bc6bf954250f776234be65ca4722507cde8791b8d3b2cbf6
2014-07-03 18:09:37.889763 > Traceback (most recent call last):
2014-07-03 18:09:37.889795 >  File "/home/penambang/p2p-drk-new/p2pool/p2p.py", line 282, in handle_shares
2014-07-03 18:09:37.889821 >  self.node.handle_shares(result, self)
2014-07-03 18:09:37.889846 >  File "/home/penambang/p2p-drk-new/p2pool/node.py", line 48, in handle_shares
2014-07-03 18:09:37.889870 >  self.node.set_best_share()
2014-07-03 18:09:37.889894 >  File "/home/penambang/p2p-drk-new/p2pool/node.py", line 299, in set_best_share
2014-07-03 18:09:37.889919 >  best, desired, decorated_heads, bad_peer_addresses = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-07-03 18:09:37.889959 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 506, in think
2014-07-03 18:09:37.889984 >  if not self.attempt_verify(share):
2014-07-03 18:09:37.890008 > --- <exception caught here> ---
2014-07-03 18:09:37.890031 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 450, in attempt_verify
2014-07-03 18:09:37.890056 >  share.check(self)
2014-07-03 18:09:37.890080 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 335, in check
2014-07-03 18:09:37.890104 >  raise ValueError('''gentx doesn't match hash_link''')
 
Last edited by a moderator:
Thank you for the info.
The errors are gone after updating to darkcoind 91106 today. I assume that the latest dnsseeder update makes sure that darkcoind is only connected to valid nodes. Resulting in no more gentx errors. Nice. :smile:
 
fydel said:
Thank you for the info.
The errors are gone after updating to darkcoind 91106 today. I assume that the latest dnsseeder update makes sure that darkcoind is only connected to valid nodes. Resulting in no more gentx errors. Nice. :smile:
Click to expand...

06? New version, sayyy whattt?! Nice! I'll update
 
You must log in or register to reply here.
Back
Top