The original post was written to the shape of GIP-0089 and kept short on purpose, which means it undersold what this covers. so here is the fuller list, grouped by who gets what. every line is a public repo under Night's Watch · GitHub or a live url, and the pledge is the same for all of it: it stays maintained, free and open for the twelve months, and the quarterly report says which of these moved and which did not.
for indexers
graph-support: 43 issues in six weeks, root cause found on 36, and the fixes that belonged upstream went upstream as pull requests. the 16 september network subgraph outage was diagnosed there while it was still happening.
gib, gateway in a box: a self-hostable tap v2 gateway for arbitrum one in one compose file that runs on a 2 GB vps, with a smoke test that proves the payment path without asking anyone’s permission. a second gateway operator is the one catalyst item nobody can do alone, so this is the workstream we keep pushing hardest.
a free public network subgraph endpoint at network.thenightswatch.dev/graphql for indexer-agent and indexer-service. no key, no quota.
horizon-doctor, reo-doctor, sik, indexer-gateway-auth, tap-query, weaver for dips agreements, foghorn: small read-only tools that catch the traps before they cost an allocation. the runbook for becoming a data service provider documents the ones we hit ourselves, including the thawing cap that refuses 30 days with an unnamed error.
while doing that we found every uups data service in this stack, ours and others’, had an empty _authorizeUpgrade that lets an upgrade silently repoint the collector. fixed where it could be tested, written up so the rest can copy it.
for subgraph developers
redstart: a typed language that compiles to assemblyscript graph build accepts unmodified, store-diffed against a hand-written subgraph with zero differences. nullable arithmetic and a forgotten save() stop being runtime surprises. graphite does the same job for people who want rust.
the graph academy at learn-thegraph.com, rebuilt at the end of august. every protocol parameter carries the date it was last checked against chain, and the symptom index at /diagnose is fed by every closed graph-support issue. it found three places where the official docs contradict each other and says so.
nuthatch for the chains studio cannot take yet. a uniswap v4 subgraph for robinhood chain would not deploy to studio last week and indexed on a free endpoint in minutes. hackathon teams get a hosted nest the same day.
for delegators and curators
lodestar, which since 7 september reads no graph subgraph at all and serves everything from self-hosted nests and one rust process. when we found the p&l panel misstated 54 of 58 indexers we published the correction rather than quietly fixing it.
the lodestar oracle, grc-009: an independent qos oracle that pays indexers directly for probes and publishes on chain, because the official one served july data as current for a month while reporting itself healthy.
subsidised hosted nests for hackathon participants - We will host your hackathon nest. Free, the same day. - Nuthatch
for the protocol
the catalyst tracker scores all eight roadmap items against public repos and says plainly which parts only the foundation can move.
seven grcs this year. dispatch, seahorn, sdsce, mainline and the nuthatch data service are deployed on arbitrum one as reference implementations any provider can run. we stopped operating them ourselves in july and said why.
upstream, six merged pull requests into graph-node, networks-registry and the reo dashboard this year, five more open, and the graph-node and indexer-rs bugs filed from support cases in the last fortnight.
what i am not claiming
that any of this is finished, that it has many users yet, or that 315,000 GRT a year changes what gets built. it covers some hosting and data bills and makes the network a participant in its own community tooling instead of a bystander. the work continues either way. I still will be at a net loss, but I am doing it for the network.
The part I would most like pushback on is the source of the 0.12073 GRT per block. Taking it from the rewards manager follows every precedent. Taking it from the innovation allocation costs indexers nothing. which would the council rather see?