Closed
Description
When the genesis_time field in the genesis.json file contains a future date & time, Tendermint ignores that and starts producing blocks right after launch (if there is quorum). An expected behaviour would be to wait until that date.
Tested on 0.21.0.
Activity
ValarDragon commentedon Aug 29, 2018
Could you double check if this problem persists on v0.23.0? We've made a couple changes to time, so that may have fixed this problem.
KrzysiekJ commentedon Aug 29, 2018
Yes, it persists.
milosevic commentedon Aug 29, 2018
It should normally be fixed in #2203.
ebuchman commentedon Aug 31, 2018
Don't think this is actually fixed in #2203.
Also not 100% on how we should do this - can we somehow just not start the ConsensusState until genesis time ?
melekes commentedon Sep 4, 2018
Can't we just
Sleepinnode#OnStartsomewhere until genesis time is reached?milosevic commentedon Sep 4, 2018
I was thinking the same.
ebuchman commentedon Sep 4, 2018
Yes, though I was thinking we'd start up the other services (eg. pex and mempool) ahead of time.
Certainly a simple solution for now is to just sleep.
milosevic commentedon Sep 5, 2018
This would actually be useful. Lets just check the complexity of doing it. If it's too complex then it might be done postlaunch and we go now with the simple sleep.
melekes commentedon Sep 18, 2018
Simple solution was implemented by @milosevic and merged to develop.
2 remaining items