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
Copy file name to clipboardExpand all lines: website/src/pages/en/subgraphs/fair-use-policy.mdx
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,11 @@ title: Fair Use Policy
6
6
7
7
## Overview
8
8
9
-
This page outlines the fair usage of [Edge & Node's Upgrade Indexer](/subgraphs/upgrade-indexer/). This policy is designed to ensure the optimized use of queries and storage across the free-tier community.
9
+
This page outlines the fair usage of [Edge & Node's Upgrade Indexer](/subgraphs/upgrade-indexer/). This policy is designed to ensure the efficient use of queries and storage across the free-tier community.
10
10
11
-
Storage limits, sync thresholds, and usage requirements are explained below. Users who exceed specified limits will need to advance to a paid plan. We thank users for doing their part to maintain performance and reliability across Edge & Node's infrastructure.
11
+
Storage limits, sync thresholds, and usage requirements are explained below. Users who exceed specified limits will need to advance to a paid plan.
12
+
13
+
We thank users for doing their part to maintain performance and reliability across Edge & Node's infrastructure.
12
14
13
15
### 1. Scope
14
16
@@ -20,8 +22,7 @@ This policy applies to all individual users, teams, chains, and dapps using Edge
20
22
21
23
Free Storage: **Up to 10 GB**
22
24
23
-
Beyond that, pricing is variable and adjusts based on usage patterns, network conditions, infrastructure requirements, and specific use cases.
24
-
Note that Subgraphs of any size will be deleted after 30 days of dormancy (no usage) in order to make space for active Subgraphs.
25
+
Beyond that, pricing is variable and adjusts based on usage patterns, network conditions, infrastructure requirements, and specific use cases. Note that Subgraphs of any size will be deleted after 30 days of dormancy (no usage) in order to make space for active Subgraphs.
25
26
26
27
#### **Syncing Limits**
27
28
@@ -43,7 +44,7 @@ If you exceed your fair use limits, you will receive an email alert giving you a
43
44
44
45
- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits.
45
46
- If your subgraph references chains that receive indexing rewards, [indicated by double check marks in the Subgraphs column here](/subgraphs/best-practices/pruning/)), then [publish your Subgraph to the Network](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) and [add signal](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it.
46
-
- If your Subgraph references a chain that DOES NOT receive indexing rewards, reach out to InfraDAO [indexing@infradao.com] or @jmulq on Telegram to discuss options that meet your technical needs.
47
+
- If your Subgraph references a chain that **does not** receive indexing rewards, reach out to InfraDAO [indexing@infradao.com] or @jmulq on Telegram to discuss options that meet your technical needs.
47
48
48
49
Edge & Node's team is committed to helping users avoid unnecessary interruptions and will continue to support all builders.
0 commit comments