Skip to content

Commit 7d664a7

Browse files
committed
Adding two docs
1 parent 92488fc commit 7d664a7

File tree

3 files changed

+110
-0
lines changed

3 files changed

+110
-0
lines changed

website/src/pages/en/subgraphs/_meta.js

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,6 @@ export default {
88
billing: '',
99
guides: titles.guides,
1010
'best-practices': titles['best-practices'],
11+
'fair-use-policy': '',
12+
'upgrade-indexer': 'Upgrade Indexer',
1113
}
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Fair Use Policy
3+
---
4+
5+
> Effective Date: May 15, 2025
6+
7+
## Overview
8+
9+
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.
22+
23+
Reach out to Edge & Node at [[email protected]](mailto:[email protected]) to discuss options that meet your technical needs.
24+
25+
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]. 31 changes: 31 additions & 0 deletions31
52+
website/src/pages/en/subgraphs/subgraph-studio-faq.mdx Original file line number Original file line Diff line number Diff line change @@ -0,0 +1,31 @@
53+
54+
---
55+
56+
## title: Subgraph Studio FAQs
57+
58+
## 1. What is Subgraph Studio?
59+
60+
[Subgraph Studio](https://thegraph.com/studio/) is a dapp for creating, managing, and publishing Subgraphs and API keys.
61+
62+
## 2. How do I create an API Key?
63+
64+
To create an API, navigate to Subgraph Studio and connect your wallet. You will be able to click the API keys tab at the top. There, you will be able to create an API key.
65+
66+
## 3. Can I create multiple API Keys?
67+
68+
Yes! You can create multiple API Keys to use in different projects. Check out the link [here](https://thegraph.com/studio/apikeys/).
69+
70+
## 4. How do I restrict a domain for an API Key?
71+
72+
After creating an API Key, in the Security section, you can define the domains that can query a specific API Key.
73+
74+
## 5. Can I transfer my Subgraph to another owner?
75+
76+
Yes, Subgraphs that have been published to Arbitrum One can be transferred to a new wallet or a Multisig. You can do so by clicking the three dots next to the 'Publish' button on the Subgraph's details page and selecting 'Transfer ownership'.
77+
78+
Note that you will no longer be able to see or edit the Subgraph in Studio once it has been transferred.
79+
80+
## 6. How do I find query URLs for Subgraphs if I’m not the developer of the Subgraph I want to use?
81+
82+
You can find the query URL of each Subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the Subgraph you’re interested in. You can then replace the `<api_key>` placeholder with the API key you wish to leverage in Subgraph Studio.
83+
84+
Remember that you can create an API key and query any Subgraph published to the network, even if you build a Subgraph yourself. These queries via the new API key, are paid queries as any other on the network.
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Edge and Node Upgrade Indexer
3+
---
4+
5+
## Overview
6+
7+
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.
8+
9+
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.
10+
11+
### What it does:
12+
13+
- Provides immediate query support for all newly deployed subgraphs.
14+
- Functions as the sole supporting Indexer for each chain until indexing rewards are activated.
15+
16+
### What it does **not** do:
17+
18+
- Does not permanently index subgraphs. Subgraph owners should curate subgraphs to use independent Indexers long term.
19+
- Does not compete for rewards. The Upgrade Indexer's participation on the Graph Network does not dilute rewards for other Indexers.
20+
- 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.
21+
22+
### Conclusion
23+
24+
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

Comments
 (0)