Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 353. (Read 903150 times)
January 17, 2013, 10:10:56 AM
No block for 6.5+ hours....really?
January 16, 2013, 05:40:13 PM
The merged mining server had about 10 minutes of downtime due to a problem at the datacenter. Everything seems to be back up and running at this time.
January 13, 2013, 06:39:55 PM
just now hooked back up on their own, thanks
January 13, 2013, 06:36:44 PM
are we down?
my miners have not been able to connect last half hour or so
my miners have not been able to connect last half hour or so
Private server redirected about a half hour ago. You may need to use the default btcguild.com:8332 temporarily if your DNS didn't update with it.
Other Update:
There was a brief restart of 2 getwork servers and the primary stratum server. Stratum downtime was only a few seconds, getwork about 1 minute. This was to implement a few quick fixes to the Stratum server, and also implement minor load balancing to help speed up longpolling via Stratum. The old code was experiencing some slowdown after a few weeks of continuous running. This should bring stales back to extremely low levels for miners with good latency.
January 13, 2013, 06:36:22 PM
are we down?
my miners have not been able to connect last half hour or so
my miners have not been able to connect last half hour or so
January 10, 2013, 09:15:05 AM
And that shows why i mine here. Good guy and honest.
January 09, 2013, 11:36:18 PM
PPLNS users got a big boost to earnings from it. Time to figure out who the real owner is and send them back the part that hasn't already been credited to accounts.
I am curious what easy method you can use to determine how much was legit fees versus a possible mistake amount of fees?
Part of me thinks you should keep it unless someone comes to you. But maybe i do not realize how easy it might be to set aside the mistake amount versus hours of work involved for you to chase someone down.
Basically i am curious how u go about it.
The person who created the bad transaction made a post (and a raw transaction in an attempt to try to get a lower fee version on the network to possibly "double spend" the transaction with the appropriate fee), and confirmed their identity.
102 BTC of the overdone fee was returned to the original wallet the transaction came from in this transaction: http://blockchain.info/tx-index/42579467/4a0fe8cb78b19778a49d171642649c9ee25453ed206894c88b049d0ee7939a0f . The rest was already credited to PPLNS miners (rounded up to 9 BTC).
Luckily you can always see the originating address, so it was risk free to send it back without worrying that it was going to the wrong person. I just needed confirmation it was safe to send back to the original address, otherwise it would've been harder to go about sending the money back (https://bitcointalksearch.org/topic/m.1445272).
January 09, 2013, 11:33:38 PM
PPLNS users got a big boost to earnings from it. Time to figure out who the real owner is and send them back the part that hasn't already been credited to accounts.
I am curious what easy method you can use to determine how much was legit fees versus a possible mistake amount of fees?
Part of me thinks you should keep it unless someone comes to you. But maybe i do not realize how easy it might be to set aside the mistake amount versus hours of work involved for you to chase someone down.
Basically i am curious how u go about it.
January 09, 2013, 11:19:14 PM
PPLNS users got a big boost to earnings from it. Time to figure out who the real owner is and send them back the part that hasn't already been credited to accounts.
January 09, 2013, 11:12:54 PM
Did you pay out the transaction fees from this block? http://blockchain.info/block-index/333825/00000000000002327a29e7fdf539e773e960e631622c46cf859efebdbb78f9a8
It had over 111 BTC in fees, over 4 times the block reward.
It had over 111 BTC in fees, over 4 times the block reward.
January 07, 2013, 09:05:04 PM
A nice stream of blocks helped speed up confirmations of the cold->hot wallet transfers. Automatic payouts were processed twice this hour to catch the ones that failed today and yesterday.
January 07, 2013, 08:34:57 PM
Some payouts failed today. Apparently a huge number of users who haven't been active/never withdrew coins in the past few months decided to come back and finally withdraw, cleaning out the hot wallet. I'm refilling the hot wallet right now, and the bad payouts have been cleared from payment history.
December 31, 2012, 05:40:28 PM
I've noticed a lot of users have returned that were absent after the DDoS, but the split between Stratum and Getwork started shifting back to getwork. When the servers were initially recovering, the Stratum redirects were not pointing to the proper IP, and your miners may have defaulted back to getwork.
If you're using a native Stratum miner and you're seeing any of the following:
1) Warning about not using stratum ("Mine more efficiently" notice at the top of each page)
2) Not having shares show up as PPLNS
3) Seeing "pool # not providing work fast enough" in cgminer output
Please give your miner a quick restart if you see any of the above when using a native stratum miner. It should redirect back to the Stratum based server.
If you're using a native Stratum miner and you're seeing any of the following:
1) Warning about not using stratum ("Mine more efficiently" notice at the top of each page)
2) Not having shares show up as PPLNS
3) Seeing "pool # not providing work fast enough" in cgminer output
Please give your miner a quick restart if you see any of the above when using a native stratum miner. It should redirect back to the Stratum based server.
December 23, 2012, 11:28:56 PM
I've deployed a fix to the generic 'btcguild.com' getwork server. I brought back the 3rd getwork server, and pointed the default DNS to that server, but the redirect for Stratum was still using the old IP from before the DDoS. If you're using a native stratum client, you may need to restart it to get back on Stratum. This shouldn't have affected too many users, since native clients should default back to getwork if the stratum redirect fails, and most proxy users had the correct IP already redirected from before the 3rd server came back online.
December 23, 2012, 12:33:55 PM
The getwork servers had a brief restart today to put in a change that I have been considering (and tried once in the past) for quite some time. Ufasoft-based miners are no longer allowed on BTC Guild getwork servers. For almost every botnet I have banned on BTC Guild, all but 2 were using Ufasoft. For GPU mining, there is no reason to use Ufasoft. CPU mining is unprofitable, a waste of resources, and puts as much load on getwork as a fast GPU, even if you're mining on a raspberry pi.
This change should improve the performance on the getwork pools for all other users.
This change should improve the performance on the getwork pools for all other users.
December 22, 2012, 11:31:21 AM
Is the site down? I get a 'To view this page, you must log in to area “realm” on btcguild.com:80' message when trying to access it.
The miners seem to work though...
The miners seem to work though...
If you ever encounter this error in the future, add 'www' to the address. When the DNS shuffles around like this during a DDoS, I don't always have time to fix the redirects to the website. It should let you in without it now.
December 22, 2012, 04:42:23 AM
Is the site down? I get a 'To view this page, you must log in to area “realm” on btcguild.com:80' message when trying to access it.
The miners seem to work though...
The miners seem to work though...
December 21, 2012, 10:55:11 AM
The attacks haven't completely stopped, but they are being mitigated. The mergedmining server should be up again shortly.
December 20, 2012, 11:16:55 PM
If we are using the proxy what server should we use?
Try multiple servers: mine1, mine2, mine3, btcguild.com, etc. The stratum proxy will redirect you to a different backend, so even if that DNS goes down you should remain connected.
December 20, 2012, 11:03:30 PM
If we are using the proxy what server should we use?
Jump to: