Replies: 1 comment
-
After creating this discussion, Radu mentioned he'll be working on the IaC and he just needs a working example with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For the indexer migration, we have a couple draft PRs for the
movement
repo:I'm wondering whether this approach makes sense, because as @musitdev pointed out in a comment on 1264, and as I'm seeing when testing 1275, there are certain incompatibilities with the Movement node. Philippe has advised to
This to me makes the most sense... I've only been able to do this using
aptos-core
(main
orl1-migration
branch, not themovement
repo.I could be incorrect and maybe there is a convenient way to run an Aptos node from the
movement
repo? But from what I can tell the best approach logistically may be instead of working with themovement
repo:The main reason for proposing this strategy, of deploying individual V2 processors alongside each post-l1 migration Aptos node, is because we've shown that it works (for one approach using a transaction stream service, see these notes), and the old Movement node doesn't appear to be compatible with the V2 indexers... so, it is proposed here to wait until each network (starting with devnet) upgrades to an Aptos node and then implement the V2 processors in the instance for the node, running each processor with its own binary.
Beta Was this translation helpful? Give feedback.
All reactions