graphprotocol / graphprotocol/graph-node
Chain name aliases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Do you want to request a feature or report a bug?
feature
What is the current behavior?
Every chain has a unique network identifier, like mainnet, matic, xdai. Some of these chains were renamed but their unique identifier stayed the same. Eventually, new developers will be confused because they do not intuitively understand why a subgraph running on Polygon should have matic as network identifier. Same for xDai which was renamed to Gnosis Chain.
Though, just changing these network identifiers would break all existing subgraphs that still have matic as network and not polygon.
What is the expected behavior?
I would recommend to introduce network identifier aliases, so we can start to communicate the new names but still support the old ones.
Example:
matic -> polygon
xdai -> gnosis-chain
Etc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating how graph-node validates and uses network identifiers, then trace the affected configuration and subgraph paths. Done means renamed identifiers such as polygon and gnosis-chain are accepted while existing matic and xdai subgraphs continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100