Quote from: CYPER on January 06, 2014, 01:38:18 PM

Quote from: os2sam on January 06, 2014, 01:36:05 PM

Quote from: CYPER on January 06, 2014, 01:33:22 PM

Quote from: os2sam on January 06, 2014, 01:20:08 PM

Quote from: CYPER on January 06, 2014, 01:16:38 PM

Quote from: os2sam on January 06, 2014, 01:14:54 PM

Quote from: CYPER on January 06, 2014, 01:11:11 PM

Quote from: DeepBit on January 06, 2014, 01:08:07 PM

Quote from: CYPER on January 06, 2014, 01:06:48 PM

So is the pool speed really 171 Gh/s?
Yet https://blockchain.info/pools shows it as 1%

You didn't read what I posted just 7 minutes ago, right ?

Nothing in relation to DeepBit actual speed.

But there is an acknowledgement of the problem and that he is working on it. Which is probably being slowed with questions like, is the pools speed really that low right now? while there are connectivity problems.

My question had nothing to do with the guy who wanted to stop a transaction.
It was just a general question.

Even without connectivity problems the 1TH/s speed is well below what https://blockchain.info/pools shows.

Your question was answered before you asked it.

Quote from: DeepBit on January 06, 2014, 01:00:04 PM

We are experiencing connectivity problems for about 3 hours now.
Working on this problem.

My question was about the discrepancy between what https://blockchain.info/pools and what Deepbit shows with or without connectivity problems.
1% of the total network is more than 100TH/s which is much greater than what is displayed on DeepBit with or without connectivity problems.

So DeepBit having connectivity problems has nothing to do with my question.
Did you get it now?

Trying to have a conversation with you is allot like trying to nail jello to the wall.

I don't think I can make my question any clearer, so if you don't know the answer that's ok Wink

Your first question was

Quote from: CYPER on January 06, 2014, 01:06:48 PM

So is the pool speed really 171 Gh/s?

Yet https://blockchain.info/pools shows it as 1%

Which was preemptively answered with

Quote from: DeepBit on January 06, 2014, 01:00:04 PM

We are experiencing connectivity problems for about 3 hours now.
Working on this problem.

Now your new question

Quote from: CYPER on January 06, 2014, 01:33:22 PM

My question was about the discrepancy between what https://blockchain.info/pools and what Deepbit shows with or without connectivity problems.
1% of the total network is more than 100TH/s which is much greater than what is displayed on DeepBit with or without connectivity problems.

So DeepBit having connectivity problems has nothing to do with my question.
Did you get it now?

Which isn't really a question at all, but an inaccurate statement, has been answered so many times in this thread it doesn't bear repeating. But just in case you missed all of those explanations, blockchain.info is very inaccurate in it's estimation of deepbits hashrate. One person, ZVS I think, has even stated that he is not deepbit because they keep assigning blocks relayed with his IP as being mined by deepbit.

But go ahead and keep implying that a getwork only pool is really running at 100 Ths instead of .8-1.2Ths. I'm sure your right since only a moron would doubt your superior analysis.