Is your feature request related to a problem? Please describe.
When launching, most coordinators would want to set a clean and easy-to-remember date for the launch of the blockchain.
Like: June 1st 12:00 CET
Our current message MsgTriggerLaunch takes a value RemainingTime, the number of seconds from the current block time for the chain launch. This makes it harder to determine an absolute date for the coordinator
Describe the solution you'd like
Change MsgTriggerLaunch, RemainingTime => LaunchTime: UNIX timestamp for the launch/genesis time
Change the message logic for
chain.LaunchTimestamp = msg.LaunchTime
The message fails if
msg.LaunchTime - block.Time > params.LaunchTimeRange.MaxLaunchTime
or
msg.LaunchTime - block.Time < params.LaunchTimeRange.MinLaunchTime
Is your feature request related to a problem? Please describe. When launching, most coordinators would want to set a clean and easy-to-remember date for the launch of the blockchain. Like: June 1st 12:00 CET Our current message
MsgTriggerLaunchtakes a valueRemainingTime, the number of seconds from the current block time for the chain launch. This makes it harder to determine an absolute date for the coordinatorDescribe the solution you'd like Change
MsgTriggerLaunch,RemainingTime=>LaunchTime: UNIX timestamp for the launch/genesis timeChange the message logic for
The message fails if
msg.LaunchTime - block.Time > params.LaunchTimeRange.MaxLaunchTimeormsg.LaunchTime - block.Time < params.LaunchTimeRange.MinLaunchTime