Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Wrong network showing up when nodes does not drop database after nethash update #4

Closed
fix opened this issue Feb 14, 2017 · 1 comment

Comments

@fix
Copy link
Contributor

fix commented Feb 14, 2017

This is protocol level issue:

  • fast fix: prevent from node to start if block height 1 in db is different from genesisBlock.json
  • full fix: upgrade protocol, for instance signing all blocks including nethash. Other protocol upgrades possible. Good for AIP proposal
@faustbrian
Copy link
Contributor

As Core 2.0 is under development we will close all the PRs and Issues regarding Core 1.0 and only handle critical issues if any come up.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants