Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
https://github.com/jtoomim/p2pool/tree/1mb_hardforked has new code. This should fix the sync issues that people have been having. It also includes a few bootstrap nodes to make it easier for people to connect to the jtoomimnet p2pool.
To set up and run my fork, you will need to do the regular steps for installing p2pool, except that instead of getting the regular github.com/p2pool/p2pool repository, you will do:
If anyone continues to have trouble connecting to jtoomimnet, please let me know.
To set up and run my fork, you will need to do the regular steps for installing p2pool, except that instead of getting the regular github.com/p2pool/p2pool repository, you will do:
Code:
git clone https://github.com/jtoomim/p2pool
cd p2pool
git checkout 1mb_hardforked
cd p2pool
git checkout 1mb_hardforked
If anyone continues to have trouble connecting to jtoomimnet, please let me know.
Hi jtoomim.
This new code sorted out all my problems!
I cloned it this morning, left it running while Ive been out on a job and just now pointed my miners at it.
Seems to have resolved all the previous problems I was having.
Im getting this now
Code:
Warning: Previous share's timestamp is 3615 seconds old.
2017-05-11 15:16:05.873198 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-11 15:16:05.873262 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-11 15:16:05.873321 (It's also possible that this share is just taking a long time to mine.)
2017-05-11 15:16:06.170906 Generating a share with 748972 bytes (2821 new) and 1701 transactions (12 new)
2017-05-11 15:16:06.172997 Warning: Previous share's timestamp is 3616 seconds old.
2017-05-11 15:16:06.173097 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-11 15:16:06.173161 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-11 15:16:06.173219 (It's also possible that this share is just taking a long time to mine.)
2017-05-11 15:16:05.873198 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-11 15:16:05.873262 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-11 15:16:05.873321 (It's also possible that this share is just taking a long time to mine.)
2017-05-11 15:16:06.170906 Generating a share with 748972 bytes (2821 new) and 1701 transactions (12 new)
2017-05-11 15:16:06.172997 Warning: Previous share's timestamp is 3616 seconds old.
2017-05-11 15:16:06.173097 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-11 15:16:06.173161 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-11 15:16:06.173219 (It's also possible that this share is just taking a long time to mine.)
My NTP is working any ideas?
