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

Im hoping this latest 3 hour block is the same thing


guess not  

Usually things ebb and flow.  our luck has been ebbing for weeks, I would like to see it start flowing again!!

Sync issue on US East again last night from a 22 second round, caused our blocks to not announce for a few hours.  Just fixed it and the blocks have been announced.  Our luck had a -massive- swing last night from around -7% to +8.3% since this difficulty kicked in.

I've started to single out suspect accounts which are either being used by a lot of IPs, or showing a large number getworks with low return rates/speed (likely to be a very large CPU mining operation).

I've started to single out suspect accounts which are either being used by a lot of IPs, or showing a large number getworks with low return rates/speed (likely to be a very large CPU mining operation).

While CPU mining is not banned from BTC Guild, they are discouraged when used in large numbers.  They are ineffective, slow, and anybody running them is likely doing so either behind the owner's back (computer lab/client computers of an IT company), or by misinforming the owner's ("They're on 24/7 anyway").

There is absolutely no situation I can find where it is cost effective for somebody to be running a CPU server farm for mining.  Somebody is going to eat that bill, and I highly doubt its the person running them.  By running these huge numbers of CPU miners, you are negatively impacting the rest of the pool.  Each CPU miner is consuming server resources similar to a GPU miner.  Long poll sessions are a fixed cost for the pool regardless of the miner speed.  Additionally, most of these CPU miners are asking for work every 5 or 10 seconds, even though they take many minutes to send something back.

If your account gets singled out, you will see a large warning on the My Account page directing you to a special server address which has long polling disabled.  This special server was put in place to keep the primary servers healthy and running stable.

Miner starts a request to long polling URL with GET method and same basic authorization as on main connection.
This request is not answered by server until new block is found by bitcoin network.

Do you have some kind of IP blocking enabled, where for example if someone from the same IP is trying to mine from two separate BTCGuild accounts, it blocks the second one ?

I made a second test account and cannot for the life of me figure out why none of my miners work with it, even when using the EXACT same arguments as my original workers that are mining just fine!

Do you have some kind of IP blocking enabled, where for example if someone from the same IP is trying to mine from two separate BTCGuild accounts, it blocks the second one ?

I made a second test account and cannot for the life of me figure out why none of my miners work with it, even when using the EXACT same arguments as my original workers that are mining just fine!

Eleuthria: Is it possible to show corrupted shares as a separate stat from stales instead of a single stale count? Since many of us are overclocking our cards, it would be helpful to know if some of us have overdone it and actually wasting resources and submitting corrupted shares.

I've started to single out suspect accounts which are either being used by a lot of IPs, or showing a large number getworks with low return rates/speed (likely to be a very large CPU mining operation).

While CPU mining is not banned from BTC Guild, they are discouraged when used in large numbers.  They are ineffective, slow, and anybody running them is likely doing so either behind the owner's back (computer lab/client computers of an IT company), or by misinforming the owner's ("They're on 24/7 anyway").

There is absolutely no situation I can find where it is cost effective for somebody to be running a CPU server farm for mining.  Somebody is going to eat that bill, and I highly doubt its the person running them.  By running these huge numbers of CPU miners, you are negatively impacting the rest of the pool.  Each CPU miner is consuming server resources similar to a GPU miner.  Long poll sessions are a fixed cost for the pool regardless of the miner speed.  Additionally, most of these CPU miners are asking for work every 5 or 10 seconds, even though they take many minutes to send something back.

If your account gets singled out, you will see a large warning on the My Account page directing you to a special server address which has long polling disabled.  This special server was put in place to keep the primary servers healthy and running stable.

I haven't been home most of the day, so I can't be more specific about the times, but my 2 workers keep reverting back to my backup pool (not btcguild), I think they have been doing that most of today, they are pointed to log on us.btcguild, anyone else having those issues?

Once again, thanks for a great pool!

Fixed the problem with payout processing.

I've also had quite a few emails regarding the new stats "Last Block Awarded" and "Shares Since Last".

Last Block Awarded is just as it sounds.  It's how long since a block was announced and the rewards were allocated to accounts.  Everytime that timer resets, you will have new confirmed/unconfirmed rewards (assuming you participated in that block).

"Shares Since Last" is a compromise.  Many people were upset that "Round Shares" was removed.  The increasing counter provided some sign that the server as a whole was continuing to accumulate shares towards the next block.

The value of Shares Since Last will be equal to:  The number of shares since the last block announcement, plus one hour.  So if a block was announced 45 minutes ago, Shares Since Last will contain 1 hour and 45 minutes of shares.  There may be any number of unannounced blocks that are waiting to be announced (solved within the last hour).  It is possible there are no blocks in that number as well.