BTCGuild - the first 200Th pool? Pool Speed 200,281 GH/s
Some amazing growth hitting the network it seems. Very surprised that BTC Guild managed to make the climb from 100 TH/s to 200 TH/s before anyone else has hit 100 (not counting hardware manufacturers doing private mining like ghash.io). |
|
|
|
is merge mining still available on this pool?
Yes, NMC is paid to anybody on the PPLNS payment system. By default namecoins are not displayed, but they can be turned on in the Settings page. Whether this display is hidden or not, you are still generating NMC while on PPLNS. |
|
|
|
My 3 blades came today. Does anyone run them with bitminter/java?
The ASICminer blades have their own mining client built in. But it is rather primitive and only supports the old getwork protocol. The recommended way to mine with them is through a stratum proxy. You can set up Slush's stratum proxy on your computer, pointing it at BitMinter, and set up the blades to point to your computer running the proxy. You can get the proxy from: https://github.com/slush0/stratum-mining-proxyAnd run it something like so: mining_proxy.exe -o mint.bitminter.com -sp 3333 -gp 8332 (if you already have something running on port 8332 you may have to change the port number) In the blade configuration for user name use something like: username_worker:workerpassword,username_worker:workerpassword So if my user name is DrHaribo, my worker is Blade1 and its password is abc123, then I put DrHaribo_Blade1:abc123,DrHaribo_Blade1:abc123 This data must be entered twice. For host/IP put the IP of your computer running the stratum proxy. That IP must also be entered twice with a comma between. So if I am running the proxy on a computer with IP address 1.2.3.4 then I put 1.2.3.4,1.2.3.4 Now you are set for efficient mining. The Stratum proxy will receive block templates from the BitMinter server and use it to generate work for the blade(s). With the blade and computer on the same network the blade will be able to fetch new work very quickly. I believe you can enter data for another pool as backup as the data after the comma, instead of the exact same thing twice. You'll probably need to set up two stratum proxies on different ports to make this work. Maybe someone can confirm whether this is failover or 50/50 mining. Luke-Jr's latest bfgminer release has support for blades. It's basically running an internal GBT/Stratum proxy for the blade. Not quite sure how it works, or if it's known to be stable yet. The new blades also can connect via USB, but I'm not sure if that has opened up any new ways to communicate with the hardware or if it's still requiring a getwork->gbt/stratum proxy. UPDATE: Looks like as of right now it isn't yet included in the windows binary releases, so you'll have to build it yourself. README.ASIC has the instructions for using a blade with bfgminer. |
|
|
|
Ahh - so it's the last 24 hours worth of closed shifts. OK - I was wondering where my recent PPLNS earnings were diappearing to in that number. I was looking at it after about 10 hours of hashing and wondering why it was so low. Now I can see that it will take 32 hours or so before it really catches up with 24 hours worth of closed shifts...
It's one of the tricky parts about PPLNS, how to report 24H earnings in a system where your most recent ~8 hours of work are still being paid. The solution I use is an accurate method, but it's always a little unnerving for people to mine for a day and see a very low 24H earnings because they haven't yet hit 24 hours worth of fully paid work. |
|
|
|
Question about exactly what the 24 hour earnings number is showing - is this the trailing 24 hours, calculated once per hour, or is it somehow shift based?
24-hour earnings has always been an approximation, but it's a rolling 24-hours. Here's a little extra detail: For PPS earnings, this is simply PPS Shares in the last 24 hours (updated every hour) * Current PPS Rate. This is why PPS users will see their 24-hour earnings estimate drop *immediately* when the difficulty adjusts, rather than gradually over the course of 24-hours. For PPLNS earnings, this is a delayed 24-hour window. It takes the most recent closed shift as the starting point, and then counts back 24 hours worth of closed shifts. This is because the open shift earnings aren't complete and will continue getting paid for the next few hours even if you turned off all equipment immediately. |
|
|
|
Same diff, diferent shifts
9542 13 0.00000031465193
9506 13 0.00000034953468
Whats going on? Share count for shift chanched without anonce or what?
Shift length is increased whenever the pool grows too much and they start completing extremely fast. Increasing the share count for shifts has no effect on your earnings when measured in a 24-hour period (or even 12-hour period at the current speed of shifts), it only tweaks the variance you see during individual shift periods. With the rate of network (and especially pool) growth, it's requiring more adjustment than usual. Example: The pool has grown over 10% (nearly 20 TH/s) in the last 24 hours. |
|
|
|
NEW RECORD! Maximum shares hashed in a single block! Block info Block status Amount Found Duration Shares Confirmed
#254556 GENERATED 25.16120801 BTC August 27, 2013 353 hours 128 997 944 YES
#251886 GENERATED 25.20500000 BTC August 13, 2013 317 hours 110 230 535 YES
#246655 GENERATED 25.05267250 BTC July 15, 2013 276 hours 70 701 270 YES
#238120 GENERATED 25.20320001 BTC May 27, 2013 173 hours 89 141 122 YES
#142756 GENERATED 50.00100000 BTC August 27, 2011 432 hours 8 439 982 YES
Bitcoin Difficulty: 65,750,060Next difficulty (estimate): 74,469,157 2*Difficulty is not much of a record. I remember when Deepbit (or maybe Slush) had a round that was 8*D. BTC Guild, Slush, and Deepbit have all had rounds in excess of 10*D. Of course, that's 3 of the oldest pools, who have all at one point been at least 30% or more of the network hash rate, so they have had a ton of rounds in order to hit those numbers. |
|
|
|
Have you tried a catchpa, fail2ban, vary behavior on failed logins, etc..?
Captcha is an option, but would ruin the current easy to access interface. Fail2ban isn't all that great, and actually won't even work with Cloudflare as far as I know. The attacker is no longer affecting the site performance the way it was before now that I've found the main bottleneck that the site was facing during his largest hits. |
|
|
|
|
I'm asking friedcat about the new blade pricing. The real issue here is blades lose any kind of novelty/giftable factor. They cost too much, they're not fun to look at, they aren't a decent conversation starter. As stated on the disclaimer, these USB miners really aren't likely to make an RoI (they never will when measured strictly in BTC). It's possible to RoI if the USD price rises (and your options were buy an erupter or sell USD that day, rather than just hold onto the BTC), but that's a gamble/investment choice.
If the margins aren't there for me, I won't sell it. It's similar on the USB miners. There's a real disconnect in how retail is supposed to work, and how these group buyers are running the business. It reminds me of cheap chinese knockoffs that sell products for pennies on the dollar in an attempt to make it up with volume. I invest my own money into buying this inventory, and I need to make enough markup to justify getting stuck with units plus time/shipping/supplies.
|
|
|
|
I have a question, why is deepbit at 11% of the bitcoin network? the hashrate is very low on the pool site but it shows that deepbit is solving blocks faster than 50btc....
Deepbit doesn't tag any blocks to allow sites to properly identify them. At the time blockchain.info was designed, the vast majority of blocks with no tag did belong to Deepbit [which was 30-40% of the network at the time]. As a result, there is still some legacy code in there that has an extremely high false positive rate where it credits Deepbit for blocks. I agree with the statement from Blockchain reported Deepbit blocks are not all solved by Deepbit. But if there is a piece of code which reports all untaged blocks as Deepbit blocks then we should not see any solominer blocks which is not true. There are also untaged blocks from solominers reported. My guess is Deepbit is very well connected within the network it's like a supernode and relay only so many blocks fom others with IP addresses which are known as Deepbit IP addresses. Deepbit is on hetzner, they're not anywhere near what would be called a "supernode". Best guess is there's simply a *huge* number of IPs which blockchain.info automatically assigns as "Deepbit" due to the number of Deepbit blocks that used to be relayed through them frequently. |
|
|
|
I have a question, why is deepbit at 11% of the bitcoin network? the hashrate is very low on the pool site but it shows that deepbit is solving blocks faster than 50btc....
Deepbit doesn't tag any blocks to allow sites to properly identify them. At the time blockchain.info was designed, the vast majority of blocks with no tag did belong to Deepbit [which was 30-40% of the network at the time]. As a result, there is still some legacy code in there that has an extremely high false positive rate where it credits Deepbit for blocks. These days, a huge number of blocks showing up as Deepbit actually belong to ghash.io (BitFury). |
|
|
|
I see the continued stress on the portal. Sorry this is happening, but thank you for your work in resolving it. I'm curious how they get thru cloudflare?
This isn't a script kiddy attack. He is absolutely using his own attack kit to do this. I've put in many barriers to entry to try to catch him, and every few days the attack evolves to bypass it. He is able to get his attack to pass the browser verification check done by Cloudflare. I'm still stumped at what the person is trying to achieve though. A completely untargeted attack (the database leaks he's using as username/password sources are bigger than any BTC site). If he does manage to get an account, odds are it will be abandoned. If not abandoned, it will probably have an email setup that they'll have to crack to change the wallet. And any account with a decent value is sure to have wallet lock enabled so there'd be no way to steal the coins even with both the account and email compromised. |
|
|
|
|
Attack to break into user accounts is still hitting on and off. I'm continuing to refine my detection as best I can, but there's still going to end up being 500+ attempts to authenticate per second when he hits the servers, and if it starts lagging, it creates a continuous delay. A few more alterations were made to the login server which will [hopefully] keep the site moving along during these events.
|
|
|
|
Is the website down again?
I'm not getting a cloudfare error/ban page, just "webpage unavailable" from chrome...
Website is fine. Make sure you're using www.btcguild.com, not 'btcguild.com'. btcguild.com points to the getwork server, which then redirects you to the proper website address. Since the getwork server is down, that redirect is broken. |
|
|
|
|
As stated in the previous page, if your IP has been banned by Cloudflare, please send me an email or a PM with your IP so I can remove the ban. In the last 24 hours the pool has banned over 30,000 IPs, and the list continues to grow. The only way to get on this list is if your computer is infected, or you have made many failed attempts to login to your account.
A lot of changes were made to keep the site from collapsing when the attack is in full swing. Additionally, the attacker has a significant number of zombies on certain IP ranges, so the IP banning is much more aggressive on anybody failing to login to an account on those IP ranges.
Regarding getwork: Getwork has been at an end of life level of support for almost a year now. Right now the single server still offering getwork is completely crashing to the point it needs a hard reboot. I will be putting it back online within the next hour, but it will probably not be coming back up the next time it fails.
|
|
|
|
are the ongoing attacks why the api is not working well today?
Unfortunately, cloudflare's "under attack mode" does tend to break the vast majority of API programs for IPs that haven't managed to get whitelisted previously. I had to leave this mode on since I was away from a computer for a large chunk of the day (outside of my emergency laptop). |
|
|
|
The latest round of block erupter inventory has arrived. Backorders will start getting cleared out tomorrow and be fully cleared by Thursday. An extension of ASICMINER's coupons will also be available for the remaining orders that were placed at 1.05 BTC last month. These coupons will be made available on Monday, and start shipping Tuesday [Monday is a holiday in the US so no mail will be moving].
These the new improved 'pink' versions ?  Sadly, I've just finished unpacking everything...all black again  . I guess I'll have to delete my promotional ads for "Complete your set today" with a 10% premium on the new colors (/s). |
|
|
|
I noticed on the account page that NameCoins unconfirmed rewards was temporarily N/A. Does that mean we aren't currently merge mining and will receive no NameCoin? Or that we just don't have a nice unconfirmed indicator?
Slush's pool stopped merged mining when the getwork servers were shut down. Slush has not stated any plans to add NMC merged mining to the Stratum pools. |
|
|
|
|
The latest round of block erupter inventory has arrived. Backorders will start getting cleared out tomorrow and be fully cleared by Thursday. An extension of ASICMINER's coupons will also be available for the remaining orders that were placed at 1.05 BTC last month. These coupons will be made available on Monday, and start shipping Tuesday [Monday is a holiday in the US so no mail will be moving].
|
|
|
|
The website has been getting "attacked" on & off all day, yes. I have to occasionally switch the settings to 'Under Attack' mode which uses those browser verification pages. The pool itself is unaffected though.
What's the point? Say they confirm a username or two, are you gonna sit back and allow account modification? Obviously their goal is to steal money from accounts which haven't utilized any of the available security settings. I honestly have no idea what they expect to get, the amount of effort they've put into this attack (they've been doing this on & off for months), there are definitely more lucrative possibilities than trying to break into a random account. |
|
|
|
|
Show Posts
