Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 274. (Read 2591928 times)
October 17, 2014, 09:28:41 AM
Please sir, can I have some more?.........
October 17, 2014, 08:55:53 AM
2014-10-17 16:51:43.421556 Skipping from block 16312a716d4e7e963a3c7ae3a41f5153965ddf6438ca4ec6 to block 1a2d435b1e4a18aac8afadd6b9617283d36ac0b47de944a5!
2014-10-17 16:51:43.437800 New work for worker! Difficulty: 612.751420 Share difficulty: 13134569.950544 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.446743 New work for worker! Difficulty: 4000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.454766 New work for worker! Difficulty: 2000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.643125 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received
2014-10-17 16:51:43.749030 Peer sent entire transaction 08dabbc9998b366eaf56a3572bacb187c06215e3f955af20ba745f4ba92a4b66 that was already received
2014-10-17 16:51:43.859451 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received
2014-10-17 16:51:44.006821
2014-10-17 16:51:44.006911 GOT BLOCK FROM PEER! Passing to bitcoind! f4545609 bitcoin: https://blockchain.info/block/0000000000000000050ef6f0b71e83a8ee299f646a2c53f21b3e1ba3f4545609
2014-10-17 16:51:44.006971
2014-10-17 16:51:43.437800 New work for worker! Difficulty: 612.751420 Share difficulty: 13134569.950544 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.446743 New work for worker! Difficulty: 4000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.454766 New work for worker! Difficulty: 2000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions
2014-10-17 16:51:43.643125 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received
2014-10-17 16:51:43.749030 Peer sent entire transaction 08dabbc9998b366eaf56a3572bacb187c06215e3f955af20ba745f4ba92a4b66 that was already received
2014-10-17 16:51:43.859451 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received
2014-10-17 16:51:44.006821
2014-10-17 16:51:44.006911 GOT BLOCK FROM PEER! Passing to bitcoind! f4545609 bitcoin: https://blockchain.info/block/0000000000000000050ef6f0b71e83a8ee299f646a2c53f21b3e1ba3f4545609
2014-10-17 16:51:44.006971
October 14, 2014, 03:59:28 PM
You don't need to make p2pool, it should just run from the directory. I would suggest deleting it & uninstalling what you installed & try again following the read me. What version of Linux are you using?
Thanks for the reply.
I am running Ubuntu 14.04
I actually fixed it after spending quite a bit of time on it. I needed to copy zope and twisted from /usr/lib/python2.7/dist-packages to /usr/lib/pypy/dist-packages.
Also, to note, (and it seems obvious now) that you need to run p2pool with the option --relay-network public.us-east.relay.mattcorallo.com. Assuming, your server is on the east coast of the US.
No worries, glad you got it running. You're much better off running the C++ binary for Matts relay node, the python one is veeeeery slow. Again, no need to build it, it runs separately from within the client directory
October 14, 2014, 03:55:05 PM
You don't need to make p2pool, it should just run from the directory. I would suggest deleting it & uninstalling what you installed & try again following the read me. What version of Linux are you using?
Thanks for the reply.
I am running Ubuntu 14.04
I actually fixed it after spending quite a bit of time on it. I needed to copy zope and twisted from /usr/lib/python2.7/dist-packages to /usr/lib/pypy/dist-packages.
Also, to note, (and it seems obvious now) that you need to run p2pool with the option --relay-network public.us-east.relay.mattcorallo.com. Assuming, your server is on the east coast of the US.
October 14, 2014, 02:43:06 PM
How can I edit for altcoin with p2pool ?
I try to find ( Windows ) No luck >
I try to find ( Windows ) No luck >
I would ask in the altcoin thread that you want to mine.
Rav3nPL has a version in git for altcoins
October 14, 2014, 02:38:36 PM
How can I edit for altcoin with p2pool ?
I try to find ( Windows ) No luck >
I try to find ( Windows ) No luck >
October 14, 2014, 04:02:57 AM
You don't need to make p2pool, it should just run from the directory. I would suggest deleting it & uninstalling what you installed & try again following the read me. What version of Linux are you using?
October 13, 2014, 11:35:22 PM
Bleg!!!
I updated my linux system... Bad mistake.
Now I am getting these errors trying to start my p2pools!
Traceback (most recent call last):
File "/opt/p2pool/run_p2pool.py", line 3, in
from p2pool import main
File "/opt/p2pool/p2pool/main.py", line 17, in
from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted.internet
Help please!!
I updated my linux system... Bad mistake.
Now I am getting these errors trying to start my p2pools!
Traceback (most recent call last):
File "/opt/p2pool/run_p2pool.py", line 3, in
from p2pool import main
File "/opt/p2pool/p2pool/main.py", line 17, in
from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted.internet
Help please!!
I have the same issue when I use pypy but not python, "ImportError: No module named twisted" even though twisted is installed. I have tried everything including re-installing twisted and re-making p2pool. I also copied twisted into python2.7 from dist-package. Any other ideas? Thanks.
October 09, 2014, 10:16:00 PM
I have a new node as well, ireland.p2pool.co, which has been running for almost a week and it is not showing on p2pool-nodes.info as well. If anyone knows how to contact the operator or what you have to do to get on this list please let us know. Thanks!
Try peering with a couple connected nodes...
I.E. Find a couple or few close nodes that are connected and add them as nodes using -n when you start a p2pool process.
October 09, 2014, 08:59:33 PM
It will find your node automatically - might take a few days to propagate
I have a new node as well, ireland.p2pool.co, which has been running for almost a week and it is not showing on p2pool-nodes.info as well. If anyone knows how to contact the operator or what you have to do to get on this list please let us know. Thanks!
October 07, 2014, 06:48:37 PM
How does this differ from pointing all the workers to the same workername on the same node, all with high difficulty?
The p2pool client software has to generate multiple workers of multiple different data sets and track them all, and then process the shares as they come in. Setting the difficulty high only helps that latter part (the shares) which is actually the least work. If python wasn't single threaded and as inefficient as it was compared to a low level language, this workload would be irrelevant over and above the work of communicating with the p2pool network and the bitcoind to generate work, but it's not when everything is serialised, so there are always bursts of worst case latencies which are real-world problematic.Excellent point.
M
October 07, 2014, 08:10:14 AM
It will find your node automatically - might take a few days to propagate
October 07, 2014, 06:07:49 AM
.....the p2pool client is actually completely native and unmodified (for now).
Oh? Are you planning something?
(Please say yes 
)1000 hours to rewrite p2pool eh - what's your hourly rate?
October 07, 2014, 05:19:37 AM
How does this differ from pointing all the workers to the same workername on the same node, all with high difficulty?
The p2pool client software has to generate multiple workers of multiple different data sets and track them all, and then process the shares as they come in. Setting the difficulty high only helps that latter part (the shares) which is actually the least work. If python wasn't single threaded and as inefficient as it was compared to a low level language, this workload would be irrelevant over and above the work of communicating with the p2pool network and the bitcoind to generate work, but it's not when everything is serialised, so there are always bursts of worst case latencies which are real-world problematic. October 07, 2014, 05:15:53 AM
It is how p2pool was intended to be used. Your clients earnings will not change, his accepted shares will have a greater weight, but the overall pool efficiency is increased because he is submitting less shares to be processed by us all.
I missed the first part of this convo but going back I can see now. So if every miner with hash rate > 5% of total hash rate ran the ckproxy, we would see a far more efficient p2pool? that would be higher than around 150th/s right now yes?How does this differ from pointing all the workers to the same workername on the same node, all with high difficulty?
M
October 07, 2014, 04:52:36 AM
It is how p2pool was intended to be used. Your clients earnings will not change, his accepted shares will have a greater weight, but the overall pool efficiency is increased because he is submitting less shares to be processed by us all.
I missed the first part of this convo but going back I can see now. So if every miner with hash rate > 5% of total hash rate ran the ckproxy, we would see a far more efficient p2pool? that would be higher than around 150th/s right now yes? October 07, 2014, 12:41:45 AM
It is how p2pool was intended to be used. Your clients earnings will not change, his accepted shares will have a greater weight, but the overall pool efficiency is increased because he is submitting less shares to be processed by us all.
I missed the first part of this convo but going back I can see now. So if every miner with hash rate > 5% of total hash rate ran the ckproxy, we would see a far more efficient p2pool? that would be higher than around 150th/s right now yes? October 06, 2014, 09:25:01 PM
I've set up a private pool solution for a reasonably large miner using a combination of p2pool and ckpool technology. You should all see a decent increase in the overall pool size over the next 24-48 hours.
This hasher is now online. His hashrate should be obvious, right at the top of the list. Barring changes in plans, and provided the hardware continues to hash well, it should be remaining on this pool.Now the interesting thing with this is, because I have connected the hardware via ckproxy instead of as 100 connections directly to the p2pool client, p2pool sees it as one client, which means that this miner's share target is more than 10 times larger than that for other miners. By doing this, even though I've dumped a large hashrate onto the pool, it won't substantially increase the target share rate for the smaller miners. This means smaller miners can benefit from the increased p2pool hashrate decreasing their variance without their share target increasing that much which normally increases their variance the same amount. If more larger miners did something similar on p2pool, it might keep the smaller miners. The large miner benefits from his p2pool client scaling where it otherwise couldn't and the smaller miners get to stay and benefit from his presence. While it's not a "fix" for the overall design, it might give p2pool some breathing space, allowing ever larger miners to join. That said, "small" these days is not really that small... Perhaps p2pool will actually end up being nothing but big miners (though that is what most of the network is now), provided their hardware is compatible :p
Sorry I'm late to the party, but this is great news and wanted to thank you.
While setting "the client" at a higher share diff does nothing for the overall pool diff, it certainly speeds up the pool as a whole vs submitting a bunch of sudo shares that don't meet the minimum diff requirement.
It is how p2pool was intended to be used. Your clients earnings will not change, his accepted shares will have a greater weight, but the overall pool efficiency is increased because he is submitting less shares to be processed by us all.
October 06, 2014, 09:06:09 PM
I've set up a private pool solution for a reasonably large miner using a combination of p2pool and ckpool technology. You should all see a decent increase in the overall pool size over the next 24-48 hours.
This hasher is now online. His hashrate should be obvious, right at the top of the list. Barring changes in plans, and provided the hardware continues to hash well, it should be remaining on this pool.Now the interesting thing with this is, because I have connected the hardware via ckproxy instead of as 100 connections directly to the p2pool client, p2pool sees it as one client, which means that this miner's share target is more than 10 times larger than that for other miners. By doing this, even though I've dumped a large hashrate onto the pool, it won't substantially increase the target share rate for the smaller miners. This means smaller miners can benefit from the increased p2pool hashrate decreasing their variance without their share target increasing that much which normally increases their variance the same amount. If more larger miners did something similar on p2pool, it might keep the smaller miners. The large miner benefits from his p2pool client scaling where it otherwise couldn't and the smaller miners get to stay and benefit from his presence. While it's not a "fix" for the overall design, it might give p2pool some breathing space, allowing ever larger miners to join. That said, "small" these days is not really that small... Perhaps p2pool will actually end up being nothing but big miners (though that is what most of the network is now), provided their hardware is compatible :p
Sorry I'm late to the party, but this is great news and wanted to thank you.
While setting "the client" at a higher share diff does nothing for the overall pool diff, it certainly speeds up the pool as a whole vs submitting a bunch of sudo shares that don't meet the minimum diff requirement.
It is how p2pool was intended to be used. Your clients earnings will not change, his accepted shares will have a greater weight, but the overall pool efficiency is increased because he is submitting less shares to be processed by us all.
October 06, 2014, 10:07:58 AM
It will find your node automatically - might take a few days to propagate
Jump to: