You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This outlines storage limits for Subgraphs that rely solely on [Edge & Node's Upgrade Indexer](/subgraphs/upgrade-indexer/). This policy is designed to ensure fair and optimized use of queries across the community.
10
+
11
+
To maintain performance and reliability across its infrastructure, Edge & Node is updating its Upgrade Indexer Subgraph storage policy. Free usage tiers remain available, but users who exceed specified limits will need to upgrade to a paid plan. Storage allocations and thresholds vary by feature.
12
+
13
+
### 1. Scope
14
+
15
+
This policy applies to all individual users, teams, chains, and dapps using Edge & Node's Upgrade Indexer in Subgraph Studio for storage and queries.
16
+
17
+
### 2. Fair Use Storage Limits
18
+
19
+
**Free Storage: Up to 10 GB**
20
+
21
+
Beyond that, pricing is variable and adjusts based on usage patterns, network conditions, infrastructure requirements, and specific use cases.
You can monitor your usage via [Subgraph Studio](https://thegraph.com/studio/).
26
+
27
+
### 3. Fair Use Limits
28
+
29
+
To preserve the stability of Edge & Node's Subgraph Studio and preserve the reliability of The Graph Network, the Edge & Node Support Team will monitor storage usage and take corresponding action with Subgraphs that have:
30
+
31
+
- Abnormally high or sustained bandwidth or storage usage beyond posted limits
32
+
- Circumvention of storage thresholds (e.g., use of multiple free-tier accounts)
33
+
34
+
The Edge & Node Support Team reserves the right to revise storage limits or impose temporary constraints for operational integrity.
35
+
36
+
If you exceed your included storage:
37
+
38
+
- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits
39
+
-[Add signal to the Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it
40
+
- You will receive multiple notifications and email alerts
41
+
- A grace period of 14 days will be provided to upgrade or reduce storage
42
+
43
+
Edge & Node's team is committed to helping users avoid unnecessary interruptions and will continue to support all web3 builders.
44
+
45
+
### 4. Subgraph Data Retention
46
+
47
+
Subgraphs inactive for over 14 days or Subgraphs that exceed free-tier storage limits will be subject to automatic data archival or deletion. Edge & Node's team will notify you before any such actions are taken.
48
+
49
+
### 5. Support
50
+
51
+
If you believe your usage is incorrectly flagged or have unique use cases (e.g. approved special request pending new Subgraph upgrade plan), reach out the Edge & Node team at [[email protected]](mailto:[email protected]).
Copy file name to clipboardExpand all lines: website/src/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,15 @@
2
2
title: Subgraph ID vs Deployment ID
3
3
---
4
4
5
+
Managing and accessing Subgraphs relies on two distinct identification systems: Subgraph IDs and Deployment IDs.
6
+
5
7
A Subgraph is identified by a Subgraph ID, and each version of the Subgraph is identified by a Deployment ID.
6
8
7
9
When querying a Subgraph, either ID can be used, though it is generally suggested that the Deployment ID is used due to its ability to specify a specific version of a Subgraph.
8
10
9
-
Here are some key differences between the two IDs: 
11
+
Both identifiers are accessible in [Subgraph Studio](https://thegraph.com/studio/):
12
+
13
+
10
14
11
15
## Deployment ID
12
16
@@ -18,10 +22,33 @@ Example endpoint that uses Deployment ID:
Using Deployment IDs for queries offers precise version control but comes with specific implications:
26
+
27
+
- Advantages: Complete control over which version you're querying, ensuring consistent results
28
+
- Challenges: Requires manual updates to query code when new Subgraph versions are published
29
+
- Use case: Ideal for production environments where stability and predictability are crucial
30
+
21
31
## Subgraph ID
22
32
23
33
The Subgraph ID is a unique identifier for a Subgraph. It remains constant across all versions of a Subgraph. It is recommended to use the Subgraph ID to query the latest version of a Subgraph, although there are some caveats.
24
34
25
35
Be aware that querying using Subgraph ID may result in queries being responded to by an older version of the Subgraph due to the new version needing time to sync. Also, new versions could introduce breaking schema changes.
26
36
27
37
Example endpoint that uses Subgraph ID: `https://gateway-arbitrum.network.thegraph.com/api/[api-key]/subgraphs/id/FL3ePDCBbShPvfRJTaSCNnehiqxsPHzpLud6CpbHoeKW`
38
+
39
+
Using Subgraph IDs comes with important considerations:
40
+
41
+
- Benefits: Automatically queries the latest version, reducing maintenance overhead
42
+
- Limitations: May encounter version synchronization delays or breaking schema changes
43
+
- Use case: Better suited for development environments or when staying current is more important than version stability
The Upgrade Indexer is a specialized Indexer operated by Edge & Node. It supports newly integrated chains within The Graph ecosystem and ensures new Subgraphs are immediately available for querying, eliminating potential downtime.
9
+
10
+
Originally designed as a transitional support, its primary purpose was to facilitate the migration of Subgraphs from the hosted service to the decentralized network. Currently, it supports newly deployed Subgraphs before the full Chain Integration Process (CIP) Indexing rewards are activated.
11
+
12
+
### What it does
13
+
14
+
- Provides immediate query support for all newly deployed Subgraphs.
15
+
- Functions as the sole supporting Indexer for each chain until indexing rewards are activated.
16
+
17
+
### What it does **not** do
18
+
19
+
- Does not permanently index Subgraphs. Subgraph owners should curate Subgraphs to use independent Indexers long term.
20
+
- Does not compete for rewards. The Upgrade Indexer's participation on the Graph Network does not dilute rewards for other Indexers.
21
+
- 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.
22
+
23
+
### Conclusion
24
+
25
+
The Edge & Node Upgrade Indexer is foundational in supporting chain integrations and mitigating data latency risks. It plays a critical role in scaling The Graph's decentralized infrastructure by ensuring immediate query support and fostering community-driven indexing.
0 commit comments