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

Blockchain network migration protocol #12

Open
ts5746 opened this issue Apr 15, 2019 · 1 comment
Open

Blockchain network migration protocol #12

ts5746 opened this issue Apr 15, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@ts5746
Copy link
Contributor

ts5746 commented Apr 15, 2019

Original internal issue on blockchain dependency and failover.

In the scenario that Blockchain Network 'X' becomes unavailable, because of external and uncontrollable reasons, we must implement a protocol to migrate the Whiteflag Network to a different underlying Blockchain system.

Proposition: Maintain a redundancy layer that stores all Whiteflag messages, as well as their respective transaction hashes. This way the Whiteflag historical record can be rebuilt at any time and its content mathematically verified.

Additionally, a procedure to determine the replacing Blockchain Network needs to be implemented.

Proposition: In the case of a forced migration, the Whiteflag Network will migrate to the Blockchain that, besides adhering to the basic technical requirements, has the most cumulative work behind it.

@ts5746 ts5746 added the enhancement New feature or request label Apr 15, 2019
@ts5746
Copy link
Contributor Author

ts5746 commented Apr 15, 2019

To be reviewed whether this is an implementation issue, or this needs to be in the protocol specification.

@ts5746 ts5746 added this to the v2-development milestone Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant