Conversation
AMP-powered subgraphs use different network names than graph-node's internal chain names (e.g., AMP uses "ethereum-mainnet" while graph-node uses "mainnet"). Add a config-level `amp` field on chains that maps AMP names to internal names, so AMP manifests work without renaming chains in the database.
The old convention made queries very hard to read. We now simply demand that users stay away from tables etc. whose name starts with `amp_`
lutter
force-pushed
the
lutter/amp-name
branch
from
176a0e6 to
349f58b
Compare
isum
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes two somewhat unrelated changes:
mainnetvsethereum-mainnet) For amp-powered subgraphs, it is expected that the manifest uses the amp name