[~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More

[error]

Always assume your users are going to try to screw with you when dealing with their input.

[1714800159]

1714800159

[1714800159]

1714800159

[eleuthria]

eleuthria:

Additionally, I am showing I am pushing out 624Mhash/s right now and your site is only showing me: 62.04 mH/sec on 1 worker and 81.13 mH/sec   on the other.

Ideas?

The hash rate shown by the pool is your average hash rate over the past 15 minutes, and is calculated based on submitted shares in that window.  It is only an ESTIMATE.  Your luck on reporting getwork results will always cause some variance over what is shown by your client.  Since you only recently started, the rate will be much lower until you've been running for 15 minutes.

[eleuthria]

Always assume your users are going to try to screw with you when dealing with their input.

Oh I know that one.  Problem was I just finished setting up the password hashing on the website (PHP) when I added it to the pool (C).  So my habits of PHP carried over.  Worked fine with standard data, but C doesn't fail quite as softly when passed bad data as what PHP allows.  The curse of higher level languages!

[shat]

Average makes sense.  Started up working again for a bit and is now back to comm errors

[travex]

Just joined with 1.5Gh/s and got comm error after 5 mins . Sad, back to BTCmine

[eleuthria]

Looks like we still have one worker that has caused a crash every time they try to communicate with the server...they're causing something completely different from the others.  Back to running a fully logged version to see what they're doing differently.

[shat]

hopefully it isn't one of mine   back up and running @ 600Mhps.  Sent you an email btw.  Check it tomorrow when you have some time.  I'm off to sleep.

[shat]

back to down

[travex]

I will join again when the pool is completely stable lol, down again.

[shat]

I have faith in it. Buddy turned me on to it today at the office. I've been in slush's and solo for a while now. Let us know if we can help at all mate.

[Nythain]

I'm stickin with it. So far been stable since it came back up. Kinks are bound to happen, at least eleuthria tends to be on top of them. Also a fan of the very quick updates about whats going on. I do need to figure out how to set up guiminer to treat a second pool as a "fallover" in case of downtimes.

[eleuthria]

Thank you for the support all.  It has been stable since the last crash (although it normally crashes about 1 minute after I say that).

It will go down for about 3 seconds shortly so that the auto-restart script can run during the night.

Worker rename and password resets are working in testing, but there's no nice way to fit them in the current page.  Tomorrow morning I will be splitting workers into two pages.  "My Account" will show the current worker stats table (with reset buttons).  Then you will have a "Manage Workers" page which has the ability to add, hide, rename, reset, and change the passwords for your workers.

[Nythain]

Wow my stales have gone through the roof since that last brief downtime, and a whole loooooot of long poll exceptions.

Scratch that. Must have just been a temporary side effect of the short downtime. Been runnin good for a while now.

[MrGaSp]

I am throwing my 420MH/s at it from deepbit..might stick with this.  I do appreciate the donate option, seems to fit the rest of the bitcoin community.

to tell you the truth, i thought of doing 99% donation tonight...idk yet though.. =P

Edit: I also really love how 'reset' doesn't wreck your ever total, ty for that..

[Nythain]

I am throwing my 420MH/s at it from deepbit..might stick with this.  I do appreciate the donate option, seems to fit the rest of the bitcoin community.

to tell you the truth, i thought of doing 99% donation tonight...idk yet though.. =P

Edit: I also really love how 'reset' doesn't wreck your ever total, ty for that..

As a fairly small contributing member of the pool (mere 78Mh/s) I would personally like to say thanks for bringing more power over.

[MrGaSp]

I am throwing my 420MH/s at it from deepbit..might stick with this.  I do appreciate the donate option, seems to fit the rest of the bitcoin community.

to tell you the truth, i thought of doing 99% donation tonight...idk yet though.. =P

Edit: I also really love how 'reset' doesn't wreck your ever total, ty for that..

As a fairly small contributing member of the pool (mere 78Mh/s) I would personally like to say thanks for bringing more power over.

No problem at all =P
Earned .2 bitcoins on this latest block, now starting fresh on this one...lets see what happens.

[Sukrim]

Wohoo, I even found a block!

However what ppl need to understand is, that in a pool you are only competing against the pool's hash rate. So it's not the hashrate of the whole network (>1 TH/s) but the pool you're in (currently <13GH/s) that determines your block finding probability (as you can only find blocks within your pool by definition!), so it's way easier to find a block in a pool, as I would need 2% of 1TH/s to have the same chance of finding a block as in this pool currently (meaning more power than this pool combined!).

[Nythain]

Yeah, but its still a fun day brightener

[BitLex]

..it's not the hashrate of the whole network (>1 TH/s) but the pool you're in (currently <13GH/s) that determines your block finding probability (as you can only find blocks within your pool by definition!), so it's way easier to find a block in a pool,..

excuse me, but are you talking about blocks, or are you talking about shares?

it's ALWAYS the hashrate of the whole network (defined by the difficulty), in comparsion to your own hashrate, that determines your block (or hash) finding probability.

on a pool, you only find shares (hashes good for difficult1-blocks) more often, not blocks (hashes good for real-network difficult).

if you're mining on a CPU on your own, you'll probably never solve a block,
if you're mining on a CPU on a pool, you'll probably never solve a block,
there's just no difference.

[Sukrim]

To the outside/whole network, the hashrate that matters is ~13GH/s --> this is the rate that determines how quickly the BTCguild pool finds blocks.

Inside the pool I hash with 270MH/s --> ~2% of the pool's hashrate, meaning I discover ~2% of all blocks that the pool discovers.
However this is irrelevant to my income of course, as I get ~2% of any other block's income too.


So the probability of me showing up in the pool statistics is my hashrate/pool hashrate
The probability of the pool showing up on blockexplorer is pool hashrate/total hashrate
The probability of me finding a block on my own is my hashrate/total hashrate

Maybe this explains it better what I tried to say... (it looks a bit wrong in hindsight up there as well, but I'll leave it there for documentary reasons)