Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 13. (Read 379084 times)
August 28, 2011, 02:48:09 AM
Is there something wrong with the stats website? I haven't seen updates in a few hours.
August 27, 2011, 11:04:25 PM
"...has now been optimized to handle much more load then before."
Like a bukakke robot, if you will.
August 27, 2011, 08:21:50 PM
Are you planning on implementing difficulty 2 or >2 shares soon? I was really looking forward to that feature when you first announced it.
P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves
)
P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves
)I doubt he will because load is not such a big deal anymore. The code, pushpoold i think it is called, has now
been optimized to handle much more load then before.
August 27, 2011, 08:01:05 PM
Are you planning on implementing difficulty 2 or >2 shares soon? I was really looking forward to that feature when you first announced it.
P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves)
P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves
) 
August 26, 2011, 11:25:51 PM
I'm pleased to announce the return of EU (DE) servers. These servers are actually running on new load balancing setup that should completely eliminate long poll delays due to overloaded network interfaces. You can use the new servers by just entering 'btcguild.com' as the server [not uswest./uscentral., just btcguild.com). If you want to make sure you always point at these servers unless they are removed, you can also use de.btcguild.com
August 26, 2011, 01:19:02 PM
Stats are updating again, was informed of the apache exploit regarding the request range header. Restarted apache during a stat update, which sets a switch to stop the server from running it multiple times simultaneously. Fixed the switch and now everything is back to normal.
August 26, 2011, 12:06:00 PM
I'm adding a new check to the new block code to prevent this from happening in the future. We had a 600 share round that lasted barely over 2 seconds, so US West hadn't sync'd the round before the round ended.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
Did we actually had a 6:45 one, 10+ million shares? is that some kind of record?
Nope. It is actually happened before and to multiple pools. It is almost becoming common to see
one every month or what not.
Mineco completed a 11.9 million share round recently....that sucked.
August 26, 2011, 11:21:43 AM
Nope. It is actually happened before and to multiple pools. It is almost becoming common to see
one every month or what not.
one every month or what not.
Well, that puts us on the negative on this round again. Im kind of getting use to it.
August 26, 2011, 10:52:31 AM
I'm adding a new check to the new block code to prevent this from happening in the future. We had a 600 share round that lasted barely over 2 seconds, so US West hadn't sync'd the round before the round ended.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
Did we actually had a 6:45 one, 10+ million shares? is that some kind of record?
Nope. It is actually happened before and to multiple pools. It is almost becoming common to see
one every month or what not.
August 26, 2011, 10:51:14 AM
I'm adding a new check to the new block code to prevent this from happening in the future. We had a 600 share round that lasted barely over 2 seconds, so US West hadn't sync'd the round before the round ended.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
Did we actually had a 6:45 one, 10+ million shares? is that some kind of record?
August 26, 2011, 10:23:57 AM
I'm adding a new check to the new block code to prevent this from happening in the future. We had a 600 share round that lasted barely over 2 seconds, so US West hadn't sync'd the round before the round ended.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
all is forgiven. especially when i squeaked in 5 shares out of 663 which resulted in a .377 payout. :-)
August 26, 2011, 10:20:41 AM
I'm adding a new check to the new block code to prevent this from happening in the future. We had a 600 share round that lasted barely over 2 seconds, so US West hadn't sync'd the round before the round ended.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
The new check will ignore these server sync issues if the total shares of a round are under 15,000 [which is about 1 minute on one server].
The blocks from last night have now been properly calculated.
August 26, 2011, 09:23:17 AM
Wow. We're on a super long 6 hour block!
And today was looking so good til now.
And today was looking so good til now.
Hopefully is another of the recurrent hang ups of the scripts that report the data.
One can only hope or today is basically shot.
The odds of us having an 8 hour block with the current pool speed is really really tiny...
By using this website: http://digbtc.com/ it seems like that is an awful lot of unclaimed blocks
for btcguild not to have grabbed one or more.
August 26, 2011, 08:04:32 AM
Wow. We're on a super long 6 hour block!
And today was looking so good til now.
And today was looking so good til now.
Hopefully is another of the recurrent hang ups of the scripts that report the data.
August 26, 2011, 07:39:18 AM
Wow. We're on a super long 6 hour block!
And today was looking so good til now.
And today was looking so good til now.
August 25, 2011, 03:05:22 PM
finding a block isn't really a function of the number of shares found
Oh really? What is it function of than? Number of shares AND bitcoin network difficulty, I hope?
Here is some homework for you. Figure out using some incomprehensibly correct statistic with page long formulas what are the odds of tossing a fair coin 4865 times and getting only at most 2275 tails .
Now please tell me how accepting D shares and solving a block (or not solving it) is different from tossing a fair coin, where D is difficulty.
The network is not flipping coins over and over again. Let me say it again, this time more clearly. There is no fucking coin.
The network is generating what we hope is a more or less random number, trillions of times per second. Can you really not tell the difference between quintillions of hashes vs. thousands of coin flips?
Pardon me for not being startled by the difference between 2,298/10,000,000,000,000,000,000 vs. 2,432/10,000,000,000,000,000,000.
August 25, 2011, 02:15:40 AM
There is a problem with confirmed rewards in solid coin mining.
August 25, 2011, 12:49:34 AM
why mining solidcoins on btc guild makes so many stales share ? up to 10 % !! 
August 24, 2011, 09:30:32 PM
PPS is 10% on DeepBit... I have a feeling you're going to end up with the same percentage.
Cheers,
Kermee
Cheers,
Kermee
If I offer PPS, it will be a lower rate than DeepBit, since my base proportional rate is 0% (2.5% for comparable deepbit features/invalid insurance). Tycho's PPS rate is set at a rate of 7% higher than his base rate, which seems to be about where our luck has been from inception (if I use Vladmir's numbers, I _THINK_ we're about 6.5% behind on total BTC production from expected average if you measure June 1st-August 21st, although that discounts a high luck day, and assumes invalid blocks should be 0% rather than ~1%). Ideally in the long run, luck zeroes in on 0% as the time frame you use grows, so I may offer it even lower and just eat the loss assuming BTC Guild stays alive long enough to get back to the 0% average.
August 24, 2011, 09:02:03 PM
PPS is 10% on DeepBit... I have a feeling you're going to end up with the same percentage.
Cheers,
Kermee
Cheers,
Kermee
Jump to: