 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
so the pps is actually as low as 0.00005129803015564 * 0.93 = 4.7707168 × 10^-5 ?
Looks about right. I wonder if anybody has put together a chart that shows what payout method is better for any given hash rate per average block time. If not, I guess I could start on an XLS or something, but I just ate lunch. Sleepy time. I have a script that calculates potential earnings for a few pools, comparing pps to prop. Pretty much got the results phewajack got. Below 600MHz i earn more on pps, even compared to zero fee prop pools. I can post the script here later when I get home. |
|
|
|
Why on Earth would they need to watch the forums? They can attack whenever they please. What benefit do they get from watching this thread? May be to check when admin is sleeping ?  Admins never sleep ;-) |
|
|
|
There was a DDoS attempt at this moment.
Well, I guess, unfortunately, cynicism confirmed. I have no doubt in my mind that whoever is responsible watches these forums closely. The admin could probably pull IP logs and get an idea; especially if the user is not a member. A member may be more difficult to detect. My guess is; this can be tracked if somebody puts the resources into doing so. Why on Earth would they need to watch the forums? They can attack whenever they please. What benefit do they get from watching this thread? |
|
|
|
Didn't want to create a new topic for this or anything sense it's more directed at people using this pool, but I was wondering how often most people payout? Do you wait to accumulate a certain amount, or payout each day? Any recommendations? Just curious.
Whenever you want really. It's not like you're gaining interest by it being in your wallet or btc guild account. |
|
|
|
So instead of reloading the block stats and my account pages on the site all the time I whipped up a quick python script to curl down the data from the api and display it. It requires python and curl to be installed, I've tested it on ubuntu but there isn't a reason it wouldn't work with any other os. For now you need to just put your API Key in the top, and if you're on a different os flavor update the #! python path and the curl path. Here is the sample of the output: +-+-+-+-BTC GUILD Pool Stats for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-+-+-+-+
+ Confirmed Payout : 0.58573323 +
+ Unconfirmed Payout : 0.34381127 +
+ Estimated Payout : 0.02086434 +
+ Sum Total (inc est): 0.95040884 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ Total Worker Hashrate 615.61 Shares 1375 Stales 3 Stale% 0.22 +
+ Pool Average Block Time (seconds) 2825 +
+ Latest Block Times 1:07:50 0:36:48 0:12:03 0:07:46 0:14:48 0:44:14 +
+ Pool Est Blks/24hrs 31 Miner Est 24hr Rewards : 0.61859068 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I'll likely provide some updates to allow for all sorts of extras (config files, idle warnings, etc.) as well but this is a start at least. Feel free to pm me if you have questions, and you can always submit a pull request to change the code. I've sent you a pull request for a small calculation fix and also individual worker stats |
|
|
|
|
Ah ok, sorry misread your question. That shouldn't happen, my script doesn't cache anything so the data is always fresh when you (re)load the page. The values must have changed inbetween you opening my page and opening the other :-)
|
|
|
|
Another little update I pushed, but pretty useful. You no longer have to enter your worker address in the text box every time you want to fetch the stats. Simply visit http://continuumpoolrpc.appspot.com/<workeraddress> for instant gratification. You can bookmark this address for easy viewing of stats at any time. Enjoy. Worker hashrate dosn't work for me. I see: Worker hash rate: 458.129844 MHashes/s but it's different from what the continuum say Pretty much what PoulGrym said, it's only an estimate of your hashrate depending on how often you're submitting shares back. But it should fluctuate around your actual hashrate so don't be worried if you see it below (or above) your actual hashrate. |
|
|
|
Another little update I pushed, but pretty useful. You no longer have to enter your worker address in the text box every time you want to fetch the stats. Simply visit http://continuumpoolrpc.appspot.com/<workeraddress> for instant gratification. You can bookmark this address for easy viewing of stats at any time. Enjoy. |
|
|
|
|
Still have games for sale
|
|
|
|
Here is my nice and simple Continuumpool stats site using the RPC protocol. This is pretty rough and I still haven't implemented the monitoradd() and monitordrop() methods but they will be soon. Anyways give it a go and give me some feedback on how to improve it. Thanks. http://continuumpoolrpc.appspot.com/Enjoy Edit: Now with even more pool and worker stats! Will try to get the monitoradd() and monitordrop() methods working sometime soon. |
|
|
|
Okay, this is going to be a newbie question, I apologize in advance. How do you use the RPC interface?
After some Googling it seemed to me that mere mortals cannot use it. But soon most (all?) of the functionality should be available from the website. I've written a script that makes use of a Python RPC client to communicate with continuumpool's server. I'm currently trying to see if I can make it an app engine site otherwise I will release it as an executable. |
|
|
|
|
That's not what pool hopping is...
|
|
|
|
|
There is no reason to have multiple worker accounts. You can set up all your workers with the exact same credentials and the pool server will be none the wiser it is different cards requesting work. The reason multiple worker accounts exist is purely so users can see statistics on individual cards/workers.
|
|
|
|
Mh/s glitch? I just started mining about 12 hours ago using BTCGuild. Let me say first, it was a lot easier to set up than I thought The GUIminer I'm using did seem to have several times where it could not communicate with the RPC whatever. Here's what's odd, unless it can be explained as a glitch on BTCGuild. By the hardware comparisons chart on the bitcoin wiki, we can see that the 6970 had a range of about [ 323 Mh/s - 423 Mh/s]. I am using one 6970 with a desktop and churning about 358 Mh/s. [tried tweaking a little, but it didn't go up and is fine while I take in the big picture of the process.] On BTCGuild it shows one's hash rate at the bottom and I assume it's close estimate of recent activity... it showed closer to 300 Mh/s. Maybe lower becasue of some averaging function that factored in time when the miner was offline for rebooting etc - e.g. discovering websites with video ads can crash it.  After being away from the system for a while and the monitors went to sleep, I came back and logged in to inspect the activity, and saw that there was 443 Mh/s on the account. If it's true, then it is a value greater than the range of 6970's setups in the bitcoin wiki. Is this a glitch with BTCGuild or did the miner suddenly become more efficient? The system is simple: Windows 7 CPU: Intel i7 2600 GPU: 1 x 6970 Miner: Guiminer ADD SDK: v. 2.4 At the this time, the pool account is showing a lower hash rate (257 Mh/s) than the Guiminer is showing 351 Mh/s (almost the same all day). The system had no down time for several hours. That also seems odd, but perhaps, it is due to BTCGuild being down or something, and then diluting it with averaging over time, maybe? But I can't see how the higher hash rate could be calculated. Any ideas on why BTCGuild read such a higher hashrate that time? The hashrates seen on on pool websites are estimates only. The only thing they can do is count the rate you're sending shares back, which is pretty crude because the time to solve one can vary greatly. So don't worry about it, the only true hashrate for your graphics card is the one shown in the miner. Hope that helps. |
|
|
|
Pool and site seems to be down...
Damn. Is this pool getting DDoS? Because mostly it goes down like a minute and up again, but this one has been down for more than an hour like 3 days ago. Been down for an hour and a half according to when my miner stopped. Not sure what's going on. |
|
|
|
|
Pool and site seems to be down...
|
|
|
|
How much for hl2 ep1 and ep2 ?
pm'd |
|
|
|
a single overclocked 5830 can get over 300 mhash/s
So i'm guessing 300mhash/s takes a year to make even 200€? No it'll be much less than a year. But yea CPU mining is pointless unless you have free electricity. And even then the returns are still small... |
|
|
|
apparently, the temp measuring unit is broken
This. What card is it? We can only dream of those temps with a fan. |
|
|
|
|
Still looking to sell some games
|
|
|
|
|
