Community owned

A library for The Graph.
Every fact dated.

Not a documentation clone and not a dashboard. 64 entries on why the protocol is shaped the way it is, each carrying the date somebody last read its sources.

Real output of this site's nightly check, not an illustration

64 entries
Across 8 collections, cross-referenced by subject rather than ordered into a course.
28 parameters
Every protocol number, with its source, a quote from it, and the date somebody read it.
5 contradictions
Places where two official pages disagree. Recorded and taught, rather than quietly resolved.

The collections

8 shelves. Start anywhere.

Read a collection through, or arrive at a single entry from a search and leave through a cross-reference. Nothing here tracks you, asks you to sign in, or tests you.

6 entries

Start here

What the protocol is for, who does the work, and where the money moves.
6 entries

Delegators

Put GRT behind an indexer and understand what you actually take home.
5 entries

Curators

Signal on the data worth indexing. A bet on future query demand.
11 entries

Indexers

Run the machines, provision stake, prove the work, get paid without trust.
12 entries

Developers

Author subgraphs, Substreams and Token API queries. Pick the right lane.
4 entries

App builders

An endpoint that stays up, a bill you understand, a query that returns.
9 entries

The ecosystem

The software the network actually runs on, and who maintains which part.
11 entries

Governance

GIPs, the Council, arbitration, and where the issuance actually goes.

How it works

Every number has a receipt and an expiry date.

The previous Graph Academy taught Cobb-Douglas rebates, L1 bonding curves and the Hosted Service until it was retired. All three were true once. Nothing in the site could tell you they had stopped being true.

One registry

No entry hard-codes a number

Every protocol value lives in one file with its source URL, a verbatim quote from that source, and the date a human read it. Entries call the registry. Change a value once and every page that mentions it updates. An entry referencing a parameter that does not exist fails the build outright.

parameters.toml entry rendered with its date
Stamped

Checked against, and by when

Each entry shows what it was verified against, the date, and when it is due another look. Past that date the page says so in a banner at the top.

Loud

The build goes red

A nightly job lists pages past their date and parameters nobody has read in ninety days. Silence is the failure mode this site is built against.

Honest

Contradictions are published, not resolved

Reading the sources on 2026-08-30 turned up three places where official pages disagree with each other or with the shipped software. Picking a winner quietly would be more comfortable and less useful, so the site marks the parameter, teaches the conflict, and names the contract that would settle it.

Current

Checked against Graph Horizon (2025-12-11)

Including GIP-0089, which redirected a fifth of protocol issuance on 2026-08-31 and quietly made every reward rate measured before that date describe a larger pot.

The honest comparison

Three sites. This one is not the important one.

The Academy is useless on its own. It explains why the protocol is shaped as it is, and hands you to the documentation for how, and to a dashboard for what is true right now.

Property Official docs Academy Dashboards
Authoritative for procedures and configuration
Live network data
Maintained by the people shipping the code
Explains why the protocol is designed this way partly
Worked economic examples and exercises partly
Records where official sources contradict each other
Every page dated and due for re-verification n/a

Three of those seven rows go against this site, and the first three are the ones that matter most if you are about to do something. Read them as instructions: when you need a procedure, go to the docs; when you need a number that is true this minute, go to a dashboard.

Use it well

What it does, and what it doesn't.

A community learning site with a narrow job. The boundaries are deliberate, and knowing them saves you looking here for something that was never going to be here.

In scope

  • Why the protocol is designed the way it is
  • Mental models you can reason with afterwards
  • Worked economic examples with the arithmetic shown
  • Practicum entries: go and look at the real thing yourself
  • Decision guides: index or delegate, which data service, which indexer
  • A glossary that keeps the obsolete terms and labels them
  • Every protocol number, sourced, quoted and dated

Out of scope

  • CLI reference, flags and configuration keys
  • Live data of any kind, including indexer tables and rates
  • Installation and deployment instructions
  • Financial or investment advice, in any form
  • Accounts, sign-ins, progress tracking or anything that watches you read
  • Recommending specific indexers or subgraphs to put money behind
  • Chains, tools and services nobody here has actually checked

Nothing on this site is financial or investment advice. It has no analytics, no cookies, no accounts and no third-party requests. Nothing is stored about you anywhere, because nothing about you is collected in the first place.


Ask the library

A question, answered from these pages only.

It reads the entries, the dispatches and the parameter registry, and answers from those. It quotes numbers with the date somebody read the source, and it says so when the sources disagree. When it does not know, it says that instead of inventing something.

Funded by one person, so it is rate limited and has a daily budget. Nothing you type is stored. Not financial advice.


Start

Open it anywhere.

64 entries, 66 glossary terms, 28 sourced parameters. Free, community owned, CC-BY-4.0.