eu-stratum.btcguild.com:3333
Dead
Dead
As posted above, it's hopefully coming back up soon. Resync of the blockchain is almost caught up.
UPDATE: EU Stratum is back online.
Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 313. (Read 903150 times)
April 23, 2013, 01:33:42 PM
As posted above, it's hopefully coming back up soon. Resync of the blockchain is almost caught up.
UPDATE: EU Stratum is back online.
April 23, 2013, 01:32:10 PM
eu-stratum.btcguild.com:3333
Dead
Dead
April 23, 2013, 01:18:53 PM
Still stating that being beyond 30% is irresponsible.
April 23, 2013, 01:14:44 PM
Just adding: BTC Guild has STILL not reached 40% of the network blocks over the last 2016. It has been over two weeks since the first posts about BTC Guild being at/over 51%, and it would still require the pool to have 25% more hash rate than it currently has before it is true.
April 23, 2013, 01:12:42 PM
what is this?
This is your pool having the sufficient hashrate for a 51% attack, once again. Note the six consecutive blocks. April 23, 2013, 01:07:20 PM
I'll just leave this here:
Please consider moving your miners if you can read this.
Please consider moving your miners if you can read this.
what is this?
April 23, 2013, 12:32:43 PM
I'll just leave this here:
Please consider moving your miners if you can read this.
Please consider moving your miners if you can read this.
April 23, 2013, 11:09:22 AM
EU Stratum is going down, will be back up as soon as possible.
UPDATE: EU Stratum should be restored within 1-2 hours. A second EU Stratum server will hopefully be coming online early May.
UPDATE: EU Stratum should be restored within 1-2 hours. A second EU Stratum server will hopefully be coming online early May.
April 21, 2013, 10:58:11 AM
EU Stratum server is being rebooted, should be back up in a few minutes. Sorry for the lack of notice.
April 20, 2013, 07:06:44 AM
Pool Speed 30,168 GH/s.
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Use the 7 day window. More accurate.
Isn't 3 days accurate enough?
I'm not referring to a three day average, but the three day estimate on bitcoin.sipa.be.
It's not a three day or a seven day rolling average on bitcoin.sipa.be, the names a bit of a misnomer. The seven day window there is similar to the results I get using a different method, so I know it's the best estimate to use.
The three day estimate still has far too much variance in it. If you try to do a GOF of 1/(three day estimate hashrate) to a gamma distribution, you get a poor fit (p<0.05). The method I use that has similar results to the 7 day estimate has quite a good fit of 1/hashrate to a gamma distribution.
I always see 3 days of diff calculation as quite accurate - and always tell anyone who looks at the diff after a change to wait for ~3 days/~432 blocks ... like now 
1.6% - nice
1.6% - nice The confidence interval of the hashrate depends on how you calculate the hashrate - blocks per unit time or amount of time per block (or blocks).
I'll get around to posting something on it Real Soon Now (tm)
In the meantime your best bet is to use the seven day line on bitcoin.sipa.be for your estimate.
April 20, 2013, 06:48:49 AM
Pool Speed 30,168 GH/s.
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Use the 7 day window. More accurate.
Isn't 3 days accurate enough?
I always see 3 days of diff calculation as quite accurate - and always tell anyone who looks at the diff after a change to wait for ~3 days/~432 blocks ... like now
1.6% - nice April 20, 2013, 05:03:32 AM
Pool Speed 30,168 GH/s.
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Use the 7 day window. More accurate.
April 20, 2013, 05:02:26 AM
Pool Speed 30,168 GH/s.
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
Network speed according to bitcoin.sipa.be 3 day average : 63GH/s
Will the only way to influence this be a ddos ?
April 20, 2013, 04:58:52 AM
With OzCoin closing down temporarily and other pools getting DDoS 30K still seems reasonable.
April 20, 2013, 02:32:19 AM
now it's almost over 30k!!!
April 19, 2013, 08:05:45 PM
How can a "51% attack" be possible when BTCGuild has ~ 42% of the hashrate atm? Have you been sniffing blockchain.info/pools sir?
Surely 42% cannot get 6 or more consecutive blocks? Surely 42% isnt risky ? Surely a ddos on another top pool or two would not push this past 51% Surely two pool ops could not work together on achieving the dominant part of the network ? Surey not... take a minute to think of what is at stake. Being past 30% is outright irresponsible in my book, this is just a dizaster wating to happen. Well, that's not a "51% attack" , is it? I'd just come from another thread claiming at that BTCGuild had 48% of the hashrate and I assumed you were referring to that thread. The problem there was that they'd been basing their estimate on blockchain.info.
The 42% I quoted was based on the estimated network hashrate and the instantaneous pool hashrate and so is not the same thing as the proportion of blocks solved.
April 19, 2013, 12:24:04 PM
Just to point it out, BTC Guild is still in the 36-37% range out of the last 2016 blocks. Luck has been terrible the last week and a half, so it's probably a bit understated right now, but I continue to trust http://blockorigin.pfoe.be and use that for the 51% mitigation steps that kick in at 40%+.
I understand and appreciate what you are doing, but you should not be the only one with a sense of responsibility here. Mining is not just making Internet Magic Money, you are the guardians of the blockchain, each and every one of you bares responsibility wether you like it or not. Start living up to the duty and bearing that responsibility. April 19, 2013, 12:18:29 PM
Just to point it out, BTC Guild is still in the 36-37% range out of the last 2016 blocks. Luck has been terrible the last week and a half, so it's probably a bit understated right now, but I continue to trust http://blockorigin.pfoe.be and use that for the 51% mitigation steps that kick in at 40%+.
April 19, 2013, 12:09:04 PM
How can a "51% attack" be possible when BTCGuild has ~ 42% of the hashrate atm? Have you been sniffing blockchain.info/pools sir?
Surely 42% cannot get 6 or more consecutive blocks? Surely 42% isnt risky ? Surely a ddos on another top pool or two would not push this past 51% Surely two pool ops could not work together on achieving the dominant part of the network ? Surey not... take a minute to think of what is at stake. Being past 30% is outright irresponsible in my book, this is just a dizaster wating to happen. April 19, 2013, 12:04:59 PM
Hi
I dont like making this post, but it needs to be said. WTF are you miners doing giving one pool all this hashpower ? At current a 51% attack is possible, I respect eleuthria and can respect that you trust him. But this is just not acceptable, what if someone managed to compromise the pool server.. or held eleuthria at gunpoint. You are playing with the very existense of bitcoin. Disperse to other pools, immediately, please.
I dont like making this post, but it needs to be said. WTF are you miners doing giving one pool all this hashpower ? At current a 51% attack is possible, I respect eleuthria and can respect that you trust him. But this is just not acceptable, what if someone managed to compromise the pool server.. or held eleuthria at gunpoint. You are playing with the very existense of bitcoin. Disperse to other pools, immediately, please.
How can a "51% attack" be possible when BTCGuild has ~ 42% of the hashrate atm? Have you been sniffing blockchain.info/pools sir?
Jump to: