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

Mark onbording tasks #19

Open
tak1827 opened this issue Mar 1, 2024 · 0 comments
Open

Mark onbording tasks #19

tak1827 opened this issue Mar 1, 2024 · 0 comments
Assignees

Comments

@tak1827
Copy link
Contributor

tak1827 commented Mar 1, 2024

To facilitate the infrastructure engineering tasks for building and opstack versions of Sand Verse and replica nodes, I've outlined a series of steps. These steps, although not necessarily in sequential order, are designed to ensure a smooth process:

  1. Build Legacy Verse on Testnet: Before establishing the opstack version, start by building the legacy version of Sand Verse. The construction steps for the legacy version are similar to those you will use for the opstack version but provide a good foundation and testing ground.

  2. Build Replica Verse: For testing purposes, construct a replica node for the legacy Sand Verse. Guide line

  3. Build Instant Verifier: To confirm that both the legacy verse and its replicas are functioning correctly, activate an instant verification feature on the testnet. Since the existing Sand Verse does not include an instant verifier, this will be the inaugural attempt at implementing such a feature in a test environment.

  4. Build opstack Version of Verse: The construction of the OpStack version of Sand Verse is divided into two phases:

  • Phase 1: Start building from scratch without incorporating data migration. Given that the data migration steps have not yet been established, the initial build will proceed without this component.
  • Phase 2: Once the data migration procedure is ready, rebuild the opstack Verse. This step ensures that all historical data and relevant information from the legacy system are correctly integrated into the new OpStack version, maintaining continuity and integrity of data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants