My guess if you've clicked one of the column headers and changed the sort order.

That's an SSL related error, which is served up by Cloudflare.  Considering you're the only person reporting it, I really can't say why you're seeing it at all.  What region are you connecting from?

Having 2 PH/s go away a few days before it sucks more ;/.

That vulnerability is being overblown to epic levels.  It requires something else on the server to allow an external connection to run commands on the local shell.  I'd call *that* the vulnerability, not bash.

No clue, I do not have any business deals or discussions with ASIC makers or cloud mining farms.  The only thing BTC Guild has ever done connected to one is when I was an official reseller for ASICMINER USB miners a year ago.

Translation:  Somebody who doesn't understand PPLNS compares per block rewards from one pool to another instead of actual earnings.  Also thinks 11 hours is sufficient to compare *any* pool to another.

With a proper test, you'd have found that BTC Guild will pay you *per block* about half of what Slush does once you have shares in every shift, and find them about twice as often.  The fees are identical, and BTC Guild pays NMC.  Statistically, it will provide better income over enough time as a result.  It is also unhoppable, while Slush's score system has been hoppable since 2011.

One last bump before the server becomes unavailable.  The various coin daemons will be shut down in a little under 24 hours, and the server lease will expire shortly after.  If you haven't made a withdrawal yet, do it now before the server is wiped clean.  Procrastinating until the last day is fine, but waiting until the day after will leave you with nothing.

EMC is *owned* by BFL, more than a "link" I'd say.

If you look at organofcorti's weekly analysis you'll find that the "Unknown" portion is mostly known.  He has done an excellent job at tracking down unknown block sources.

AFAIK, BFL never used BTC Guild for any testing.  They almost exclusively used EclipseMC or private pools.



Eligius has been very close to BTC Guild for the last few months, normally about 30% smaller in hash rate.  Slush just gets lucky once in a while.  When a small pool gets lucky, their size on that chart can more than double for a day or two.  Right now BTC Guild is 1-block behind Eligius and Slush over the last 4 days, which isn't unexpected, BTC Guild had pretty poor luck for about 3 days (then the last 24 hours had a decent spike).

Guild did have it's 2 PH/s user leave again in the last 2 days.  They seem to disappear for a few days every now and then.


I generally recommend http://blockorigin.pfoe.be/chart.php .  2016 blocks is a much better scale for comparison.  Luck still has an impact, but it's not nearly as significant as what you see on a 1-4 day chart.



On a slightly different note, looks like the 3-month luck will be joining the 100%+ club soon (the 2 oldest weeks in the 3-month average were pretty low)!

Stability issues is a funny way to hide the fact that they just don't like BTC Guild because I've never pulled any punches on calling Inaba/Josh out on his bullshit, and have always been vocal in my anti-BFL views due to their actions.  The last time the pool had an outage that affected more than a fraction of the pool was 9 months ago (January), and the last time any outage lasted over an hour was during the massive DDoS last October which went on for a few weeks (though most users were only affected for a day or so).

How cute, the lying scumbag is trying to say I'm the one full of shit.  (Also: Wrong thread, though if it's in the Pools subforum I'll see it no matter where you put it).

Just posting another reminder that users should *never* use the same password on BTC Guild as they use on any other site.  In the last few days, over 14,000 IPs have been banned for repeated registrations and login brute force attempts.  There are now databases tens of millions of unique username and password combinations that have been harvested from websites (large and small alike).  Using the same password on multiple sites that you consider to be important is multiplying your risk because it only takes one of them having a password leak to compromise all of them.


And as usual, set an email on your account to require somebody to have your email account as well in order to make account changes.  Lock your email and they can't change it.  Lock your wallet and they can't change it no matter how hard they try unless they actually break into your computer and steal your wallet.dat which contains the private key of your locked address.

0.0001, and they're executed every 2 hours.  The entire balance will be paid with that payment and no transaction fee charged to you.  However, DOGE and EAC are currently stuck until tomorrow, I need to do another transfer out of cryptsy and into the local pool wallet but do not have my cryptsy 2FA device with me today.

EDIT/CLARIFICATION:  "Tomorrow" is September 17th, which is technically today.  Basically the transfer will be done later this afternoon (probably around 4 PM [PST]), at which point any pending withdrawals for those coins will be executed.

Or anything with the words "Bitcoin" and "Trust" in the name.

There was an error earlier with the user login cache which wasn't being updated when a user changed their password (it also affected a few new registrations).  For users that recently registered, it has been fixed if they were not put into the cache.  For users that recently changed their passwords, you may need to change them again in order for the cache to reflect the change.

The earlier known instance of this error was approximately 6 hours ago.

256 or 512 will both work.  Even the default will work fine for them, it's only a small subset of miners (Dragon Miners and the rebranded copies of them) that actually *need* the difficulty changed to work properly.

Me too.  Just a little over a month before the first comment period extension ends, hopefully we'll be seeing a revised draft and yet another comment period after that.

There was a problem with changing wallet addresses earlier where any address entered would be rejected as invalid.  This error has been fixed.

Well the current block and that last block are sure feeling like a sucker punch after the last few weeks of good luck.


Figured I'd pre-empt the bitching about luck with some bitching of my own.