Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 432. (Read 2591964 times)
February 03, 2014, 03:57:55 PM
I was thinking about creating a public P2pool node. What kind of hardware and bandwidth would I need? Lets assume I get 1 TH.
February 03, 2014, 11:52:43 AM
I am finding interesting with the newest update to P2Pool 3.4.14 that my miners aren't finding anything but my friend who is using a Avy 107GH/s is finding blocking and is getting paid more than what my 186GH/s miners are getting when they do eventually find stuff. Previous before the patch the 107GH/s miner was finding nothing while my rigs were finding the blocks.
That's probably more luck than actual differences in P2Pool versions.
February 03, 2014, 11:48:02 AM
I am finding interesting with the newest update to P2Pool 3.4.14 that my miners aren't finding anything but my friend who is using a Avy 107GH/s is finding blocking and is getting paid more than what my 186GH/s miners are getting when they do eventually find stuff. Previous before the patch the 107GH/s miner was finding nothing while my rigs were finding the blocks.
February 03, 2014, 10:16:44 AM
Does this also mean that a miner would received 100% of the payout and the pool would receive 0%? Because that's what also just happen. My miners are still doing the 50% while the second miner which was just paid out (after I updated the server) got 100% of the payout.
Yes, exactly. If share A's 50% chance goes to the miner, the miner gets full payment for that share on all blocks found.
I think it might be possible to improve on this in a way that would remain backwards compatible with older versions of p2pool. I'll write it up this evening when I get home from work.
If anyone knows offhand, is the sharechain packed in such a way that a specific byte order is required and the structure can't be changed? Or is it stored in more of a json/xml sort of way where a field could be added and older nodes will just ignore the new field since they never access/read it?
February 03, 2014, 08:28:07 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding) 
You can track new commits/updates on GitHub.
https://github.com/forrestv/p2pool/commits/master
Updates actually come fairly often to the "dirty" codebase, but you can stick with the Tags(the whole version numbers) for the "stable" releases.
Where is the stable release kept?
As I mentioned above... The Tags: https://github.com/forrestv/p2pool/releases
You should surf around the Github repository to get a feel of how github projects have their stuff stored... Releases/tags, issues lists, bug fixes and experimentation in the Master branch and the various README files, etc. This is all pretty standard github stuff and can come in handy not just for P2pool updates, but for seeing the behind the scenes stuff with BFGMiner, CGMiner, CPUMiner, Bitcoind, etc.
Oh there isn't an actual stable release vs a dirty release of P2Pool then.
Umm. Not quite getting what you're saying here. This is all pretty standard code development stuff and most projects follow this structure.
Master branch has the rolling bug fixes, experimentation, git pulls from other branches/forks, etc. Other branches are created to try out ideas or for modular development while the Master branch is the main branch. Once a project is relatively stable, a release is tagged while development continues for the next major version.
For p2pool the last stable tag is 3.14 which was released two months ago.
Current HEAD commit version on the Master Branch is 13.4-14-g7aa75ce-dirty that was updated a few days ago.
I'm sure once new features accumulate and things are at a stable point, forrestv will roll out a version 3.15 at some point.
It's your choice to use the major stable releases or the interim in-flux/in-development beta or "dirty" releases.
You control which commit point or release tag to pull from when you git pull from the repository. Or you can just download the tag releases from the link I posted.
Don't know if this will help you or confuse you more, but try this for more info: http://www.lockergnome.com/web/2011/12/13/how-to-use-github-to-contribute-to-open-source-projects/
February 03, 2014, 06:55:57 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding)
You can track new commits/updates on GitHub.
https://github.com/forrestv/p2pool/commits/master
Updates actually come fairly often to the "dirty" codebase, but you can stick with the Tags(the whole version numbers) for the "stable" releases.
Where is the stable release kept?
As I mentioned above... The Tags: https://github.com/forrestv/p2pool/releases
You should surf around the Github repository to get a feel of how github projects have their stuff stored... Releases/tags, issues lists, bug fixes and experimentation in the Master branch and the various README files, etc. This is all pretty standard github stuff and can come in handy not just for P2pool updates, but for seeing the behind the scenes stuff with BFGMiner, CGMiner, CPUMiner, Bitcoind, etc.
Oh there isn't an actual stable release vs a dirty release of P2Pool then.
February 03, 2014, 06:42:31 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding)
You can track new commits/updates on GitHub.
https://github.com/forrestv/p2pool/commits/master
Updates actually come fairly often to the "dirty" codebase, but you can stick with the Tags(the whole version numbers) for the "stable" releases.
Where is the stable release kept?
As I mentioned above... The Tags: https://github.com/forrestv/p2pool/releases
You should surf around the Github repository to get a feel of how github projects have their stuff stored... Releases/tags, issues lists, bug fixes and experimentation in the Master branch and the various README files, etc. This is all pretty standard github stuff and can come in handy not just for P2pool updates, but for seeing the behind the scenes stuff with BFGMiner, CGMiner, CPUMiner, Bitcoind, etc.
February 03, 2014, 06:11:38 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding)
You can track new commits/updates on GitHub.
https://github.com/forrestv/p2pool/commits/master
Updates actually come fairly often to the "dirty" codebase, but you can stick with the Tags(the whole version numbers) for the "stable" releases.
Where is the stable release kept?
February 03, 2014, 06:10:46 AM
The -fee doesn't seem to be working...since I have added it -fee 50 my server has taken home most of the payout. The recent pay looks like this; server = 0.03817988, my wallet = 0.00722744. It looks like that for all the other payouts too. Looks like something is broken in the code. 
Must just be variance. How many shares have you found? Remember, the pool doesn't receive 50% of the payout, it receives randomly over time 50% of the shares. So the number of the shares the fee has in the sharechain can vary quite a bit. There is a literal random() call with the fee % to see who owns each share your node finds.
Hard cording in a fee amount to the sharechain like how donations work would be a really nice feature and easy to add. But not backwards compatible, so it'd have to be one of those things that only kick in once 95% of the network has upgraded. Then the variance is gone for both operator and miner in regards to node fee.
Does this also mean that a miner would received 100% of the payout and the pool would receive 0%? Because that's what also just happen. My miners are still doing the 50% while the second miner which was just paid out (after I updated the server) got 100% of the payout.
February 03, 2014, 06:00:14 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding)
You can track new commits/updates on GitHub.
https://github.com/forrestv/p2pool/commits/master
Updates actually come fairly often to the "dirty" codebase, but you can stick with the Tags(the whole version numbers) for the "stable" releases.
February 03, 2014, 04:22:12 AM
Just in case no one has been watching, there is a new update to P2Pool. I am not sure what the fixes do as the op doesn't seem to care to let everyone know what he's fixing...for we know he could be working for the NSA and putting back doors into his code! (kidding)
February 02, 2014, 09:01:52 PM
Does anyone know how to get the following data from this P2Pool site onto another site like my own?
I am interested in the "blocks found today" and "Local user summary" data at the bottom of the page.
http://sleipnir.syari.net/pool/
Here's what I use:
p2pool.smoothrunnings.ca:9332/
I am interested in the "blocks found today" and "Local user summary" data at the bottom of the page.
http://sleipnir.syari.net/pool/
Here's what I use:
p2pool.smoothrunnings.ca:9332/
February 02, 2014, 08:56:55 PM
Is the P2Pool on GMT time? I am just noticing now my hashing time is 5 hours ahead of my local time.
February 02, 2014, 09:10:01 AM
The -fee doesn't seem to be working...since I have added it -fee 50 my server has taken home most of the payout. The recent pay looks like this; server = 0.03817988, my wallet = 0.00722744. It looks like that for all the other payouts too. Looks like something is broken in the code.
Must just be variance. How many shares have you found? Remember, the pool doesn't receive 50% of the payout, it receives randomly over time 50% of the shares. So the number of the shares the fee has in the sharechain can vary quite a bit. There is a literal random() call with the fee % to see who owns each share your node finds.
Hard coding in a fee amount to the sharechain like how donations work would be a really nice feature and easy to add. But not backwards compatible, so it'd have to be one of those things that only kick in once 95% of the network has upgraded. Then the variance is gone for both operator and miner in regards to node fee.
February 02, 2014, 07:31:02 AM
The -fee doesn't seem to be working...since I have added it -fee 50 my server has taken home most of the payout. The recent pay looks like this; server = 0.03817988, my wallet = 0.00722744. It looks like that for all the other payouts too. Looks like something is broken in the code.
You need to find more shares, to it will even out 50/50.
February 02, 2014, 07:20:29 AM
The -fee doesn't seem to be working...since I have added it -fee 50 my server has taken home most of the payout. The recent pay looks like this; server = 0.03817988, my wallet = 0.00722744. It looks like that for all the other payouts too. Looks like something is broken in the code.
February 02, 2014, 01:07:26 AM
From Btc-guild January 24, 2014
"There was a brief (3-4 minute) restart on all servers this afternoon in order to apply a critical patch to all stratum servers. This patch was required before the next difficulty update, which is likely to push the network difficulty beyond the 2.1 billion mark. The original stratum code was written with difficulty barely at the 1-million mark, and was not written to anticipate network difficulty exceeding the maximum size of a 32-bit variable."
Does something simialiar affect to p2pool, are all the versions of the bitcoind, leveldb or what ever depedencies ready for exceeding the maximum size of a 32-bit variable?
"There was a brief (3-4 minute) restart on all servers this afternoon in order to apply a critical patch to all stratum servers. This patch was required before the next difficulty update, which is likely to push the network difficulty beyond the 2.1 billion mark. The original stratum code was written with difficulty barely at the 1-million mark, and was not written to anticipate network difficulty exceeding the maximum size of a 32-bit variable."
Does something simialiar affect to p2pool, are all the versions of the bitcoind, leveldb or what ever depedencies ready for exceeding the maximum size of a 32-bit variable?
February 02, 2014, 12:47:25 AM
I'm losing hope here... we lost 100 users which certainly isn't helping variance.
Perhaps it's the patronizing "tone" some of the users here feel the need to use when others ask questions. Some even call themselves "old timers" with 8 months experience. I know it's made me look elsewhere...The lack of finding work, aka blocks, isn't related to just pool but everyone feels it. Before building and using my own P2Pool server I was using Bitminter who was going through weeks of not finding any work and their overall pool numbers started to dwindle. Now they are back to almost 380TH/s, what we are seeing will pass and another pool will be affected then everyone on that pool or almost everyone will jump ship.
Quote from: bkminer
So has the problem from December been fixed with the ban peers commit? I'm still running outgoing only.
Yeah, go ahead and change maxconnections to non-zero, I've had it at 10 for the past week and it's been stable with the latest version of p2pool on git. 
February 01, 2014, 09:59:30 PM
... and if you keep your log files (I have them for all time I run p2pool ... which isn't much) you can just grep "Share difficulty"
(of course p2pool truncates them and you lose log info - unless you resolve that)
Heh, in the first day of the recent run when I turned on p2pool (6pm to 12midnight) it went as low as 793467.233915 and as high as 940359.665147
In a somewhat tabular form (my timezone) ...
26th 628549.635965 to 955434.444950 23:21:44
27th 623111.657122 to 1005577.897267 00:20:27
28th 667502.146435 to 908145.054910 11:53:23
29th 600278.575638 to 814628.296267 11:03:18
30th 563518.983970 to 762241.221921 10:02:30
31st 524941.323059 to 765905.483240 15:22:34
01st 468151.837131 to 734301.175462 11:53:23
So yes there clearly is decline over the past week ... but during each day the diff varies a lot!
And yes it's not just falling (the time at the end is when the lowest diff was)
Edit: hmm I was trying to work out from the log when the orphans/dead happen - it seems it doesn't want to let you know ... you just happen to find out a little later when the counter increments in the "Shares:" line
e.g.
(yeah my 4th share so far today was my 2nd orphan share today ...)
(of course p2pool truncates them and you lose log info - unless you resolve that)
Heh, in the first day of the recent run when I turned on p2pool (6pm to 12midnight) it went as low as 793467.233915 and as high as 940359.665147
In a somewhat tabular form (my timezone) ...
26th 628549.635965 to 955434.444950 23:21:44
27th 623111.657122 to 1005577.897267 00:20:27
28th 667502.146435 to 908145.054910 11:53:23
29th 600278.575638 to 814628.296267 11:03:18
30th 563518.983970 to 762241.221921 10:02:30
31st 524941.323059 to 765905.483240 15:22:34
01st 468151.837131 to 734301.175462 11:53:23
So yes there clearly is decline over the past week ... but during each day the diff varies a lot!
And yes it's not just falling (the time at the end is when the lowest diff was)
Edit: hmm I was trying to work out from the log when the orphans/dead happen - it seems it doesn't want to let you know ... you just happen to find out a little later when the counter increments in the "Shares:" line
e.g.
Code:
2014-02-02 13:21:22.128994 GOT SHARE! user db3d6334 prev 04e3b80b age 28.13s
...
2014-02-02 13:22:57.976632 Shares: 26 (3 orphan, 0 dead) Stale rate: ~11.5% (4-29%) Efficiency: ~100.3% (80-109%) Current payout: ...
2014-02-02 13:22:57.976694 Pool: 124TH/s Stale rate: 11.8% Expected time to block: 21.1 hours
2014-02-02 13:22:59.397758 New work for worker! Difficulty: 64.000000 Share difficulty: 567565.872050 Total block value: 25.064420 BTC including 282 transactions
2014-02-02 13:22:59.521511 New work for worker! Difficulty: 16.000000 Share difficulty: 567565.872050 Total block value: 25.064420 BTC including 282 transactions
2014-02-02 13:23:00.984396 P2Pool: 17381 shares in chain (17385 verified/17385 total) Peers: 6 (0 incoming)
2014-02-02 13:23:00.984510 Local: 154GH/s in last 10.0 minutes Local dead on arrival: ~9.7% (7-13%) Expected time to share: 4.4 hours
2014-02-02 13:23:00.984556 Shares: 26 (4 orphan, 0 dead) Stale rate: ~15.4% (6-34%) Efficiency: ~95.2% (74-106%) Current payout: ...
February 01, 2014, 09:35:01 PM
So has the problem from December been fixed with the ban peers commit? I'm still running outgoing only.
Jump to: