Hi, BIP 42 is a code base consensus soft fork that at the time of
activation does not really manifest as a fork because nobody is running any
code not already applying it. Can a similar thing be done in 17 years? (I
haven't really made sense of this year 2038 problem, I don't know or
understand
yes but ... just for the sake of argument ... if a change such as this
wraparound interpretation is made anytime in the next 5 years it'll be over
a *decade after that *before any wrapped-around timestamp is legitimately
mined ... and by then nobody will be running incompatible (decade old) node
> What happens if a series of blocks has a timestamp of 0x at the
> appropriate time?
The chain will halt for all old clients, because there is no 32-bit value
greater than 0x.
> 1. Is not violated, since "not lower than" means "greater than or equal to"
No, because it has to
> Interesting discussion.Correct me if I'm wrong: but putting too many features
> together in one shot just can't make things harder to debug in production if
> something very unexpected happens.It's a basic principle of software
> engineering.
Soft fork features can (and should) obviously be
