Lower performance, less support, less time spent upgrading and maintaining servers (both frontend and backend).  Ghash.io's stability is abysmal by any reasonable standard.  The only reason they're so big is more than 50% of their speed is a private farm of ASICs since they're acquiring them basically at cost from BitFury.

Running a remote proxy has the same problem as trying to use getwork on a remote server.  You are losing performance if you attempt to do so.  Proxies are not difficult to run, and can be done on virtually any level of hardware.

You should ALWAYS use a Stratum Proxy for ASICMINER Blades/Cubes.  They are not designed for working on remote servers via getwork and you will lose a significant amount of performance doing so.  Run a stratum proxy on the same local network as the blades/cubes in order to get maximum performance.

Absolutely nothing has happened in the last few weeks, so...you're welcome?

The only thing that has happened since your last post about the problem is I drove 450 miles with a car full of electronics and 2 cats.

There's a giant graph on the PPLNS Stats page for luck.  24 hour earnings for PPS are accurate except for the first 24 hours after a difficulty change.  24 hour earnings for PPLNS are accurate, except they're on an ~8 hour delay (uses the last 24 hours worth of closed shifts since open shifts are not done getting paid).



There was a 5 minute outage roughly last night due to a backup script on the DB server eating up all the space on the drive.  Most mining software should have automatically reconnected. 

Are you sure you're using the right worker name?  Not using a '.' instead of a '_'? or something like that.  There is absolutely nothing wrong on the servers (~24,000 connected users).  Nothing has changed in weeks either.

198.245.63.145 is the verification server.  You're only on that server for the very first submission.  Set your miner to connect to the URL it's redirecting you to instead and see if that fixes it.

Good evening,
  It *is* on your end, otherwise I'd have an inbox with a couple hundred emails and a pool with a ton of speed missing.  My only guess is your system doesn't like the redirect DNS, since you're connecting to the verification server, it's sending you the redirect, and then 1 second later it's complaining about not responding with the old pool URL in there.

  Try connecting directly to the redirection server?

Definitely a problem on your end.  A significant number of users use the slush stratum proxy with BTC Guild and the speed has been stable/growing consistently for weeks.  Either you have a bad username and it's kicking you off, or you're not authorizing a worker and it's disconnecting you after a while of holding open an idle connection.  Other problem would be routing issues on your end between you and Chicago.

A huge majority of GHash.IO's speed is from their private farm.  They are the largest single miner in the network at this point.  Their service has been unreliable and support is non-existant, mostly because they have no incentive to actually keep their public pool operating smoothly.  BTC Guild isn't going to compete with someone like that.

These articles miss the point.  They're calling addresses people.  This would be the equivalent of saying 90+% of all US dollars are owned by 100 people (probably fewer), because BANKS are the ones holding the dollars for the vast majority of all currency.

A huge number of those stockpiles are likely wallets for exchanges.

Except running a blade on remote getwork is inefficient and costs you a few % of your speed since they aren't able to multi-task when submitting shares.  They also submit every diff=1 result regardless of server requirements, eating up even more time.  If you have a blade and do not run a local proxy, you're losing out on your potential.

Most botnet computers don't even hash at 1 MH/s, just FYI (speaking from significant experience dealing with the damned things).  Most people with i5/i7 computers know enough to see their computer is running slow as dirt and the fan is always spinning fast.  Not saying they're immune to it, just saying the vast majority of high end CPUs are not in botnets, they're mostly made up of low end.

Also was only referring to *active* CPU miners, rather than all the infected computers on earth.  Most botnet operators aren't touching BTC because a CPU miner is not worth as much as a spambot/ddos slave anymore at modern difficulties.

One KNC Jupiter is likely more powerful than every CPU miner combined (including botnets).

Specific time payouts aren't currently on the list of things being tweaked.  It may come later.  I'm in the process of moving over the next week and a half, so I'm trying to pick my battles carefully.

NMC payouts are now back and running.  They've been updated to now payout the highest multiple of your threshold (IE:  Set your threshold to 0.10, if you have 0.23, it'll pay 0.20).  BTC payouts will *offer* this method of automatic payouts in the near future, but the default will still pay the amount you set as your Auto Payout threshold.

NMC earnings are expected to return in roughly 24 hours.

I'm now remembering something Luke-Jr mentioned.  Blades do not multitask, so when they submit a share/complete a getwork request, they are not hashing until a response is received.  This would likely cause a somewhat noticeable impact on overall performance (few percent at minimum) since blades also send back every diff=1 result.

3 batches of NMC payouts were just sent out to see if that has any affect on the payout node getting stuck on an orphaned chain.  Additional namecoin earnings are still disabled for at least 24 hours to keep an eye on the status of all the nodes.

Since those are BTC Guild ports, have you tried resetting your stats on the dashboard?  BTC Guild's speed estimates are based on an hour if you've been mining that long.  If you had issues, it takes a full hour for those issues to stop affecting your average speed estimates.

It's normal. Look at the luck chart on the bottom of the PPLNS Stats page.