Topic: Is the first Bitcoin network attack just happening? (Read 1747 times)
If it were an attack blocks would still be generated wouldn't they? unless a different attack was being done that i have not herd of yet.
This is part of a reply from wareen that i got by PM when i had the thread locked.
Gonna post it here for posterity and because it seems you guys will like it
Gonna post it here for posterity and because it seems you guys will like it
At least your thread got me interested to take a look at some block chain statistics - the longest time between two blocks was over 25 hours! That was back in the early months of Bitcoin but nevertheless interesting. Since about January 2010 it was relatively stable with one exception in August 2010 where I think there was some attack due to a bug in the client which had to be fixed manually. The longest interval within the stable period was on May 15th 2011 with 94 minutes!
I'd love to see a real-time histogram of the block generation, just so it could allay fears like these. It's just variance, like other posters have said.
Yeah I never really understood why people constantly post stuff like this like what they are posting is never suppose to happen.
For the same reason the one brat in kindergarten does something for attention... For the attention.
I'd love to see a real-time histogram of the block generation, just so it could allay fears like these. It's just variance, like other posters have said.
Yeah I never really understood why people constantly post stuff like this like what they are posting is never suppose to happen.
I'd love to see a real-time histogram of the block generation, just so it could allay fears like these. It's just variance, like other posters have said.
Zomfg bitcoin has been haxored SELL SELL SELL! 
seems like everything is ok: 7 blocks during last 2 hours
30 minutes? That's just three times the expected value...
Everything's fine - there have been incidents of no block being found for over 60 minutes so don't worry and maybe use the time to read up on some statistics.
When no block is found for half a day we should probably start getting suspicious
Everything's fine - there have been incidents of no block being found for over 60 minutes so don't worry and maybe use the time to read up on some statistics.
When no block is found for half a day we should probably start getting suspicious
What got me thinking was the 2 blocks found at the exact same time, not the 30min. wait
Edit: maybe i should not say exact same time because obviously the last block had to be found at least a nano-second later
30 minutes? That's just three times the expected value...
Everything's fine - there have been incidents of no block being found for over 60 minutes so don't worry and maybe use the time to read up on some statistics.
When no block is found for half a day we should probably start getting suspicious
Everything's fine - there have been incidents of no block being found for over 60 minutes so don't worry and maybe use the time to read up on some statistics.
When no block is found for half a day we should probably start getting suspicious
Look at this http://blockexplorer.com/
2 last blocks found at the exact same time and now, more than 30min later, no more blocks... WTF?!?!
Well, something's not right in this picture.
Before someone says it's a block explorer error, well, it isn't. I sent a transaction like 25minutes ago, and still no confirmation, the block number in my client match the one in block explorer.
2 last blocks found at the exact same time and now, more than 30min later, no more blocks... WTF?!?!
Quote
136584 35ac219a1a... 2011-07-16 15:24:22 1 50 0.216
136583 1d7635c503... 2011-07-16 15:24:22 61 1784.05664625 24.966
136583 1d7635c503... 2011-07-16 15:24:22 61 1784.05664625 24.966
Well, something's not right in this picture.
Before someone says it's a block explorer error, well, it isn't. I sent a transaction like 25minutes ago, and still no confirmation, the block number in my client match the one in block explorer.
Jump to: