Collection

The ecosystem

Every layer of this protocol is somebody's repository. This collection maps them: what each piece does, which lane it belongs to, and who is on the hook when it breaks.

9 entries 97 min to read through intermediate
01

The core stack

  1. The core stack Five repositories carry the protocol: the indexing engine, the indexer components, the contracts, the developer tooling and the client library. Everything else sits on top of them. 12 min
  2. Where the code lives Four organisations hold nearly everything, and which one a repository sits in tells you who is on the hook when it breaks. 8 min
02

Indexing

  1. Indexing it yourself A second lane has grown up beside graph-node: single-binary indexers you run yourself, with no gateway, no network and no third party in the path. 11 min
03

Serving

  1. Gateways, and why there is more than one Every query reaches an indexer through a gateway, which picks who serves you and handles the payment. A protocol with one gateway has a single point of control it was designed to avoid. 11 min
04

Authoring

  1. Authoring tools beyond AssemblyScript Subgraphs have been written in AssemblyScript since the beginning. Three projects argue that the language, and in one case the file format, was never the interesting part. 10 min
05

Data services

  1. Data services being built on Horizon Horizon made the protocol a substrate for services other than subgraph serving. Here is what people are actually building on it, and the shared machinery underneath. 13 min
06

Operating

  1. Tools for running an indexer The gap between the official stack and a well-run indexer is filled by community tooling: preflight checks, POI comparison, API guards and payment agreements. 12 min
  2. The oracles the protocol runs on Several things the protocol treats as facts are produced by oracles rather than derived on chain. Knowing which is which tells you where the trust actually sits. 10 min
07

Practicum

  1. Reading the ecosystem yourself Nothing here is a test. Go and look at the repositories, and form your own view of what is maintained and what is somebody's weekend. 10 min

Elsewhere

This collection explains why. Two other places carry the rest.

The procedure The Graph on GitHub Exact steps, flags and configuration, maintained by the people who ship the code. This site does not duplicate them and never will.