i'm interested in a iPhone interface. I love checking my miner stats throughout the day
Alright, link to the mobile interface now available on the "My Account page". You can add an icon for it to your Home screen via Safari.
Topic: [ANN] The First Litecoin PPS Pool (litecoinpool.org) - page 73. (Read 227532 times)
Alright, link to the mobile interface now available on the "My Account page". You can add an icon for it to your Home screen via Safari.
You might have noticed I have moved the payout history to a separate page, adding links to the block explorer for each transaction. I have also added the possibility to change the donation percentage because, believe it or not, one of our miners wanted to donate more. 
By the way, is anybody interested in an iPhone interface to check your live stats? Let me know!
By the way, is anybody interested in an iPhone interface to check your live stats? Let me know!
i'm interested in a iPhone interface. I love checking my miner stats throughout the day
Windows or Linux? If you're using Windows, it might well be that excessive load (not cpu usage) was only a problem under Linux, and you didn't experience it even with the old drivers.
Windows. Don't really know how to tell the difference between CPU usage and load from the task manager indeed, unlike on Linux where top makes it obvious ^^ Yeah, I know it might sound confusing. The point is that CPU usage is the same, but CPU load is not.
Lucky you... I have the same temps as before, around 58-59°C (Phenom 2 955 @3.6GHz)Yeah, I know it might sound confusing. The point is that CPU usage is the same, but CPU load is not.
Lucky you... I have the same temps as before, around 58-59°C (Phenom 2 955 @3.6GHz) Uhm, bizarre. On my main Bitcoin rig I see no slowdown at all using both CPU cores of a Sempron for Litecoin (5.8 kH/s) and two 5870's for Bitcoin (850 MH/s). This is using ATI drivers 11.12 and AMD Stream SDK 2.5, under Linux. And CPU temperature went down from 64°C to 60°C. Works like a charm now!
+/- fixed by setting GPU miner affinity to a single core and raising its priority while lowering LTC miner priority.Still, I don't get how your CPU temperature can decrease if all you did in the end was replace a 100% CPU usage by driver mess with a 100% CPU usage by LTC miner...
Yeah, I know it might sound confusing. The point is that total CPU usage is the same as before, but CPU load is not.
Uhm, bizarre. On my main Bitcoin rig I see no slowdown at all using both CPU cores of a Sempron for Litecoin (5.8 kH/s) and two 5870's for Bitcoin (850 MH/s). This is using ATI drivers 11.12 and AMD Stream SDK 2.5, under Linux. And CPU temperature went down from 64°C to 60°C. Works like a charm now!
+/- fixed by setting GPU miner affinity to a single core and raising its priority while lowering LTC miner priority.Still, I don't get how your CPU temperature can decrease if all you did in the end was replace a 100% CPU usage by driver mess with a 100% CPU usage by LTC miner...
By the way, for those of you who are doing both CPU and GPU mining with an ATI card on the same rig, consider updating ATI drivers to version 11.12. This new version should solve the CPU usage problem, even on multiple-card setups.
Yup, I noticed that too, only problem is I still can't use all my cores to mine LTC because then the GPU miner almost stops. And also when I don't leave 2 idle cores the GPU miner mines a bit slower.Uhm, bizarre. On my main Bitcoin rig I see no slowdown at all using both CPU cores of a Sempron for Litecoin (5.8 kH/s) and two 5870's for Bitcoin (850 MH/s). This is using ATI drivers 11.12 and AMD Stream SDK 2.5, under Linux. And CPU temperature went down from 64°C to 60°C. Works like a charm now!
Bitcoin... and Litecoin... live together in perfect harmony...
By the way, for those of you who are doing both CPU and GPU mining with an ATI card on the same rig, consider updating ATI drivers to version 11.12. This new version should solve the CPU usage problem, even on multiple-card setups.
Yup, I noticed that too, only problem is I still can't use all my cores to mine LTC because then the GPU miner almost stops. And also when I don't leave 2 idle cores the GPU miner mines a bit slower. Just signed up! Looking forward to making my server room even hotter now that the CPUs are in use lol
Welcome aboard, Red Emerald!By the way, for those of you who are doing both CPU and GPU mining with an ATI card on the same rig, consider updating ATI drivers to version 11.12. This new version should solve the CPU usage problem, even on multiple-card setups. I have just carried out the update on my main box, and I now have one more core for mining Litecoin. Plus, temperatures dropped considerably!
(Thanks to grue for the heads up!)
Just signed up! Looking forward to making my server room even hotter now that the CPUs are in use lol
EDIT:
ahh nvm i'm soooooo stupid....
forgot the $ sign.... and my friend and I didn't noticed that...
ahh nvm i'm soooooo stupid....
forgot the $ sign.... and my friend and I didn't noticed that...
A question about the API:
Currently the API is like this (in php print_r() format):
{code}
All the workers' names include a dot, and it's 500 if I use the data like this:
How to use it correctly?
Currently the API is like this (in php print_r() format):
{code}
All the workers' names include a dot, and it's 500 if I use the data like this:
Code:
echo $lp["workers"]["user.worker"]["hash_rate"];
The dots should not be an issue if you use associative arrays. The following code works for me:
Code:
$api = json_decode(file_get_contents("http://www.litecoinpool.org/api?api_key=my-api-key-here"), TRUE);
echo $api["workers"]["pooler.1"]["hash_rate"];
A question about the API:
Currently the API is like this (in php print_r() format):
All the workers' names include a dot, and it's 500 if I use the data like this:
How to use it correctly?
Currently the API is like this (in php print_r() format):
Code:
Array
(
[user] => Array
(
[total_rewards] => 0.0
[paid_rewards] => 0.0
[unpaid_rewards] => 0.0
[past_24h_rewards] => 0.0
)
[workers] => Array
(
[user.worker] => Array
(
[hash_rate] => 0.0
[valid_shares] => 0
[stale_shares] => 0
)
)
[pool] => Array
(
[hash_rate] => 697
[pps_rate] => 0.00096512
)
[network] => Array
(
[hash_rate] => 22763
[difficulty] => 0.76679615
)
)
All the workers' names include a dot, and it's 500 if I use the data like this:
Code:
echo $lp["workers"]["user.worker"]["hash_rate"];
Difficulty is increasing... +15%!
I have just noticed a curious fact: at difficulty 1, the expected daily earnings in coins/day equal the hash rate in khash/s, with an error of less than 0.6%!
Suppose your hashing speed is 1 kH/s: you will compute 86,400,000 hashes a day. At difficulty 1 the probability of finding a block is 2-32 per hash. Since a block is worth 50 coins, your expected daily earnings will amount to
86,400,000 / 4,294,967,296 * 50 = 1.00582838058
This means that you can estimate your daily income by simply dividing the hash rate by the difficulty. Now isn't that remarkable?
I have just noticed a curious fact: at difficulty 1, the expected daily earnings in coins/day equal the hash rate in khash/s, with an error of less than 0.6%!
Suppose your hashing speed is 1 kH/s: you will compute 86,400,000 hashes a day. At difficulty 1 the probability of finding a block is 2-32 per hash. Since a block is worth 50 coins, your expected daily earnings will amount to
86,400,000 / 4,294,967,296 * 50 = 1.00582838058
This means that you can estimate your daily income by simply dividing the hash rate by the difficulty. Now isn't that remarkable?
A 27 block orphaned chain? Any idea why the network wouldn't re-org in 26 or less blocks?
It'd be interesting to analyse the two chains and see if any transactions were changed. 
A 27 block orphaned chain? Any idea why the network wouldn't re-org in 26 or less blocks?
Another reason to choose PPS: you get paid even when blocks get out of the main chain.
There was one rather long (27 blocks) chain that became orphaned 7 hours ago, and two of those blocks were found by our pool.
Did this affect your earnings? Not at all! (It only affected the pool's wallet, d'oh!)
Here is the root of the orphaned chain:
http://blockexplorer.sytes.net/block/51eb5d3c807107c6e9dc5ba0074883b718d1a5fe48f245f8cef53eff74ee09dc
There was one rather long (27 blocks) chain that became orphaned 7 hours ago, and two of those blocks were found by our pool.
Did this affect your earnings? Not at all! (It only affected the pool's wallet, d'oh!
)Here is the root of the orphaned chain:
http://blockexplorer.sytes.net/block/51eb5d3c807107c6e9dc5ba0074883b718d1a5fe48f245f8cef53eff74ee09dc
Do you mind if I poll your API every five-or-so minutes?
No problem.
Do you mind if I poll your API every five-or-so minutes?
Jump to: