I've been P2Pool mining for a week now with about 600MH/s. So far so good. However, I'm trying to understand something. I keep a running tail on my log file to see the shares I get and blocks found. Today, there were two blocks found which I did not get any shares during the round. However, my bitcoin client shows income under "Mined" at the precise time those blocks were found. I thought I only get paid for shares I find and if a block is found that I didn't find a share, I would receive no payment on it. Looks like I'm wrong. Can anyone clarify and set me straight?
P2Pool uses the PPLNS payment scheme. Every time a block is found, the previous "N" shares get paid. N is 3 times the number of shares needed to find a block on average. At the moment, N=7546. Note, all of the past N shares get paid even if they were submitted before a previous block was found. Yes, that means that a single share can result in you getting paid for multiple blocks. In fact, on average, you should get paid for 3 blocks for every share that you find. When we are lucky, you'll get paid in more than 3 blocks. When we are unlucky, you'll get paid for fewer. |
|
|
|
A couple p2pool.info updates... Donations/SubsidiesI was thinking it would be cool if p2pool.info listed how much has been donated as subsidies. Maybe that could be added into the luck calculation, too.
I updated p2pool.info to include a list of donations/subsidy payments. I decided not to include them in the luck calculation. I detect these transactions by looking for any transaction that includes payments to 10 or more known p2pool miner addresses (I have a list of basically all the addresses that have ever submitted a share). I think this is a pretty robust approach as long as there aren't any donations that go to less than 10 people. If that ever happens and someone lets me know, I can manually add that transaction to the list. JSON APIIt may not have been obvious, but the way that p2pool.info actually works is that all of the things you see on the web page are rendered in your local browser with client-side, javascript code. The web page gets all the data it uses via a series of ajax requests to retrieve JSON data from the p2pool.info web server. On the chance that someone may find something interesting to do with the JSON data, I decided to CORS enable them. So feel free to use this data to make awesome things. Please to not make a zillion requests to my web server though, because while I can easily scale out to handle more load (yay, Cloud!), I don't want to have to do so just for the JSON API because it costs me money. If these APIs get abused, I'll have to remove access to them. The stats and blocks endpoints can also be used to retrieve deltas: P.S. If the response to any of these JSON APIs is not self explanatory, feel free to just ask. |
|
|
|
2012-03-09 16:57:48.460000 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 10061: No connection could be made because the target machine actively refused it..
I'm getting this error, can anyone help me? That error means that either bitcoind is not running (p2pool is looking for it on the same machine as the p2pool process) or is not configured to accept RPC requests. |
|
|
|
Does p2pool still work with 0.5.2 or is 0.6.0rc2 absolutely necessary?
Yes, you can still use 0.5.x |
|
|
|
Just thinking about how I would detect these... I could look for sendmany transactions that have known addresses in them. Maybe the donation address is enough?
The donation address appears not to be included in subsidy payments. So I don't have a consistent way to identify subsidy payments unless someone can provide me one or more addresses that have consistently been mining with a reasonably high hashrate (and therefore has received every subsidy sent in the past) and will continue to be consistently mining with a high hashrate (and will therefore receive every subsidy sent in the future). I can identify the subsidy payments that I have received, but I know that some payments happened before I switched to p2pool. And my hashrate is just above the cutoff where if the pool grows much more, I may not receive every payment in the future (because my share would be below 0.01 of the total payment). The only other thing I can do is maintain a list by hand. It could still appear on the website, but someone would have to tell me every time a subsidy was sent and I'd have to manually add it to the list. So... |
|
|
|
I was thinking it would be cool if p2pool.info listed how much has been donated as subsidies. Maybe that could be added into the luck calculation, too.
That is a good idea. Maybe a separate item. Just thinking about how I would detect these... I could look for sendmany transactions that have known addresses in them. Maybe the donation address is enough? To incorporate these into the luck numbers is a little more tricky. Right now luck is not measuring amount of BTC earned (vs expected), but is measuring things based on hashes. I'd have to change it to be based on BTC or I'd have to translate subsidies into "hash equivalents". I'll think about it more after I look at finding a way to identify subsidy payments in the first place. |
|
|
|
The first version I had out there was just bad...this is much cleaner.
One of these days I might look into email, but I really don't think that I'll need it. Glad someone benefited from the script.
I didn't do emails or anything. The script just quietly fixes the problem by restarting everything. I may add a pause followed by a re-check of the statuses to which I might resort to a full scale automated reboot of the rig if the miner restart didn't fix the issue. I don't really want to just be notified that something is wrong and have to manually fix it. I want the script to fix the problem itself. |
|
|
|
The warning comes after you put in your bitcoin address and namecoin address. I pasted a sample of the output below.
That's an old warning. At the time that web page was created, 0.5 was unreleased and the reported issues were just bugs in bitcoin (not specifically related to signing messages). 0.5.x is quite stable now and what most of us are probably using on a day to day basis. |
|
|
|
Forgive me, I just updated the scripts, the one to modify is the cgm-dev-parse. The new corresponding number is line 45. I think you can just modify that to you liking. I'm sorry I don't already have a device restart function.
Thanks for the help. The 'nc' command was the trick I needed and wasn't familiar with. I already have a script (init.sh) that kills all running miners and starts new ones in background screen sessions, so I just needed a way to detect that it was necessary. This is pretty simple script I ended up with (I run it every 15 minutes via cron): #!/bin/bash
totaldevs=$(cgminer --ndevs | grep '] GPU' | wc -l)
alivedevs=$(echo "{\"command\":\"devs\"}" | nc localhost 4028 | sed 's/\x0$//' | python -mjson.tool | grep 'Alive' | wc -l)
if [ "$totaldevs" != "$alivedevs" ]
then
echo "At least one GPU is not alive. Restarting miner."
/home/username/init.sh
fi |
|
|
|
Has anyone written a script that checks if any GPUs are DEAD/OFF via the API? I'd like to create something that checks periodically and restarts cgminer if that happens (since a restart usually fixes the issue). If someone already has a simple script to talk to cgminer, I'd love to use it as a starting point.
https://bitcointalk.org/index.php?topic=66779.0An example would be line 60, however all it does is pop up a non modal window. You can modify it to email you with echo "$node gpu$i reports $STATUS" | mail -s "Device Failure" emailaddress@whatever.comor whatever else you want. Outstanding. Thank you. |
|
|
|
|
Has anyone written a script that checks if any GPUs are DEAD/OFF via the API? I'd like to create something that checks periodically and restarts cgminer if that happens (since a restart usually fixes the issue). If someone already has a simple script to talk to cgminer, I'd love to use it as a starting point.
|
|
|
|
That wasn't found by the main p2pool but was found by a small fork of miners that didn't update. Blocks found by the un-updated splinter group are now intentionally excluded. Those miners are not part of the reported pool hashrate and so their blocks shouldn't be credited against the main pool's hashrate for the purposes of things like round length and luck statistics. I suppose I could still display "fork blocks" in some distintive way, though. |
|
|
|
|
In the absence of user accounts where you can identify who really owns a miner address, you could do what eligius did for this same situation. They made users sign their request for namecoin <-> bitcoin address mapping with the private key for their bitcoin address.
|
|
|
|
I wish to have cgminer always split work across my GPUs, especially on p2pool. Can I force-enable this as an option?
Why? To satisfy my OCD. Do you need a better reason? You can't do what you are asking. I asked because if there were a good reason for wanting this, then it might be worth exploring further and possibly doing the development to make it possible. |
|
|
|
I wish to have cgminer always split work across my GPUs, especially on p2pool. Can I force-enable this as an option?
Why? |
|
|
|
So I see the variance is still pretty noticeable... Would anyone be willing to share rough weekly/monthly profits and their mhash which is pointed at p2pool? I'm one of those seeing is believing kinda guys. When I was just mining one gpu, I was getting about .03 more/day than I would have on PPS/Prop at a big pool with fees, so I was happy, but now that I'm on 4 gpu's and over 3x more mhash (1350 now), I'm just curious as to if I will still make my calculated (based off of BTC calculators and such) ~.9BTC per day?
You can see the recent luck on the p2pool.info stats page. You can determine what any miner made by doing simple math with those values and any bitcoin mining calculator. For example, a 1GH/s miner would earn 0.67 BTC/day if they have no variance. You can see that p2pool has been unlucky recently and in the last 7 days, the pool has found about 65% of the blocks that would have been expected if the pool had no variance. So that 1GH/s miner would actually have made 0.67 BTC/day * 0.65 = .4355 BTC/day over the past 7 days. Of course on weeks that p2pool is lucky, the pool will find more blocks than expected if there were zero variance and that miner would make more than 0.67 BTC/day. Over a long period of time, the good weeks will tend to offset the bad weeks, etc. |
|
|
|
|
Show Posts
