[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[sawa]

Located in Moscow, Russian Federation

Hello, keke51. If you are from Russia, then there is a Russian-language forum. Starting from this message https://forum.bits.media/index.php?/topic/253-p2pool-detcentralizovannyi-pul/?p=700166 and further, the people gave a lot of tips on setting up the jtoomim's forked node.

[sawa]

To those who mines on my crypto.office-on-the.net: https://bitcointalk.org/index.php?topic=852083.msg18912707#msg18912707

[in2tactics]

To those who mines on my crypto.office-on-the.net: https://bitcointalk.org/index.php?topic=852083.msg18912707#msg18912707

Wow, you run a lot of nodes.

[m_a17]

https://blockchain.info/ru/block-index/1500822
Block fork .
Size   999.597 KB
Transaction Fees   1.86340041 BTC
 

[flameruk]

Located in Moscow, Russian Federation

Hello, keke51. If you are from Russia, then there is a Russian-language forum. Starting from this message https://forum.bits.media/index.php?/topic/253-p2pool-detcentralizovannyi-pul/?p=700166 and further, the people gave a lot of tips on setting up the jtoomim's forked node.

Anything around in English?
Ive got the jtoomim fork running keeps saying "downloading shares" but it goes no further.
Seems to only connect to 2 X other nodes.
Fell to sleep at the laptop the other night and still the same 7 hours later.
Not sure what im doing wrong here, the main chain is chugging away nicely.

When I originally loaded the main chain it says "processing xx shares" etc but dont get that far with the fork.
Any ideas, I want in real bad?

[jtoomim]

Ive got the jtoomim fork running keeps saying "downloading shares" but it goes no further.
Fell to sleep at the laptop the other night and still the same 7 hours later.

Email your p2pool/data/bitcoin/log file to (edit: email redacted because of spam).

Also, if anyone is having trouble connecting and doesn't mind giving me ssh access, I would like to be able to investigate these issues further. I've heard several reports from other people of having trouble downloading shares, but I've not yet been able to reproduce the issue myself.

[flameruk]

Ive got the jtoomim fork running keeps saying "downloading shares" but it goes no further.
Fell to sleep at the laptop the other night and still the same 7 hours later.

Email your p2pool/data/bitcoin/log file to j at toom dot im.

Also, if anyone is having trouble connecting and doesn't mind giving me ssh access, I would like to be able to investigate these issues further. I've heard several reports from other people of having trouble downloading shares, but I've not yet been able to reproduce the issue myself.

Cool. I'll re git clone it in the morning (UK) and give you ssh access.
I've got to finish off some embedded code for a work job tonight as I spent far to much time trying to get the fork working over the weekend.
Thanks for this sir.

[sawa]

Hello, jtoomim. We have a problem and it is not solved https://bitcointalk.org/index.php?topic=18313.msg18844122#msg18844122
Currently, most nodes have already rolled back the commit, cd0b24abd68467b0752eced317690cc3e388f9eb, to prevent synchronization loops. With this commit, the node periodically goes into an infinite loop, until it is restarted. To restart the node, I needed to kill the p2pool process, since it did not even react to CTRL+C

[Dropwise]

Why has block https://blockchain.info/block-height/465654 not paid out?

[windpath]

Why has block https://blockchain.info/block-height/465654 not paid out?

It has, it was found by jtoomims fork, not the main P2Pool chain.

[Dropwise]

Oh thank you for clarifying. I was unaware of the fork. Can someone kindly direct me to a setup guide for configuring a jtoomims p2pool node? I'm struggling to find this.

[notabeliever]

Oh thank you for clarifying. I was unaware of the fork. Can someone kindly direct me to a setup guide for configuring a jtoomims p2pool node? I'm struggling to find this.

look at the threads above #15322 and   #15328

https://bitcointalk.org/index.php?topic=18313

[-ck]

May I suggest that if forrestv does not approve of jtoomim's fork and include the code in the main repository that a new thread be created for the alternative fork out of respect for the original thread and pool? Alternatively, if forrestv is happy for the jtoomim fork to be the main pool and take over management of the p2pool concept entirely this should also run in its own thread such that jtoomim can be the opening poster where announces/changes can be documented.

[flameruk]

Ive got the jtoomim fork running keeps saying "downloading shares" but it goes no further.
Fell to sleep at the laptop the other night and still the same 7 hours later.

Email your p2pool/data/bitcoin/log file to j at toom dot im.

Also, if anyone is having trouble connecting and doesn't mind giving me ssh access, I would like to be able to investigate these issues further. I've heard several reports from other people of having trouble downloading shares, but I've not yet been able to reproduce the issue myself.

OK so I went onto the Russian "how to".
I cant read a word of Russian but can understand the code.

I used this :-

git clone -b 1mb_hardforked https://github.com/jtoomim/p2pool.git p2pool

And now im working. Must have been trying the Git Clone wrong.
Ill let this run, its downloading and processing the share chain and see what happens.

[mad3]

Any ideas why my backup pool has different numbers for everything?  And why did the backup pool output 2 different lines with "New work?"  The second line has the same share difficulty as my main instance, but the difficulty, block value and number of transactions aren't the same.  Both nodes to show the same number of shares in the chain and the same pool hash rate and stale rate.

[in2tactics]

Any ideas why my backup pool has different numbers for everything?  And why did the backup pool output 2 different lines with "New work?"  The second line has the same share difficulty as my main instance, but the difficulty, block value and number of transactions aren't the same.  Both nodes to show the same number of shares in the chain and the same pool hash rate and stale rate.

We need to know which two pools you are referring to.

[jtoomim]

Hello, jtoomim. We have a problem and it is not solved https://bitcointalk.org/index.php?topic=18313.msg18844122#msg18844122
Currently, most nodes have already rolled back the commit, cd0b24abd68467b0752eced317690cc3e388f9eb, to prevent synchronization loops. With this commit, the node periodically goes into an infinite loop, until it is restarted. To restart the node, I needed to kill the p2pool process, since it did not even react to CTRL+C

Thanks for the info. It does seem that there may be something wrong with that commit. It's a pretty important commit, though. Without it, in my early testing, I was getting about 60% of my shares orphaned due to transmission failures. I think that orphan rate mostly applies to the first share after a new block, so the orphan rate is likely to be lower in a production environment. However, it will still cost you money if you try to run completely without it.

The purpose of that commit was to fix a problem in which transaction hashes that were part of a stratum job could not be dereferenced into full transactions for share propagation. To fix it, that commit does a few things:

1. It keeps a separate record of transactions that were most recently received by bitcoind in a getblocktemplate vs. transactions that were most recently handed out to miners.
2. It uses a Python namespace hack to keep the transactions in memory in a separate variable in case #1 above doesn't work
3. If share transmission doesn't work due to missing transactions, it queues additional attempts with a delay.

It looks like the problem was with the share retransmission logic (#3). I don't think the retransmission logic is necessary any more, so I made a branch that excludes just that part and see if it fixes the problems that people have been having. I'm testing it now. Looks good so far; I'll post again once testing is finished.

[jtoomim]

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:

Code:

git clone https://github.com/jtoomim/p2pool
cd p2pool
git checkout 1mb_hardforked

If anyone continues to have trouble connecting to jtoomimnet, please let me know.

[pashecf]

2017-05-10 20:50:20.355000 P2Pool: 0 shares in chain (0 verified/8607 total) Peers: 6 (0 incoming)
2017-05-10 20:50:20.355000  Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:
2017-05-10 20:50:23.507000 Processing 57 shares from 208.84.223.121:9333...
2017-05-10 20:50:23.507000 > Share check failed: 0000000000000024677fb883b7adf4d0005b9de313b8d5a6a7f305047533bff5 -> 00000000000000d388b15e1aca14c569e6d6a2b748469a847ea10c167a05ba96
2017-05-10 20:50:23.522000 > Traceback (most recent call last):
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 134, in download_shares
2017-05-10 20:50:23.522000 >     self.handle_shares([(share, []) for share in shares], peer)
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 47, in handle_shares
2017-05-10 20:50:23.522000 >     self.node.set_best_share()
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 293, in set_best_share
2017-05-10 20:50:23.522000 >     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)
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 486, in think
2017-05-10 20:50:23.538000 >     if self.attempt_verify(share):
2017-05-10 20:50:23.538000 > --- <exception caught here> ---
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 464, in attempt_verify
2017-05-10 20:50:23.538000 >     share.check(self)
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 323, in check
2017-05-10 20:50:23.553000 >     if self.timestamp > int(time.mktime(time.gmtime()) - time.mktime(time.gmtime(0))) + 300:
2017-05-10 20:50:23.553000 > exceptions.OverflowError: mktime argument out of range
2017-05-10 20:50:23.553000 > Share check failed: 00000000000000d388b15e1aca14c569e6d6a2b748469a847ea10c167a05ba96 -> 000000000000001d67b2dbc2e3979ece6983117c25d8041e61f69d810f784d2e
2017-05-10 20:50:23.553000 > Traceback (most recent call last):
2017-05-10 20:50:23.553000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 134, in download_shares
2017-05-10 20:50:23.553000 >     self.handle_shares([(share, []) for share in shares], peer)
2017-05-10 20:50:23.553000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 47, in handle_shares
2017-05-10 20:50:23.569000 >     self.node.set_best_share()
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 293, in set_best_share
2017-05-10 20:50:23.569000 >     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)
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 486, in think
2017-05-10 20:50:23.569000 >     if self.attempt_verify(share):
2017-05-10 20:50:23.569000 > --- <exception caught here> ---
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 464, in attempt_verify
2017-05-10 20:50:23.585000 >     share.check(self)
2017-05-10 20:50:23.585000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 323, in check
2017-05-10 20:50:23.585000 >     if self.timestamp > int(time.mktime(time.gmtime()) - time.mktime(time.gmtime(0))) + 300:
2017-05-10 20:50:23.585000 > exceptions.OverflowError: mktime argument out of range

[jtoomim]

I haven't tested on Windows before. That looks like it might be a Windows-specific error. I'll see if I can reproduce it.