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
Describe the bug
Timestamp are messed up if we try to create an ARK side-chain with core-deployer :
Default timestamp in genesisBlock are set to 0 which corresponds to 21/03/2017 14:00. It should be set to Timestamp(today) - Timestamp(21/03/2017 14:00), at the time deployer is runned or even better at the time first block is added to the blockchain on network first start.
No idea why, but timestamp of forged blocks after genesis block are computed wrongly : They start from date 01/01/2019, but time is correct.
To Reproduce
Steps to reproduce the behavior:
Run deployer from core-deployer packages with some
legit parameters
Use the generated configuration files on fresh core installation
After nodes start to forge, check timestamps in blocks table from database
Do the maths : 1490101200 + block timestamp, then convert to date
Or run an explorer to have some nice display of the data
Screenshots
Server (please complete the following information):
OS: Ubuntu Server
Version 16.04
The text was updated successfully, but these errors were encountered:
Describe the bug
Timestamp are messed up if we try to create an ARK side-chain with core-deployer :
Default timestamp in genesisBlock are set to 0 which corresponds to 21/03/2017 14:00. It should be set to Timestamp(today) - Timestamp(21/03/2017 14:00), at the time deployer is runned or even better at the time first block is added to the blockchain on network first start.
No idea why, but timestamp of forged blocks after genesis block are computed wrongly : They start from date 01/01/2019, but time is correct.
To Reproduce
Steps to reproduce the behavior:
legit parameters
Screenshots
Server (please complete the following information):
The text was updated successfully, but these errors were encountered: