From d9fe936bba6118cd321d31bbd9fc40744a9ad405 Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Mon, 23 Jun 2025 20:08:56 +0100 Subject: [PATCH 1/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 64 +++++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 31 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index 892d20a..c129833 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -1,42 +1,44 @@ + +--- # Upcoming Eligibility Criteria -We will announce changes to the eligibility criteria in the table below. Once the change goes live then it will be reflected in the eligibility criteria section of this document. +**We will announce changes to the eligibility criteria in the table below.** Once the change goes live then it will be reflected in the `Indexing Rewards Eligibility Criteria` section of this document. -| Upcoming Requirement | Justification | Date Updated/Introduced (YYYY-MM-DD)| -|----------------------|---------------|-------------------------------------| -| **Requirement 1:** | This is a placeholder for future criteria, watch this space to stay informed. We will also announce any upcoming requirements via our existing official channels. | YYYY-MM-DD | +| Upcoming Requirement | Justification | Date This Eligibility Requirement Will Be Updated/Introduced (YYYY-MM-DD) | +|----------------------|---------------|---------------------------------------------------------------------------| +| **Requirement 1:** | This is a placeholder for future criteria, watch this space to stay informed. We will also announce any upcoming requirements via our existing official channels. | `YYYY-MM-DD` | > **Note**: -> -> When announcing new eligibility criteria we will allow a window for indexers to prepare their infrastructure before any new/updated criteria goes live, refer to the `Date Updated/Introduced (YYYY-MM-DD)` column to see when upcoming eligibility criteria will merge. +> When announcing new eligibility criteria we will allow a window for indexers to prepare their infrastructure before any new/updated criteria goes live, refer to the `Date This Eligibility Requirement Will Be Updated/Introduced (YYYY-MM-DD)` column to see when upcoming eligibility criteria will merge. We would typically allow a 14 day window after announcing a change before it goes live. -# Eligibility Criteria +--- +# The Indexing Rewards Eligibility Criteria: The Service Quality Oracle determines which indexers are eligible to receive indexing rewards using a threshold rewards algorithm that operates by checking indexers meet the following criteria: -1. Indexers must be online for 5+ days in a given 28 day rolling period. - 1. To be online an indexer must serve at least 1 qualifying query on 10 different subgraphs - 1. A qualifying query is one where: - 1. The query response HTTP status was 200 OK, indicating query success. - 2. The query response latency was <5,000 ms. - 3. The query was served <50,000 blocks behind chainhead. - 4. The subgraph had at least 500 GRT in curation signal at the time that the query was served. +1. **Indexers must be online for 5+ days in a given 28 day rolling period.** + 1. **To be online, an indexer must serve at least 1 qualifying query on 10 different subgraphs** + 1. **A qualifying query is one where:** + 1. **The query response HTTP status was 200 OK, indicating query success.** + 2. **The query response latency was <5,000 ms.** + 3. **The query was served <50,000 blocks behind chainhead.** + 4. **The subgraph had at least 500 GRT in curation signal at the time that the query was served.** + +All four qualifying query criteria must be satisfied simultaneously for a query to count towards the daily requirement. +As above, the qualifying query criteria must be satisfied on 10+ subgraphs per day, for 5+ days in any given 28 day rolling window. +Eligibility for indexing rewards is typically refreshed daily via the ServiceQualityOracle contract. > **Note**: -> -> All four quality criteria must be satisfied simultaneously for a query to count towards the daily requirement. -> -> The above query criteria must be satisfied on 10+ subgraphs per day, for 5+ days in any given 28 day rolling window. -> -> Issuance eligibility is refreshed daily via the ServiceQualityOracle contract. -> -> Once an indexer has qualified for issuance via the ServiceQualityOracle contract, they can claim indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if the requirements change. - - - -| Requirement | Justification | Date Updated/Introduced (YYYY-MM-DD)| -|-------------|---------------|-------------------------------------| -| **Query Status:** The query must have a `200 OK` HTTP response status indicating query success | Indexer infrastructure needs to be capable of serving successful queries to benefit data consumers. | TBD (at genesis of the SQO) | -| **Query Latency:** The query response must be delivered to the gateway in `< 5,000 ms` | Fast query responses are important to data consumers. | TBD (at genesis of the SQO) | -| **Query Freshness:** The query must be served from a subgraph that is `< 50,000 blocks` behind chainhead | Data needs to be fresh to be useful to data consumers. | TBD (at genesis of the SQO) | -| **Subgraph Signal:** The subgraph needs to have `≥ 500 GRT` in curation signal at the time when the query was served. | Indexers are encouraged to serve data on subgraphs that have curation signal. This also creates an economic barrier against those that prefer to game the system. | TBD (at genesis of the SQO) | +> * Once an indexer has successfully qualified for issuance by satisfying the above criteria, and a corresponding transaction has been placed on chain by an authorizde Oracle into the ServiceQualityOracle contract, the now eligible indexer can continue claiming indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if the issuance eligibility requirements change thereafter. + +--- + + +#### Below is a table showing Justification, date and notes for the above eligibility criteria + +| Requirement | Justification | Date That Requirement Was Last Updated/Introduced (YYYY-MM-DD) | Notes | +|-------------|---------------|----------------------------------------------------------------|-------| +| **Query Status:** The query must have a `200 OK` HTTP response status indicating query success | Indexer infrastructure needs to be capable of serving successful queries to benefit data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | +| **Query Latency:** The query response must be delivered to the gateway in `< 5,000 ms` | Fast query responses are important to data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | +| **Query Freshness:** The query must be served from a subgraph that is `< 50,000 blocks` behind chainhead | Data needs to be fresh to be useful to data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | +| **Subgraph Signal:** The subgraph needs to have `≥ 500 GRT` in curation signal at the time when the query was served. | Indexers are encouraged to serve data on subgraphs that have curation signal. This also creates an economic barrier against those that prefer to game the system. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | From aedaedaeb85f913a61b0451ccca019d77b789ada Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Mon, 23 Jun 2025 20:17:27 +0100 Subject: [PATCH 2/8] Update ELIGIBILITY_CRITERIA.md Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index c129833..8258614 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -2,17 +2,17 @@ --- # Upcoming Eligibility Criteria -**We will announce changes to the eligibility criteria in the table below.** Once the change goes live then it will be reflected in the `Indexing Rewards Eligibility Criteria` section of this document. +**We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the `Active Eligibility Criteria` section of this document. -| Upcoming Requirement | Justification | Date This Eligibility Requirement Will Be Updated/Introduced (YYYY-MM-DD) | -|----------------------|---------------|---------------------------------------------------------------------------| -| **Requirement 1:** | This is a placeholder for future criteria, watch this space to stay informed. We will also announce any upcoming requirements via our existing official channels. | `YYYY-MM-DD` | +| Upcoming Requirement | Justification | Date Requirement Will Be Updated/Introduced (YYYY-MM-DD) | +|----------------------|---------------|----------------------------------------------------------| +| **Example Requirement:** | This is a placeholder for future criteria. Watch this space to stay informed. We will also announce any upcoming requirements via our existing official channels. | `YYYY-MM-DD` | > **Note**: -> When announcing new eligibility criteria we will allow a window for indexers to prepare their infrastructure before any new/updated criteria goes live, refer to the `Date This Eligibility Requirement Will Be Updated/Introduced (YYYY-MM-DD)` column to see when upcoming eligibility criteria will merge. We would typically allow a 14 day window after announcing a change before it goes live. +> When announcing new eligibility criteria we will allow a window for indexers to prepare their infrastructure before any new/updated criteria goes live, refer to the `Date Requirement Will Be Updated/Introduced (YYYY-MM-DD)` column to see when an upcoming eligibility criterion will take effect. We will typically allow a 14-day window after announcing a change before it goes live. --- -# The Indexing Rewards Eligibility Criteria: +# Active Eligibility Criteria The Service Quality Oracle determines which indexers are eligible to receive indexing rewards using a threshold rewards algorithm that operates by checking indexers meet the following criteria: From 6b7a6b8db73ce26a008203b580a7275be2b7931e Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Mon, 23 Jun 2025 22:05:46 +0100 Subject: [PATCH 3/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 54 ++++++++++++++++++++++++++--------------- 1 file changed, 34 insertions(+), 20 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index 8258614..42d9557 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -1,44 +1,58 @@ --- + # Upcoming Eligibility Criteria **We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the `Active Eligibility Criteria` section of this document. | Upcoming Requirement | Justification | Date Requirement Will Be Updated/Introduced (YYYY-MM-DD) | |----------------------|---------------|----------------------------------------------------------| -| **Example Requirement:** | This is a placeholder for future criteria. Watch this space to stay informed. We will also announce any upcoming requirements via our existing official channels. | `YYYY-MM-DD` | +| **Example Requirement:** | This is a placeholder for future criteria. Watch this space to stay informed. We will also announce upcoming requirements via official channels. | `YYYY-MM-DD` | > **Note**: -> When announcing new eligibility criteria we will allow a window for indexers to prepare their infrastructure before any new/updated criteria goes live, refer to the `Date Requirement Will Be Updated/Introduced (YYYY-MM-DD)` column to see when an upcoming eligibility criterion will take effect. We will typically allow a 14-day window after announcing a change before it goes live. +> We will typically allow a 14 day window after announcing a change before it goes live. --- + # Active Eligibility Criteria -The Service Quality Oracle determines which indexers are eligible to receive indexing rewards using a threshold rewards algorithm that operates by checking indexers meet the following criteria: +The following criteria is used to identify indexers that should be eligible to receive indexing rewards. -1. **Indexers must be online for 5+ days in a given 28 day rolling period.** - 1. **To be online, an indexer must serve at least 1 qualifying query on 10 different subgraphs** - 1. **A qualifying query is one where:** - 1. **The query response HTTP status was 200 OK, indicating query success.** - 2. **The query response latency was <5,000 ms.** - 3. **The query was served <50,000 blocks behind chainhead.** - 4. **The subgraph had at least 500 GRT in curation signal at the time that the query was served.** +- **Days Online Requirement:** Indexers must be online for **5+ days** in a given **28 day** rolling period for rewards eligibility. +- **Daily Query Requirement:** To be online, an indexer must serve at least **1 qualifying query** on **10 different subgraphs**. +- **Query Quality Requirements:** A qualifying query is one that simutanousely meets **all** of the following criteria: + - Query Response HTTP Status: **200 OK**. + - Query Response Latency: **< 5,000 ms**. + - Query Freshness: **< 50,000 blocks** behind chainhead. + - Subgraph Curation Signal: **≥ 500 GRT**. -All four qualifying query criteria must be satisfied simultaneously for a query to count towards the daily requirement. -As above, the qualifying query criteria must be satisfied on 10+ subgraphs per day, for 5+ days in any given 28 day rolling window. Eligibility for indexing rewards is typically refreshed daily via the ServiceQualityOracle contract. > **Note**: -> * Once an indexer has successfully qualified for issuance by satisfying the above criteria, and a corresponding transaction has been placed on chain by an authorizde Oracle into the ServiceQualityOracle contract, the now eligible indexer can continue claiming indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if the issuance eligibility requirements change thereafter. +> Once an indexer has successfully qualified for issuance by satisfying all of the above criteria, and a corresponding transaction has been submitted on chain by an authorized Oracle into the ServiceQualityOracle contract, the now eligible indexer can continue claiming indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if issuance eligibility requirements change. --- +# Eligibility Requirements Changelog + +This table tracks changes to eligibility requirements over time. -#### Below is a table showing Justification, date and notes for the above eligibility criteria +| Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | +|----------------------|---------------------|-----------------------------|-------------|---------------|-------| +| **Days Online** | Indexers must be online for **5+ days** in a given **28 day** rolling period for rewards eligibility. | TBD | Initial | Encourages indexers familiarize themselves with infrastructure maintainance and ongoing operations. | Planned for Service Quality Oracle launch | +| **Daily Query Requirement** | Must serve **≥1 qualifying query** on **≥10 different subgraphs** per day for a day to count towards the online requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | +| **Query Quality Requirements** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | + +--- -| Requirement | Justification | Date That Requirement Was Last Updated/Introduced (YYYY-MM-DD) | Notes | -|-------------|---------------|----------------------------------------------------------------|-------| -| **Query Status:** The query must have a `200 OK` HTTP response status indicating query success | Indexer infrastructure needs to be capable of serving successful queries to benefit data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | -| **Query Latency:** The query response must be delivered to the gateway in `< 5,000 ms` | Fast query responses are important to data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | -| **Query Freshness:** The query must be served from a subgraph that is `< 50,000 blocks` behind chainhead | Data needs to be fresh to be useful to data consumers. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | -| **Subgraph Signal:** The subgraph needs to have `≥ 500 GRT` in curation signal at the time when the query was served. | Indexers are encouraged to serve data on subgraphs that have curation signal. This also creates an economic barrier against those that prefer to game the system. | TBD | This requirement is planned to be introduced at launch of the Service Quality Oracle | +# Future Example Changes + +The following are examples of how future changes would be recorded in the changelog above: + +| Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | +|----------------------|---------------------|------------------------------|------------|---------------|-------| +| **Days Online** | Must be online for **10+ days** in a **28 day** rolling period | YYYY-MM-DD | Updated | Increase reliability requirements based on network maturity | Increased from 5+ days | +| **Query Latency** | Query response latency must be **< 1,000 ms** | YYYY-MM-DD | Updated | Improve user experience with faster responses | Tightened from < 5,000 ms | +| **Indexer Stake** | Indexer must have **≥ 100,000 GRT** staked | YYYY-MM-DD | New | Ensure indexers have skin in the game for quality service | New requirement added | + +--- From f9d4beef2e5a16ec44f6ed3a5f9374442088015c Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Tue, 24 Jun 2025 12:46:56 +0100 Subject: [PATCH 4/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index 42d9557..a807f08 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -3,7 +3,7 @@ # Upcoming Eligibility Criteria -**We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the `Active Eligibility Criteria` section of this document. +**We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the [Active Eligibility Criteria](https://github.com/graphprotocol/service-quality-oracle/blob/main/ELIGIBILITY_CRITERIA.md#active-eligibility-criteria) section of this document. | Upcoming Requirement | Justification | Date Requirement Will Be Updated/Introduced (YYYY-MM-DD) | |----------------------|---------------|----------------------------------------------------------| @@ -18,8 +18,8 @@ The following criteria is used to identify indexers that should be eligible to receive indexing rewards. -- **Days Online Requirement:** Indexers must be online for **5+ days** in a given **28 day** rolling period for rewards eligibility. -- **Daily Query Requirement:** To be online, an indexer must serve at least **1 qualifying query** on **10 different subgraphs**. +- **Days Online Requirement:** Indexers must be active for **5+ days** in a given **28 day** period for rewards eligibility. +- **Daily Query Requirement:** To be active, an indexer must serve at least **1 qualifying query** on **10 different subgraphs**. - **Query Quality Requirements:** A qualifying query is one that simutanousely meets **all** of the following criteria: - Query Response HTTP Status: **200 OK**. - Query Response Latency: **< 5,000 ms**. @@ -29,30 +29,30 @@ The following criteria is used to identify indexers that should be eligible to r Eligibility for indexing rewards is typically refreshed daily via the ServiceQualityOracle contract. > **Note**: -> Once an indexer has successfully qualified for issuance by satisfying all of the above criteria, and a corresponding transaction has been submitted on chain by an authorized Oracle into the ServiceQualityOracle contract, the now eligible indexer can continue claiming indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if issuance eligibility requirements change. +> Once an indexer has successfully qualified for indexing rewards by satisfying the active eligibility criteria, and a corresponding transaction has been submitted on chain by an authorized Oracle into the ServiceQualityOracle contract, the now eligible indexer can continue claiming indexing rewards from the protocol for the duration of the qualification period (default is 14 days), even if the active eligibility criteria change. --- # Eligibility Requirements Changelog -This table tracks changes to eligibility requirements over time. +This table tracks changes to the indexing rewards eligibility requirements over time. | Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | |----------------------|---------------------|-----------------------------|-------------|---------------|-------| -| **Days Online** | Indexers must be online for **5+ days** in a given **28 day** rolling period for rewards eligibility. | TBD | Initial | Encourages indexers familiarize themselves with infrastructure maintainance and ongoing operations. | Planned for Service Quality Oracle launch | -| **Daily Query Requirement** | Must serve **≥1 qualifying query** on **≥10 different subgraphs** per day for a day to count towards the online requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | -| **Query Quality Requirements** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | +| **Indexer Activity** | Indexers must be active for **5+ days** in a given **28 day** period for indexing rewards eligibility. | TBD | Initial | Encourages indexers familiarize themselves with infrastructure maintainance and ongoing operations. | Planned for Service Quality Oracle launch | +| **Query Qualification** | Indexers must serve **≥1 qualifying query** on **≥10 different subgraphs** in a day for the day to count towards the days active requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | +| **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | --- # Future Example Changes -The following are examples of how future changes would be recorded in the changelog above: +The following are examples of how future changes could be recorded in the changelog above: | Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | |----------------------|---------------------|------------------------------|------------|---------------|-------| -| **Days Online** | Must be online for **10+ days** in a **28 day** rolling period | YYYY-MM-DD | Updated | Increase reliability requirements based on network maturity | Increased from 5+ days | -| **Query Latency** | Query response latency must be **< 1,000 ms** | YYYY-MM-DD | Updated | Improve user experience with faster responses | Tightened from < 5,000 ms | -| **Indexer Stake** | Indexer must have **≥ 100,000 GRT** staked | YYYY-MM-DD | New | Ensure indexers have skin in the game for quality service | New requirement added | +| **Indexer Activity** | Indexers must be active for **10+ days** in a given **28 day** period for indexing rewards eligibility. | YYYY-MM-DD | **Updated** | Gradually increase activity requirements to encourage more consistent indexer participation in the network. | **Indexer Activity** increased to **10+ days** in a given 28 day period from **5+ days** in a given 28 day period | +| **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 1,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | YYYY-MM-DD | **Updated** | Ensure that indexer infrastructure is capable of sub-second query responses to help improve data consumer experience through faster responses. | **Query Response Latency** tightened to **< 1,000 ms** from **< 5,000 ms**. Other query response quality requirements unchanged. | +| **Query Volume** | Indexers must have served **500+ queries** in the last 28 days. | YYYY-MM-DD | **New** | Encourage indexers to participate in the network to a greater degree, while still ensuring that acheiving indexing rewards eligibility is feasible for all active indexers. | New requirement added. | --- From 0c4ac67752543e98de6d2cc600453c2338d6947f Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Tue, 24 Jun 2025 12:59:16 +0100 Subject: [PATCH 5/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index a807f08..53eb3d5 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -40,7 +40,7 @@ This table tracks changes to the indexing rewards eligibility requirements over | Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | |----------------------|---------------------|-----------------------------|-------------|---------------|-------| | **Indexer Activity** | Indexers must be active for **5+ days** in a given **28 day** period for indexing rewards eligibility. | TBD | Initial | Encourages indexers familiarize themselves with infrastructure maintainance and ongoing operations. | Planned for Service Quality Oracle launch | -| **Query Qualification** | Indexers must serve **≥1 qualifying query** on **≥10 different subgraphs** in a day for the day to count towards the days active requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | +| **Query Qualification** | Indexers must serve **≥1 qualifying query** on **≥10 different subgraphs** in a day for the day to count towards the **Indexer Activity** requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | | **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | --- From 11a2a9178c4a8b06374981e7615545571e050a1a Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Tue, 24 Jun 2025 14:53:01 +0100 Subject: [PATCH 6/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index 53eb3d5..c6d89d9 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -1,3 +1,4 @@ +This document defines the requirements an Indexer must meet to be eligible for indexing rewards. It includes the current active criteria, a schedule of any upcoming changes, and a log of all historical requirements. The goal is to provide a transparent and predictable set of standards for all network participants. --- From 4c0881152584782a0f7e8b05ac655a3b6102e54d Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Tue, 24 Jun 2025 14:55:32 +0100 Subject: [PATCH 7/8] Update ELIGIBILITY_CRITERIA.md --- ELIGIBILITY_CRITERIA.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index c6d89d9..ba6d420 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -17,11 +17,11 @@ This document defines the requirements an Indexer must meet to be eligible for i # Active Eligibility Criteria -The following criteria is used to identify indexers that should be eligible to receive indexing rewards. +The following criteria are used to identify indexers that should be eligible to receive indexing rewards. - **Days Online Requirement:** Indexers must be active for **5+ days** in a given **28 day** period for rewards eligibility. - **Daily Query Requirement:** To be active, an indexer must serve at least **1 qualifying query** on **10 different subgraphs**. -- **Query Quality Requirements:** A qualifying query is one that simutanousely meets **all** of the following criteria: +- **Query Quality Requirements:** A qualifying query is one that simultaneously meets **all** of the following criteria: - Query Response HTTP Status: **200 OK**. - Query Response Latency: **< 5,000 ms**. - Query Freshness: **< 50,000 blocks** behind chainhead. @@ -40,7 +40,7 @@ This table tracks changes to the indexing rewards eligibility requirements over | Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | |----------------------|---------------------|-----------------------------|-------------|---------------|-------| -| **Indexer Activity** | Indexers must be active for **5+ days** in a given **28 day** period for indexing rewards eligibility. | TBD | Initial | Encourages indexers familiarize themselves with infrastructure maintainance and ongoing operations. | Planned for Service Quality Oracle launch | +| **Indexer Activity** | Indexers must be active for **5+ days** in a given **28 day** period for indexing rewards eligibility. | TBD | Initial | Encourages indexers to familiarize themselves with infrastructure maintenance and ongoing operations. | Planned for Service Quality Oracle launch | | **Query Qualification** | Indexers must serve **≥1 qualifying query** on **≥10 different subgraphs** in a day for the day to count towards the **Indexer Activity** requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | | **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | @@ -54,6 +54,6 @@ The following are examples of how future changes could be recorded in the change |----------------------|---------------------|------------------------------|------------|---------------|-------| | **Indexer Activity** | Indexers must be active for **10+ days** in a given **28 day** period for indexing rewards eligibility. | YYYY-MM-DD | **Updated** | Gradually increase activity requirements to encourage more consistent indexer participation in the network. | **Indexer Activity** increased to **10+ days** in a given 28 day period from **5+ days** in a given 28 day period | | **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 1,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | YYYY-MM-DD | **Updated** | Ensure that indexer infrastructure is capable of sub-second query responses to help improve data consumer experience through faster responses. | **Query Response Latency** tightened to **< 1,000 ms** from **< 5,000 ms**. Other query response quality requirements unchanged. | -| **Query Volume** | Indexers must have served **500+ queries** in the last 28 days. | YYYY-MM-DD | **New** | Encourage indexers to participate in the network to a greater degree, while still ensuring that acheiving indexing rewards eligibility is feasible for all active indexers. | New requirement added. | +| **Query Volume** | Indexers must have served **500+ queries** in the last 28 days. | YYYY-MM-DD | **New** | Encourage indexers to participate in the network to a greater degree, while still ensuring that achieving indexing rewards eligibility is feasible for all active indexers. | New requirement added. | --- From 0d8e7b6b09a6728d9ba33acfe6d086383a2c4e25 Mon Sep 17 00:00:00 2001 From: MoonBoi9001 Date: Thu, 26 Jun 2025 15:23:34 +0100 Subject: [PATCH 8/8] Remove example changelog --- ELIGIBILITY_CRITERIA.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/ELIGIBILITY_CRITERIA.md b/ELIGIBILITY_CRITERIA.md index ba6d420..da63911 100644 --- a/ELIGIBILITY_CRITERIA.md +++ b/ELIGIBILITY_CRITERIA.md @@ -38,22 +38,10 @@ Eligibility for indexing rewards is typically refreshed daily via the ServiceQua This table tracks changes to the indexing rewards eligibility requirements over time. -| Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | +| Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type: Initial, Updated, New, Removed | Justification | Notes | |----------------------|---------------------|-----------------------------|-------------|---------------|-------| | **Indexer Activity** | Indexers must be active for **5+ days** in a given **28 day** period for indexing rewards eligibility. | TBD | Initial | Encourages indexers to familiarize themselves with infrastructure maintenance and ongoing operations. | Planned for Service Quality Oracle launch | | **Query Qualification** | Indexers must serve **≥1 qualifying query** on **≥10 different subgraphs** in a day for the day to count towards the **Indexer Activity** requirement. | TBD | Initial | Encourages indexers to become familiar with the process of syncing a range of subgraphs. | Planned for Service Quality Oracle launch | | **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 5,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | TBD | Initial | *•* Indexer infrastructure needs to serve successful queries to benefit data consumers.
*•* Fast query responses are important to data consumers.
*•* Encourages indexers to sync to chainhead.
*•* Creates a barrier against gaming eligibility requirements. | Planned for Service Quality Oracle launch | --- - -# Future Example Changes - -The following are examples of how future changes could be recorded in the changelog above: - -| Requirement Category | Requirement Details | Effective Date (YYYY-MM-DD) | Change Type | Justification | Notes | -|----------------------|---------------------|------------------------------|------------|---------------|-------| -| **Indexer Activity** | Indexers must be active for **10+ days** in a given **28 day** period for indexing rewards eligibility. | YYYY-MM-DD | **Updated** | Gradually increase activity requirements to encourage more consistent indexer participation in the network. | **Indexer Activity** increased to **10+ days** in a given 28 day period from **5+ days** in a given 28 day period | -| **Query Response Quality** | *•* Query Response HTTP Status: **200 OK**
*•* Query Response Latency: **< 1,000 ms**
*•* Query Freshness: **< 50,000 blocks** behind chainhead.
*•* Subgraph Curation Signal: **≥ 500 GRT**. | YYYY-MM-DD | **Updated** | Ensure that indexer infrastructure is capable of sub-second query responses to help improve data consumer experience through faster responses. | **Query Response Latency** tightened to **< 1,000 ms** from **< 5,000 ms**. Other query response quality requirements unchanged. | -| **Query Volume** | Indexers must have served **500+ queries** in the last 28 days. | YYYY-MM-DD | **New** | Encourage indexers to participate in the network to a greater degree, while still ensuring that achieving indexing rewards eligibility is feasible for all active indexers. | New requirement added. | - ----