The Graph parameters
17 rules in 5 groups, as the chain itself states them, read every hour
Network
How The Graph's time is divided.
-
Epoch length
How many Ethereum blocks make an epoch, the unit allocations and rewards are counted in.
- 7,200 blocks
- About 1 day
Indexers and delegation
What an indexer stakes to serve subgraphs, and how much delegation it can take.
-
Minimum provision
The least an indexer must provision to the Subgraph Service to serve subgraphs.
- 100,000 GRT
-
Maximum provision
The most an indexer may provision to the Subgraph Service.
- No limit
-
Delegation cap
How many times its own provision an indexer may use in delegated stake. Delegation past it earns nothing extra.
- 16×
-
Thawing period
How long undelegated or unprovisioned GRT stays locked before it can be withdrawn. It earns nothing meanwhile.
- 28 days
-
Longest thawing period
The longest thawing period any provision on The Graph may set.
- 28 days
-
Stake locked per fee
How many times the query fees it collects an indexer must keep locked, as a guarantee while they can be disputed.
- 10×
-
Delegators slashed
Whether delegated stake can be slashed along with the indexer's own.
- No
Disputes and slashing
How anyone can dispute an indexer's work, and what a dispute it loses costs it.
-
Dispute period
How long after a query or an allocation it can still be disputed.
- 28 days
-
Dispute deposit
What the disputer (the fisherman) puts down, lost if the dispute is rejected.
- 10,000 GRT
-
Largest slash
The most of an indexer's provision one dispute can slash.
- 10%
-
Fisherman's reward
The share of a slash paid to the fisherman who won the dispute; the rest is burned.
- 50%
Rewards
When an allocation earns indexing rewards, and how query fees are shared.
-
Proof deadline
An allocation must present a proof of indexing at least this often; past it, closing the allocation earns no indexing rewards.
- 28 days
-
Curators' share of fees
The share of each query fee paid to the subgraph's curators.
- 10%
Rewards eligibility
Who may collect indexing rewards: an oracle checks each indexer's service and renews its eligibility.
-
Eligibility checks
Whether indexing rewards go only to indexers the oracle has found eligible.
- On
-
Eligibility lasts
How long an indexer stays eligible after the oracle last confirmed it.
- 14 days
-
Oracle timeout
If the oracle makes no update for this long, every indexer counts as eligible, so rewards don't stop with the oracle.
- 7 days
Recent changes
Values that changed since BitBasic began reading them on Nov 7, 2026, by a governance vote or an upgrade. Each is dated when it was first read, and counted once a second reading agrees.
No value has changed since Nov 7, 2026.