Blog
Field notes
Real deployments and the scar tissue from them - what it's actually like to run your own indexer in production.
-
Upgrading a live indexer, three versions in one go
The nuthatch behind Lodestar's dashboard had been on 0.3.0 since it shipped. We bumped it to 0.6.0 while it was serving real traffic - three minor versions in one swap. This is the operator's log, and the good news is that it was an anticlimax.
-
The Graph put Nuthatch in their hackathon bounty
ETHGlobal Lisbon's $7,000 Best AI Tooling track names Nuthatch as an accepted data backend, alongside Subgraph Studio. What it means, and a field guide for anyone building on the bird this weekend.
-
No eth_calls in nuthatch: what you derive instead
Over 70% of subgraphs call eth_call to read contract state. nuthatch's data path makes none, on purpose, and gives you recipes that derive the same values from indexed events, byte-for-byte and free.
-
Index Uniswap V3 yourself: for free, in under an hour, without writing code
Self-host a full Uniswap V3 index, every pool, every swap, prices and volume, with one Rust binary, one config file, and SQL. No graph-node, no gateway, no query fees.
-
We put a live dashboard on our own indexer. Here's the box.
Nuthatch stopped being a demo today. A real public dashboard - Lodestar - now serves two of its panels from a single nuthatch binary running on one small VPS of ours. This is the operator's log: the nests, the backfill, the box, the 86 MB, and the runtime deadlock we had to root-cause to get there.