Topic: The timestamp of the block 57060 is lower than the median of the prev 11 blocks (Read 719 times)
February 15, 2016, 08:47:21 AM
Thanks bud <3
February 15, 2016, 08:29:44 AM
February 15, 2016, 08:18:03 AM
I was reading the developer reference and I found this:
It's nice to have that rule in the protocol because otherwise miners could set any timestamp in the past. But I don't understand how is it possible that the block 57060 doesn't follow that rule. As you can see, it has a timestamp of more than one hour before the previous block. That shouldn't be a problem if the timestamp was still greater or equal the median of the previous eleven, but it turns out it is not.
The median of the blocks [57049-57059] is 1274556410.5454545, and thats +797 seconds ahead of the timestamp of the block 57060.
How is this possible?
Quote
The block time is a Unix epoch time when the miner started hashing the header (according to the miner). Must be greater than or equal to the median time of the previous 11 blocks. Full nodes will not accept blocks with headers more than two hours in the future according to their clock.
It's nice to have that rule in the protocol because otherwise miners could set any timestamp in the past. But I don't understand how is it possible that the block 57060 doesn't follow that rule. As you can see, it has a timestamp of more than one hour before the previous block. That shouldn't be a problem if the timestamp was still greater or equal the median of the previous eleven, but it turns out it is not.
The median of the blocks [57049-57059] is 1274556410.5454545, and thats +797 seconds ahead of the timestamp of the block 57060.
How is this possible?
Code:
Height Timestamp
57049 1274553925
57050 1274554547
57051 1274554591
57052 1274554864
57053 1274555612
57054 1274555564
57055 1274556515
57056 1274557815
57057 1274558735
57058 1274558865
57059 1274559483
57060 1274555613
Jump to: