Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 137. (Read 379078 times)

Whoops, sorry guys, i'll power down my 2.5 Mhash Asus Eee monster, should fix your connection problems :p

Everyone.... everyone.... take a breath. It will be OK.   

Let me recap the entire thread for everyone who is just joining in. IF you have read everything and now whats going on, you can skip this post.

When eleuthria set up his mining pool less than 20 days ago, he never imagined it would grow so fast. The pool basically went from 0 to 250 gH/sec. This is simply too much for the server he was testing this pool on. Eleuthria simply had no idea that having 0 fees and such an awesome interface would attract so many miners to his pool.

Facts:

• You choose what percentage you would like to Donate, this means you can choose 0%
• If you donate 2.5% or more, you can take a payout immediately after a block is solved. Even if the block is later found to be invalid!
• If you donate 0 - 2.4% you have to wait for the Block to be confirmed before you can take a payout. A Block is confirmed when 120 additional Blocks have been solved after that. (The additional blocks include any blocks solved anywhere in the world.)
• The payout is based on the number of shares your miners submit during a Round.
• Eleuthria is setting up a new server. After this is complete the current "idle/rpc" errors will go away. Until then, I would suggest to setup your miner to connect to a backup pool--this way you will be constantly mining somewhere if BTC Guild goes down for a bit.
• After the new server is setup, new registrations will be open again.
• The new server is supposed to be set up within a week (hopefully this weekend).
• Eleuthria is extremely active on this forum and on IRC chat (freenode.net  #btcguild )
• This is the best pool I have ever seen.

How the pool shares work:
A share is every "Accepted" hash. A Round is how long it takes for the pool to solve a block.

Example:
Lets say a round takes 90 minutes, then a block is found. During those 90 minutes all the workers and miners in the entire pool submit 300,000 "Accepted" shares. First the pool takes the 50 Bitcoins and divides them among all the shares:
50  / 300000  =  0.0002 BTC per share.
Now, lets say that during that same 90 minute Round, your workers submitted 250 of those 300,000 shares. You would get paid:
0.0002 BTC per share  *  250  =  .04 BTC paid for that round. Makes sense, right?


New Example:
In this round there are 275,000 shares. Right now each share is worth 0.000181818 BTC. Your workers have been mining for 120 minutes and you have 300 "Accepted" shares in the pool. If a block were to be found at that instant, your payout would be:
(50 / 275000) = 0.000181818 BTC * 300 = 0.054545 BTC
Please note: this is how the "Estimated Rewards" section of the "My Account" page on BTC Guild works.
BUT you decide to stop mining. You still have 300 shares in the pool, but the other miners keep working and keep submitting more shares. Finally after 180 minutes a block is found. In total, there are now 395,250 shares submitted during that round. This means that each share is worth 0.0001265 BTC
You still have 300 shares submitted during the round (even though you left early) so you would still get paid:
0.0001265 BTC * 300 = 0.03795 BTC


I know this is pretty basic, but I hope it helps new users to Bitcoins and Pools.


1KFvGaeqNVWiBgMdTHXDWMqBnw1nPKjFPq

More Ghash/s means your rewards will go down, unless you're the one adding it. I have dropped 200Mhash/s because of the disconnect and idle issues on all of my miners as well.

So you have to take all of that into account.

I dont have that many idles... 5 an hour or so?
What I did notice is that my estimated reward is lower... which may be because one of my external workers is offline, but its still weird...

Yes, many disconnects and miner idle notifications. I suppose related to the server load. Work idle once every few seconds at worst, 5-10 times a minute at best.

So we move to another pool, or wait for others to move first to bring down server load. Maybe the new dedi will be ready this weekend though.

Y
I'm seeing the same. Multiple idles popping up once every 90 seconds or so.

I am also getting quite the idle miner warning.

EDIT:

How has this pool gone from 240 gh/s to 267.24gh/s in around 12 minutes?

my heart jumped of joy when I saw this:
Estimated Rewards    171.23255814       Estimated reward from current round.

But guess its a calculation glitch

that one is nice. 

it's 7 different workers on 4 different machines and 3 different OSes and it's only your pool.
overload extreme.

however, maybe i'll check back later, but it's useless for me right now.

No idea what the problem is on that one.  We've still got about a thousand workers running which aren't experiencing anything close to it.

well,
i really don't mind to "..see idle warnings/RPC errors from time to time..",
but check this out.
and that's only 4hours

Please read the giant warning on the front post, or the last few pages of the thread.  The server is absolutely overloaded.  Even after shutting registration, the people already in the pool have been adding speed/turning workers back on and pushed it 30 GH past what it was when new users were stopped from registering.

It would diminish our reward a bit, but not eliminate it.

something's wrong,
i get a "warning: job finished, miner is idle",
followed by "Problems communicating with bitcoin RPC"
every minute or so, which is.....not so good.
poclbm that is on ubuntu and a GUIminer on windows,
phoenix doesnt tell me those warnings as often, but miners stop working randomly (every few hours) with a "work queue empty, miner is idle" (which is why i switched back to poclbm).

guess i'm currently losing a lot more than i'd pay in fees on other pools.

Correct me if I'm wrong in this, but wouldn't that defeat the concept of the invalid insurance/reward those of us that donate 2.5% or more get?

Oh, heh.  I wasn't suggesting that we had consecutive invalid blocks.  There was one before, round 8.

Block 151 has already been solved. So far it's not showing invalid to me.

OH CRAP

Check out block #150

That was also the number of pokemon originally.  Coincidence?  I think not.  Maybe we will see a dimensional rift and daemons from the other side in short order.   

Looks like we got a second invalid block.

Any thought of rolling the shares from the invalid round into the next round?