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

Introduce third approach: Keep old chain running #7

Open
sea212 opened this issue Mar 29, 2023 · 0 comments
Open

Introduce third approach: Keep old chain running #7

sea212 opened this issue Mar 29, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@sea212
Copy link
Member

sea212 commented Mar 29, 2023

In that case you want to avoid that blocks intermingle between the old and the new network, which is possible since they share the same history. If not taken care of, new blocks from the old chain after the fork could enter the new chain and cause problems.

  1. Specify exact block when snapshot is taken and transferred to new network
  2. Prepare a chainspec with proper protocolId and badBlocks feature and share in time
@sea212 sea212 added the enhancement New feature or request label Mar 29, 2023
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