|
| 1 | +# Network Arbitration Policy for Subgraphs |
| 2 | + |
| 3 | +> **Note**: This policy applies to **subgraphs** specifically. The Networks Registry tracks multiple Graph services (subgraphs, firehose, substreams, token API), but arbitration is currently only applicable to subgraph indexing and querying. |
| 4 | +
|
| 5 | +## What is Arbitration? |
| 6 | + |
| 7 | +Arbitration is The Graph Network's dispute resolution system for subgraphs. It allows fishermen to challenge indexers who provide incorrect query responses or Proofs of Indexing (POIs). If proven incorrect, the indexer is penalized (slashed) and the fisherman receives a reward. |
| 8 | + |
| 9 | +This system ensures data integrity and indexer accountability on The Graph Network. |
| 10 | + |
| 11 | +For complete details, see: |
| 12 | +- [GIP-0008: Timeline for Sunsetting Hosted Service](https://snapshot.org/#/council.graphprotocol.eth/proposal/0xbdd884654a393620a7e8665b4289201b7542c3ee62becfad133e951b0c408444) - Introduced the Feature Support Matrix |
| 13 | +- [Arbitration Charter](https://github.com/graphprotocol/graph-improvement-proposals/blob/main/gips/0009-arbitration-charter.md) - Detailed arbitration rules and procedures |
| 14 | + |
| 15 | +## Default Rule |
| 16 | + |
| 17 | +Networks with indexing rewards (`issuanceRewards: true`) support both query and indexing arbitration on The Graph Network unless explicitly documented as exceptions in the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). |
| 18 | + |
| 19 | +This is a bidirectional relationship: |
| 20 | +- **Indexing rewards enabled** → Arbitration support enabled |
| 21 | +- **Arbitration support enabled** → Indexing rewards enabled |
| 22 | + |
| 23 | +## Checking Arbitration Support |
| 24 | + |
| 25 | +To verify if a network supports arbitration: |
| 26 | + |
| 27 | +1. Check the [Networks Table](./networks-table.md) |
| 28 | +2. Look for ✅ in the **"Indexing Rewards"** column |
| 29 | +3. If ✅ present → Network has full arbitration support (query + indexing) |
| 30 | +4. If no ✅ → Network does not have arbitration support |
| 31 | +5. For rare exceptions, check the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) |
| 32 | + |
| 33 | +## Examples |
| 34 | + |
| 35 | +- **Ethereum** (`issuanceRewards: true`) → ✅ Full arbitration support |
| 36 | +- **Near** (`issuanceRewards: false`) → ❌ No arbitration support |
| 37 | + |
| 38 | +## Governance |
| 39 | + |
| 40 | +Per [GGP-0062](https://snapshot.org/#/s:council.graphprotocol.eth/proposal/0x4eff14202f6204c0927860a9adff865fce33c32b6cbe7054227457631ee261b9): |
| 41 | + |
| 42 | +**Network-level (managed in this registry)**: |
| 43 | +- **The Graph Foundation** (with Technical Advisory Board review) has authority to add or remove indexing rewards for networks via the `issuanceRewards` field |
| 44 | +- Since indexing rewards determine arbitration support, this authority also controls network arbitration eligibility |
| 45 | + |
| 46 | +**Feature-level (managed in Feature Support Matrix)**: |
| 47 | +- **The Graph Council** can determine which new graph-node features or data source types are eligible for indexing rewards and arbitration |
| 48 | +- These decisions are documented in the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) |
| 49 | + |
| 50 | +### Updating Indexing Rewards in the Registry |
| 51 | +When adding/removing indexing rewards to networks, the following steps must be taken: |
| 52 | +1. PR with the updated `issuanceRewards` field is opened by the maintainers or the Foundation |
| 53 | +2. PR is reviewed by the maintainers |
| 54 | +3. Transaction enabling/disabling rewards is executed on chain |
| 55 | +4. PR is merged by the maintainers or the Foundation, and the registry is published |
| 56 | + |
| 57 | +## Relationship with Feature Support Matrix |
| 58 | + |
| 59 | +Historically, both network support and indexing rewards were documented in the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) in the indexer repository. This created duplication with the Networks Registry. |
| 60 | + |
| 61 | +**New approach (established by this documentation)**: |
| 62 | +- **Networks Registry** (`issuanceRewards` field) = Source of truth for which networks have indexing rewards |
| 63 | +- **Feature Support Matrix** = Documents graph-node features and arbitration rules, references registry for network-level data |
| 64 | + |
| 65 | +This separation eliminates duplication and clarifies ownership: network metadata lives in the registry, graph-node behavior lives in the feature matrix. |
| 66 | + |
| 67 | +## Related Documentation |
| 68 | + |
| 69 | +- [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) - Graph-node features and arbitration policy |
| 70 | +- [Networks Table](./networks-table.md) - Complete list of supported networks |
| 71 | +- [GIP-0008](https://snapshot.org/#/council.graphprotocol.eth/proposal/0xbdd884654a393620a7e8665b4289201b7542c3ee62becfad133e951b0c408444) - Introduced the Feature Support Matrix |
| 72 | +- [Arbitration Charter](https://github.com/graphprotocol/graph-improvement-proposals/blob/main/gips/0009-arbitration-charter.md) - Detailed arbitration rules and procedures |
| 73 | +- [GGP-0062](https://snapshot.org/#/s:council.graphprotocol.eth/proposal/0x4eff14202f6204c0927860a9adff865fce33c32b6cbe7054227457631ee261b9) - Governance structure for feature matrix |
0 commit comments