Ecosystem Compatibility & Migration Validation for Aptos Core Upgrade #183
Description
As part of the Aptos Core migration and framework upgrade initiative, we must ensure that the Movement ecosystem tools—explorer, indexer, SDKs, wallets, and partner applications—remain functional and accurate post-migration.
This issue tracks the validation and upgrade work required across ecosystem components following DB migration and framework updates.
cc @Rahat-ch @shayansanjideh @Primata @vpallegar
Validation Targets
-
Indexer
- Ensure indexer can be restarted and fully reindexes from backup/migrated DB.
- Assigned: @andygolay
-
REST API Compatibility
- Test compatibility and correctness of REST endpoints.
- Focus on basic checks (e.g. balances, module deployment).
- @sebtomba
-
SDKs / CLI Tools
- Confirm Movement SDKs and CLI tools interact correctly with the new node.
-
Explorer
- Validate block/transaction visibility.
- Confirm account lookup and search work properly.
-
Wallet & Transaction Flow
- Validate wallet integration and transaction propagation across RPC.
-
Partner RPC Integrations
- Check RPC compatibility with known partners using custom RPC setups.
Optional Enhancements
- Capture list of known partners using private RPCs and test integration paths.
- (Stretch goal) Add automated API test coverage for high-traffic endpoints.
Dependencies
- Build DB switch mechanism #179
- Verification of DB Integrity Post-Migration to Latest Aptos Core #181
Notes
- If total downtime is acceptable (< 2–3 hours), partners can be notified and network halted temporarily.
- Otherwise, consider connecting the new Aptos Core node to the DA sequencer during migration to minimize lost transactions.