Can Bitcoin be affected by an extra second?

[nachoig]

Explaining: because of the Earth's rotation speed, 2015 will have an extra second. According to this article, this extra second can lead to some instabilities over the internet. So, for example, can this affect the interval between Bitcoin blocks?

http://www.theverge.com/2015/1/7/7508651/leap-second-2015-earths-rotation-slowing

[DeathAndTaxes]

No.  Bitcoin already has a very loose time synchronization.  Timestamps can be off as much as two hours and still be considered valid.  An extra second isn't even detectable.

[Foxpup]

To elaborate, systems that assume Unix timestamps are always sequential will be mistaken about the ordering of events that take place during a leap second and the following second, since the two seconds are indistinguishable from the timestamps. For example, an event which occurs at 11:59:60.8 PM will have a later timestamp than an event that takes places half a second later at 12:00:00.3 AM, since 11:59:60 PM and 12:00:00 AM are the same in Unix time. (And some systems, when dealing with human-readable time formats, will give an error on seeing the 60.8 seconds, since such a timestamp is "obviously" invalid.)

Bitcoin has none of these problems. It does not use timestamps to determine the ordering of events, with out-of-order timestamps being perfectly valid, and a single second will not make any appreciable difference to the block interval.

[Beymond]

First i was like why is there even a question like this
After reading this
Exactly 

To elaborate, systems that assume Unix timestamps are always sequential will be mistaken about the ordering of events that take place during a leap second and the following second, since the two seconds are indistinguishable from the timestamps. For example, an event which occurs at 11:59:60.8 PM will have a later timestamp than an event that takes places half a second later at 12:00:00.3 AM, since 11:59:60 PM and 12:00:00 AM are the same in Unix time. (And some systems, when dealing with human-readable time formats, will give an error on seeing the 60.8 seconds, since such a timestamp is "obviously" invalid.)

Bitcoin has none of these problems. It does not use timestamps to determine the ordering of events, with out-of-order timestamps being perfectly valid, and a single second will not make any appreciable difference to the block interval.

[samson]

There's a whole mailing list dedicated to leap seconds and how they should be handled / standardised.

[nachoig]

Thanks for the explanation people.