[CHECKLIST] V2 Migration

[drewstone]

Overview

Migrating frontend apps (tangle-dapp, tangle-cloud, leaderboard) to fit with tnt-core/v2. Remove everything related to Polkadot/Substrate.

Detailed requirements here

Tasks

• Plan and create checklist for this later
• [TASK] QA restaking (deposit, delegate, undelegate, withdraw) for v2 #3083
• [TASK] QA liquid staking #3084
• QA claim migration #3085
• QA submitting blueprints / visualizing them (CC @danielbui12)
• QA registering operators and registering for blueprints
• QA creating, paying, and operating services
• QA pricing engine usage (RFQ - request for quotes, for customers)
• QA leaderboard

[vutuanlinh2k2]

Requirements

Tracking doc for migration to tnt-core/v2. Everything should go into a v2 branch. We don't merge anything until v2 is feature-parity working with the majority of Tangle v2.

Unified library components / docs

• Remove Polkadot wallet providers from the app's wallet provider. Only EVM should remain.
• Remove Polkadot dependencies from the shared libraries and the repo.
• Update the docs to remove Polkadot references, shift to EVM protocol.

GraphQL

We need a new GraphQL repo, can do it entirely clean. Can use Envio

• Build the indexer config for Tangle v2
• Every restaking/cloud thing here needs to be considered
• Review points calculations in here and migrate to new GraphQL (likely remove anything related to nomations/Polkadot lingo functionality).
• Audit credits claiming work and figure out / improve this line item once we get to it @vutuanlinh2k2

App

• Before deprecating the Bridge and Nominations can we leverage it in any way? Of course keep the UI components around, they might be useful.
• Remove Polkadot dependencies entirely by the end of this.
• Migrate restaking (more subtasks below)
• Migrate depositing assets.
• Migrate delegating assets.
• Migrate undelegating.
• Migrate withdrawing.
• Migrate vaults to the new EVM protocol incentive information.
• Migrate operator class/hooks listing operators, etc.
• Migrate querying and presenting blueprints on UI

Cloud

• Remove Polkadot dependencies entirely by the end of this.
• Migrate querying and presenting blueprints on UI
• Migrate deploying a blueprint.
• Migrate registering as an operator.
• Add preregistering for blueprints.

Leaderboard

• Update to the new everything. @vutuanlinh2k2 could expand this out once we get there.

[drewstone]

I've likely completed most of this @vutuanlinh2k2, you should go through and check off everything that is done here so you're up to speed. Book time with me or otherwise start testing individual pages (like the cloud, leaderboard, or dApp). There is a local script that runs and spins up an indexer ./scripts/local-env/setup-local-env.sh. Use that.

There is also now migration claims which claims balances from Substrate addresses which needs to be battle tested.