|
Title: Block in future timestamp ? Post by: btc_enigma on August 28, 2015, 12:31:14 PM Today I found a block having timestamp which is > current time . Found this on my bitcoin node
Just to be sure I googled this on blockchain.info and found similar result: https://i.imgur.com/GGSqYrS.png Blockr had similar timestamp in the future ... but tradeblock was showing a past timestamp as expected Wondering if somone could throw some light on this, is this expected ? Title: Re: Block in future timestamp ? Post by: monsterer on August 28, 2015, 12:34:06 PM Timestamps are unreliable in a peer to peer environment. The only true 'time stamping' is POW.
Title: Re: Block in future timestamp ? Post by: btc_enigma on August 28, 2015, 01:13:59 PM Timestamps are unreliable in a peer to peer environment. The only true 'time stamping' is POW. So nodes will accept blocks with timestamp > current time ? Title: Re: Block in future timestamp ? Post by: monsterer on August 28, 2015, 01:48:37 PM Timestamps are unreliable in a peer to peer environment. The only true 'time stamping' is POW. So nodes will accept blocks with timestamp > current time ? There is a wide bounds for acceptability, I can't remember the exact bounding they use. Title: Re: Block in future timestamp ? Post by: achow101 on August 28, 2015, 02:39:18 PM Timestamps are unreliable in a peer to peer environment. The only true 'time stamping' is POW. So nodes will accept blocks with timestamp > current time ? There is a wide bounds for acceptability, I can't remember the exact bounding they use. Title: Re: Block in future timestamp ? Post by: btc_enigma on August 29, 2015, 06:06:46 AM Timestamps are unreliable in a peer to peer environment. The only true 'time stamping' is POW. So nodes will accept blocks with timestamp > current time ? There is a wide bounds for acceptability, I can't remember the exact bounding they use. What is rational behind this design, I understand 1 min or so , for time lags on node . If block timestamp is so unreliable, what is the point of having it in the block header. This could lead to cases where timestamp of block n < timestamp of block n-1 Title: Re: Block in future timestamp ? Post by: amaclin on August 30, 2015, 07:50:57 AM bc.i has a bug
this site always shows the same timestamp for Block Timestamp and Received Time Title: Re: Block in future timestamp ? Post by: DannyHamilton on August 30, 2015, 08:01:25 AM What is rational behind this design, The only thing the timestamp is intended to be used for is calculating the new proof-of-work difficulty every 2016 blocks. A variation in timestamps of 120 minutes or so isn't a problem for that use case, and it means that the decentralized peer-to-peer system doesn't need a centralized source of time that everyone can agree on. This could lead to cases where timestamp of block n < timestamp of block n-1 Yes. It happens all the time. Title: Re: Block in future timestamp ? Post by: btc_enigma on August 30, 2015, 10:57:23 AM Quote The only thing the timestamp is intended to be used for is calculating the new proof-of-work difficulty every 2016 blocks. A variation in timestamps of 120 minutes or so isn't a problem for that use case, and it means that the decentralized peer-to-peer system doesn't need a centralized source of time that everyone can agree on. Thanks. Make sense ! Title: Re: Block in future timestamp ? Post by: spin on September 03, 2015, 10:03:29 AM Yes. It happens all the time. Pardon the pun? |
