Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Side-chain timestamps are messed up #38

Open
Z-a-r-a-k-i opened this issue Dec 4, 2018 · 2 comments
Open

Side-chain timestamps are messed up #38

Z-a-r-a-k-i opened this issue Dec 4, 2018 · 2 comments
Labels
Type: Bug The issue relates to broken or incorrect behaviour.

Comments

@Z-a-r-a-k-i
Copy link

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:

  1. Run deployer from core-deployer packages with some
    legit parameters
  2. Use the generated configuration files on fresh core installation
  3. After nodes start to forge, check timestamps in blocks table from database
  4. Do the maths : 1490101200 + block timestamp, then convert to date
  5. Or run an explorer to have some nice display of the data

Screenshots
capture

Server (please complete the following information):

  • OS: Ubuntu Server
  • Version 16.04
@alexbarnsley
Copy link
Member

@Z-a-r-a-k-i the deployer side isn't quite ready so there are likely issues. When it is, it will be updated in the deployer repo.

@Z-a-r-a-k-i
Copy link
Author

Okay thank you Alex

@faustbrian faustbrian transferred this issue from ArkEcosystem/core Dec 19, 2018
@faustbrian faustbrian added the Type: Bug The issue relates to broken or incorrect behaviour. label Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug The issue relates to broken or incorrect behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants