You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are various places in the SDK's state machine where the block time is highly integral to core business logic (e.g. governance, vesting, etc...)
When running simulation from a custom genesis file (i.e. not random), the genesis time must also not be random, but rather use the genesis file's timestamp. Not only that, but the genesis file's timestamp should be that of the last block (exported block) time.
e.g.
When running simulations on a migrated exported mainnet genesis at height 1017669, the genesis time that should be used is 1562964590.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
There are various places in the SDK's state machine where the block time is highly integral to core business logic (e.g. governance, vesting, etc...)
When running simulation from a custom genesis file (i.e. not random), the genesis time must also not be random, but rather use the genesis file's timestamp. Not only that, but the genesis file's timestamp should be that of the last block (exported block) time.
e.g.
When running simulations on a migrated exported mainnet genesis at height 1017669, the genesis time that should be used is 1562964590.
For Admin Use
The text was updated successfully, but these errors were encountered: