Go home blockchain, you are drunk! | Bitcointalksearch.org

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Quote from: Phinnaeus Gage on April 08, 2013, 08:06:26 PM

- snip -
Yea, nothing to see here just there there was nothing to see when InstaWallet was approached with an issue but assured everybody that everything was fine--then poof, they were gone.

I'm sure this is just a hiccup of some nature, but truly, truly needs to be addressed.
- snip -

Come on Phinnaues, you've been around long enough to know better. I thought you had a better understanding of Bitcoin than that. This has nothing to do with blockchain.info. This is an artifact of the timestamp in "the blockchain". I never expected you to be one to try and spread FUD.

Phinnaeus Gage

legendary

Activity: 1918

Merit: 1570

Bitcoin: An Idea Worth Spending

Quote from: Kluge on April 08, 2013, 12:49:48 PM

Quote from: Come-from-Beyond on April 08, 2013, 12:37:12 PM

Relax guys. It's time written into a block. It can vary within 2 hour timeframe.

Yup. Happens pretty often. I think Luke-Jr brought up a point (at least a year ago) where it could be problematic for some reason, but it wasn't anything major, IIRC.

Yea, nothing to see here just there there was nothing to see when InstaWallet was approached with an issue but assured everybody that everything was fine--then poof, they were gone.

I'm sure this is just a hiccup of some nature, but truly, truly needs to be addressed.

Full Disclosure (and hope I don't regret this): I truly like BlockChain.

DannyHamilton

legendary

Activity: 3388

Merit: 4615

Not a fork.

Not problematic.

Happens often.

There can be no guarantee that every peer on the network has their clocks perfectly synchronized. As such the protocol allows for some leeway in the timestamp that a miner places in the block that they solve. This leeway can result in a newer block having an older timestamp then the block (or blocks) preceding it. Since the blocks are ordered in the blockchain, this isn't a problem. The fact that the block has the hash of the previous block in its header proves that it actually occurred after the previous block, and the peers are all happy with that proof.

Kluge

donator

Activity: 1218

Merit: 1015

Quote from: Come-from-Beyond on April 08, 2013, 12:37:12 PM

Relax guys. It's time written into a block. It can vary within 2 hour timeframe.

Yup. Happens pretty often. I think Luke-Jr brought up a point (at least a year ago) where it could be problematic for some reason, but it wasn't anything major, IIRC.

Come-from-Beyond

legendary

Activity: 2142

Merit: 1009

Newbie

Relax guys. It's time written into a block. It can vary within 2 hour timeframe.

kerogre256

full member

Activity: 161

Merit: 100

http://blockexplorer.com/ show it too ...

Bytas

sr. member

Activity: 323

Merit: 250

Why is this topic moved? We didn't find out yet if this is a problem embedded in the blockchain.
Does this mean it's the site that fails? Some explanation might be nice :p

kerogre256

full member

Activity: 161

Merit: 100

Yeh what happend here ? Can someon explain ?

alexeft

legendary

Activity: 854

Merit: 1000

I have seen it many times at blockchain.info but I don't know what it is. Perhaps a fork?

Bytas

sr. member

Activity: 323

Merit: 250

So, i saw this very strange thing on blockchain.info, where the newer block is older than the one before it O.o
What am i seeing here, is this a typical example of a fork? or just the website being silly?
Any theories on this?

Topic: Go home blockchain, you are drunk! (Read 925 times)