Skip to content

Edits #951

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 16, 2025
Merged

Edits #951

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/src/pages/en/subgraphs/upgrade-indexer.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ Originally designed as a transitional support, its primary purpose was to facili

### What it does

- Provides immediate query support for all newly deployed subgraphs.
- Provides immediate query support for all newly deployed Subgraphs.
- Functions as the sole supporting Indexer for each chain until indexing rewards are activated.

### What it does **not** do

- Does not permanently index subgraphs. Subgraph owners should curate subgraphs to use independent Indexers long term.
- Does not permanently index Subgraphs. Subgraph owners should curate Subgraphs to use independent Indexers long term.
- Does not compete for rewards. The Upgrade Indexer's participation on the Graph Network does not dilute rewards for other Indexers.
- Doesn't support Time Travel Queries (TTQ). All Subgraphs on the Upgrade Indexer are auto-pruned. If TTQs are needed on a Subgraph, [curation signal can be added](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to attract Indexers that will support this feature.

Expand Down