Topic: Some blocks have earlier block times than their predecessing block, how/why? (Read 878 times)
August 12, 2015, 05:14:20 AM
Having timestamps in blocks is a regrettable consequence of the requirement to adjust for difficulty.
August 11, 2015, 07:20:56 PM
Who says what the altcoins do actually works-- many have just had spontanious failures due to ill advised changes like twiddling how retargeting works... and there is no reason to expect that most have ever been analyized from an adversarial perspective (much less actually attacked). ... but thats a question for another subforum.
As you note, it works fine in Bitcoin as is... and, in fact, requiring the time to be monotonic would open up new attacks. If you want a monotonic time out of bitcoin you can extract one by simply running a rolling maximum over the timestamps, forcing miners to conceal more information won't help anything.
As you note, it works fine in Bitcoin as is... and, in fact, requiring the time to be monotonic would open up new attacks. If you want a monotonic time out of bitcoin you can extract one by simply running a rolling maximum over the timestamps, forcing miners to conceal more information won't help anything.
August 09, 2015, 05:20:36 AM
Then how do we agree on the next difficulty / retarget ?
Do we take the block time for that, even though we know they're not accurate? (I can see how that works, just wondering)
*edit* now that I think of it, I can see how that works with Bitcoin, taking the average over the past 2016 blocks, but how would that work with altcoins that retarget much faster, or even after every single block? (albeit a gradual retarget, e.g. gravity well formulas)
Do we take the block time for that, even though we know they're not accurate? (I can see how that works, just wondering)
*edit* now that I think of it, I can see how that works with Bitcoin, taking the average over the past 2016 blocks, but how would that work with altcoins that retarget much faster, or even after every single block? (albeit a gradual retarget, e.g. gravity well formulas)
August 09, 2015, 04:42:50 AM
-snip-
What's up with that? Is there a trustworthy method of restoring a block's actual, correct time of mining?
What's up with that? Is there a trustworthy method of restoring a block's actual, correct time of mining?
No, because of what heretolearn said and the fact that the timestamp influences the blocks hash miners tend to manipulate the timestamp for mining purposes. The exact time for a block is not that crucial to the network.
August 09, 2015, 03:56:55 AM
There is no central authority to keep track of time. The block is mined by computers running on different timezones worldwide. For a block to be included it must pass some basic sanity tests - the block time is not earlier than the median of the last 11 blocks. So as long as thats fine, its included.
August 09, 2015, 03:34:27 AM
I noticed that quite frequently a block is mined at an earlier time than its predecessor. At least according to its timestamp, which is generated by the server that mined the block, and obviously they can have some difference. But the differences are quite large sometimes (over 10 minutes).
For example:
Block 368511 was mined at 2015-08-05 15:49:19, and the next block was mined at 2015-08-05 15:37:55 (almost 12 minutes earlier).
Or block 367387 was mined at July 28th 2015, 22:36:45, and the next block was mined July 28th 2015, 22:25:56 (again, almost 12 minutes earlier).
I'm using different block explorers to indicate it's not a bug in a particular block explorer, these times are the same everywhere.
What's up with that? Is there a trustworthy method of restoring a block's actual, correct time of mining?
For example:
Block 368511 was mined at 2015-08-05 15:49:19, and the next block was mined at 2015-08-05 15:37:55 (almost 12 minutes earlier).
Or block 367387 was mined at July 28th 2015, 22:36:45, and the next block was mined July 28th 2015, 22:25:56 (again, almost 12 minutes earlier).
I'm using different block explorers to indicate it's not a bug in a particular block explorer, these times are the same everywhere.
What's up with that? Is there a trustworthy method of restoring a block's actual, correct time of mining?
Jump to: