Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 252. (Read 903150 times)

I dont own any ASIC but Ive accidentally left some BTC in my guild account.  Any chance I could close my account and get the balances cleared.
Unfortunately BTC has progressed beyond some of the older miners ability to earn and I got the auto payout mixed up and it left some behind

well now i rememebr why my miner shuts down on my. either that or its my miner it self. bfgminer i think its called. (windows 7)

Sorry to those on one of the two EU Stratum servers.  A workaround/fix is being tested for the Slush Stratum Mining Proxy and minimum difficulty settings.  Two restarts later, and the fix seems to be working.

Other servers will have restarts over the next few minutes as the fix is applied to each stratum server.

Thanks Eleuthria!  Was able to jump back in and make worker changes. All good now 

The website has had no issues on my side, but there have been issues changing workers, related to one specific server not acknowledging the requests.  That should be over now.  Mining software should have redirected to the alive servers fairly effectively (based on pool speed, that did happen successfully).


Just an update, there is a flaw in the Slush stratum mining proxy that was found recently.  The first method a client is supposed to send with stratum is a mining.subscribe method.  This tells the server to start sending you work at each update, and sends you the default server difficulty (1).  Later on, slush added the ability for the proxy itself to authorize as a worker, rather than passing worker authorization from the software pointed at the proxy.  This authorization happens BEFORE the mining.subscribe method is sent, and causes a conflict.  When you auth the worker, it sends you the worker minimum difficulty and work to start on.  THEN the proxy sent the subscribe, which by default sends server difficulty (1).  This is confusing the mining proxy and causing significant lowdifficulty rejects.

A fix is being pushed out today to work around this flaw in the stratum proxy.  A temporary workaround for users is to leave your minimum difficulty at 1, or simple don't run the proxy with '-cu and -cp' arguments.

Are the current site issues (refuse to load, not even cloud fire, or issues changing worker settings) related to today's dbase copying or is this another attack/site issue. Also when I was able to get in, the pool stats showed the US stratum server status as "Dead:105m". Related?  From BFGMiner's status though, it looks like I've been able to hash away and submit status updates without failover on stratum.btcguild.com.

ok, cool, just curious.

It probably hasn't been scanned in yet.  It sometimes takes a day or so before it shows up in the tracking system.  If your order was packed after ~3 PM yesterday, it wouldn't have been scanned in yet.  Yesterday's pickup was a bit early, and today's pickup hasn't shown up yet.

how come package tracking isn't working for my latest order. Says "Information for this number isn't available at this location." doing something differently?

Latency has a very little impact on earnings, and it's easily outweighed by the uptime at the Chicago colo.

I can provide colocation space if he wants (reasonable prices as well!)

I need a server closer to my location. Any plans to expand somewhere eastward, say Florida?

Yep.

So hard to /Troll these days.

/Sarcasm

Keep up the good work. Go BTCGuild! 

The new server for the database has been delivered to the colo this morning.  The new server is planned to go online at 5 PM (PST) on Friday.  This will require a brief restart on all pool servers in order to redirect them to the new database.

The website may have a few lag spikes during the next 24-48 hours as parts of the database are copied over to the new server.  Once everything is moved, this should drastically reduce the current lag spikes that happen about twice per hour, and the minor lag spikes that happen about four times per hour as a result of all the scripts that are needed to keep the statistics updated.

Ah, sarcasm, a difficult concept to master.  
Thanks,
Sam

Satoshi has nothing to do with the code any more ... it's full of ... other ... non-Satoshi ... code now

He was being sarcastic

People that have solo mined with high hash rate ASIC's have setup their own pool software to do it.

The Bitcoin-QT client has no Stratum protocol nor variable difficulty.

Edit: All I am trying to say is that solo mining 23,506.34 GH/s is no trivial task.

Nonsense, Qt can handle anything you throw at it. To say otherwise is to doubt Satoshi, and I will not have it.

/Troll