Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 49. (Read 2591916 times)
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.
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://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313
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.
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.
Why has block https://blockchain.info/block-height/465654 not paid out?
Hello, jtoomim. We have a problem and it is not solved https://bitcointalksearch.org/topic/m.18844122
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
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
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.Fell to sleep at the laptop the other night and still the same 7 hours later.
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.
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).Fell to sleep at the laptop the other night and still the same 7 hours later.
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.
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.
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?
https://blockchain.info/ru/block-index/1500822
Block fork .
Size 999.597 KB
Transaction Fees 1.86340041 BTC
Block fork .
Size 999.597 KB
Transaction Fees 1.86340041 BTC
To those who mines on my crypto.office-on-the.net: https://bitcointalksearch.org/topic/m.18912707
Wow, you run a lot of nodes. 
To those who mines on my crypto.office-on-the.net: https://bitcointalksearch.org/topic/m.18912707
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.
Thank you very much, I bet Im loading shares. So:
Node IP - 141.136.115.230:9333 (standart port, 9332 - worker port)
Gear: macmini 2012 (i5 2.4ghz) MacOS:)
Located in Moscow, Russian Federation
Connected to ml.toom.im:9333
Pipe - 40mbs wire
to connect to me use run_p2pool.py -n 141.136.115.230:9333
Node IP - 141.136.115.230:9333 (standart port, 9332 - worker port)
Gear: macmini 2012 (i5 2.4ghz) MacOS:)
Located in Moscow, Russian Federation
Connected to ml.toom.im:9333
Pipe - 40mbs wire
to connect to me use run_p2pool.py -n 141.136.115.230:9333
Dear PROs, can someone post an instruction on how to start jtoomims forked node. I cloned one from github, run it - and it keeps saying "Unknown share type 16"
I got usual p2pool node on that machine and it worked fine.
I got usual p2pool node on that machine and it worked fine.
Hello, keke51. You need to connect your node to one of the jtoomimnet nodes, using the "-n [url:port]" command-line option. jtoomimnet's sharechain is incompatible with mainnet's sharechain, which is why you're getting the "Unknown share type 16" error. jtoomimnet's protocol version number is 32; mainnet's is 16.
For example, here are instructions for connecting your node to jtoomim's node, among others:
...
To connect to me: run_p2pool.py -n ml.toom.im:9333
...
To connect to me: run_p2pool.py -n ml.toom.im:9333
...
You are also encouraged to publicly share your node details here, once you've set up your node. It would go a long way in helping jtoomim with the further testing of his fork.
If you want to contribute to the networked chain for share propagation testing, please clone https://github.com/jtoomim/p2pool/commits/1mb_hardforked, then configure your node to point to the previous poster's node (e.g. python run_p2pool.py -n previous_node), then list your node IP, what it's connected to, what type and speed of CPU you're using, how fat your pipe is, and whether you're using pypy or CPython (the regular python). Example, and to start us off:
Node IP: ml.toom.im (default ports)
Connected to: ml.toom.im:9334 and :9336 (or :9335 and :9337 for p2p ports)
To connect to me: run_p2pool.py -n ml.toom.im:9333
CPU: Core i7 4790k 4.0 GHz
Pipe: 100m/100m fiber
Using: pypy 2.4.0
Node IP: ml.toom.im (default ports)
Connected to: ml.toom.im:9334 and :9336 (or :9335 and :9337 for p2p ports)
To connect to me: run_p2pool.py -n ml.toom.im:9333
CPU: Core i7 4790k 4.0 GHz
Pipe: 100m/100m fiber
Using: pypy 2.4.0
Dear PROs, can someone post an instruction on how to start jtoomims forked node. I cloned one from github, run it - and it keeps saying "Unknown share type 16"
I got usual p2pool node on that machine and it worked fine.
I got usual p2pool node on that machine and it worked fine.
> whose total work is equal to 3 times the average work required to solve a block, or 8640
That's it, thanks! "3" is the "spread" from the network config file...
That's it, thanks! "3" is the "spread" from the network config file...
frodocooper, please note that my fork includes several improvements, not just a change to the maximum number of transactions per share, and consequently actually has a significantly *lower* share orphan rate than the p2pool mainnet. I don't have any good data on whether jtoomimnet is more fair or less fair than mainnet as of yet, but preliminary data suggests that it's about the same or slightly better.
As for the voting, I'm not sure there was any point. If anyone wants to mine on a share chain that allows less than 1 MB of new transactions per share, then there needs to be two separate share chains, because there is at least one miner (me) who chooses not to mine on anything less than full blocks. Rather than have one chain on which everyone compromises, why not just have two chains to satisfy everyone's goals?
Also, there are plenty of methods by which share network traffic can be reduced or taken out of the latency-critical path. I would prefer to just make shares propagate faster regardless of size rather than organize a vote on how much to cap our block sizes.
Edit: Sorry if I came off as irritable earlier. I'm just tired of politics getting in the way of fixing the code. I think that forking, as a permissionless process, is just socially easier to deal with than trying to get consensus, and in the case of p2pool, it has very few disadvantages. This way, I can just write code, and if you think it's better, you can use it. It's really simple that way. I don't have to worry about writing the code and having it never be used, since I know that I will use it even if nobody else does. And users don't have to worry about voting on features they don't understand; they can see the new code already running before they decide whether or not they like it and want to make a switch.
As for the voting, I'm not sure there was any point. If anyone wants to mine on a share chain that allows less than 1 MB of new transactions per share, then there needs to be two separate share chains, because there is at least one miner (me) who chooses not to mine on anything less than full blocks. Rather than have one chain on which everyone compromises, why not just have two chains to satisfy everyone's goals?
Also, there are plenty of methods by which share network traffic can be reduced or taken out of the latency-critical path. I would prefer to just make shares propagate faster regardless of size rather than organize a vote on how much to cap our block sizes.
Edit: Sorry if I came off as irritable earlier. I'm just tired of politics getting in the way of fixing the code. I think that forking, as a permissionless process, is just socially easier to deal with than trying to get consensus, and in the case of p2pool, it has very few disadvantages. This way, I can just write code, and if you think it's better, you can use it. It's really simple that way. I don't have to worry about writing the code and having it never be used, since I know that I will use it even if nobody else does. And users don't have to worry about voting on features they don't understand; they can see the new code already running before they decide whether or not they like it and want to make a switch.
Point taken, jtoomim. I too apologize if I offended you in any way; my intention was simply to get the point across that there is almost always never an optimal solution, but there is almost always a better one. In the case of P2Pool, and Bitcoin in general, my personal belief is that compromise is almost always the better solution, compared to hard-forking.
But nevertheless, you do make very good, and reasonable, points. And I'll respect that, even if I do not agree with all of them.
. (Also, I'm not a programmer, so I may have skimmed over much of the finer workings of your code, simply because I do not understand code. I do apologize if I made unfair and unfounded generalizations.)Feels like a Scooby Doo caper, but actually your both wrong
I need to update the description on p2pool.org, and do not have the patience to find the code snippet on my phone, but the share chain length is kind of dynamic. While it stays close to three days, if I remember correctly both share weight and the "spread" change it to be less then 3 days under certain circumstances.
The real answer is both deep in this thread, and in the code... I'll spend the time to dig it out and update the site on Monday, unless someone feels like linking the code here before then
I need to update the description on p2pool.org, and do not have the patience to find the code snippet on my phone, but the share chain length is kind of dynamic. While it stays close to three days, if I remember correctly both share weight and the "spread" change it to be less then 3 days under certain circumstances.
The real answer is both deep in this thread, and in the code... I'll spend the time to dig it out and update the site on Monday, unless someone feels like linking the code here before then
Yeah, the P2Pool page on the Bitcoin wiki does say that "Each share contains a generation transaction that pays to the previous n shares, where n is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= [72] hours of shares), whichever is smaller."
I'm still confused as to what the first part means.
(By the way, the P2Pool Bitcoin wiki page needs to be updated. It still says that shares are valid to at most 24 hours, among other outdated information.)
Feels like a Scooby Doo caper, but actually your both wrong
I need to update the description on p2pool.org, and do not have the patience to find the code snippet on my phone, but the share chain length is kind of dynamic. While it stays close to three days, if I remember correctly both share weight and the "spread" change it to be less then 3 days under certain circumstances.
The real answer is both deep in this thread, and in the code... I'll spend the time to dig it out and update the site on Monday, unless someone feels like linking the code here before then
I need to update the description on p2pool.org, and do not have the patience to find the code snippet on my phone, but the share chain length is kind of dynamic. While it stays close to three days, if I remember correctly both share weight and the "spread" change it to be less then 3 days under certain circumstances.
The real answer is both deep in this thread, and in the code... I'll spend the time to dig it out and update the site on Monday, unless someone feels like linking the code here before then
Those were the days when a share used to be valid for 3 days.
Could you kindly point me to some reliable resources that show P2Pool's share lifespan being reduced from approximately three days to one day? Jump to: