Question: DEFAULT_MAX_TIME_ADJUSTMENT != MAX_FUTURE_BLOCK_TIME #15436

issue cryptozeny opened this issue on February 18, 2019

cryptozeny commented at 11:19 AM on February 18, 2019: none

https://github.com/bitcoin/bitcoin/blob/29e82e460e19818b420e7169ac8ed5248d6d0af9/src/timedata.h#L13

https://github.com/bitcoin/bitcoin/blob/29e82e460e19818b420e7169ac8ed5248d6d0af9/src/chain.h#L21

why different? IMHO both should be the same, or should be an associated number... :thinking:
cryptozeny renamed this:
~~DEFAULT_MAX_TIME_ADJUSTMENT != MAX_FUTURE_BLOCK_TIME~~
Question: DEFAULT_MAX_TIME_ADJUSTMENT != MAX_FUTURE_BLOCK_TIME
on Feb 18, 2019
benthecarman commented at 12:09 AM on February 25, 2019: contributor

DEFAULT_MAX_TIME_ADJUSTMENT refers to the limit of how different a peer's time can be from your own clock vs MAX_FUTURE_BLOCK_TIME refers to how different a block's timestamp can be from your own clock
cryptozeny commented at 5:03 AM on February 25, 2019: none

good to know thanks, but i am still confused. how to handle this...
sipa commented at 6:31 AM on February 25, 2019: member

They're completely unrelated. I don't understand what you mean by "handle it".

I'm going to close this. Questions like this about Bitcoin's design, as opposed to actual sofrware issues with the Bitcoin Core implementation, belong more on https://bitcoin.stackexchange.com or various fora.
sipa closed this on Feb 25, 2019
DrahtBot locked this on Dec 16, 2021

Contributors