Nests · Graph Protocol
Lodestar sync bounties
bounty-nest · Arbitrum
Every sync bounty posted on Lodestar's BountyBoard 2.0.0 and what became of it: open, paid, cancelled or refunded. `open_bounties` is what an indexer's automation polls.
The copy we host
Read when this page was built, on 2026-11-11. If your browser can reach the nest, the status and block above are replaced with what it says now.
Query it
The stock binary behind a read-only proxy: GET only, no key, no admin. Stood up for
Lodestar.
https://nuthatch-indexer.com/nests/bounty-nest curl 'https://nuthatch-indexer.com/nests/bounty-nest/sql?q=SELECT%20*%20FROM%20open_bounties' Tables
One per contract event, as the nest listed them on 2026-11-11. Its schema describes the views as well.
| table | event |
|---|---|
| board__bounty_cancelled | BountyCancelled(uint256,uint256) |
| board__bounty_distributed | BountyDistributed(uint256,address,address,address,uint256,address) |
| board__bounty_posted | BountyPosted(uint256,address,bytes32,uint256,uint256) |
| board__bounty_refunded | BountyRefunded(uint256,uint256) |
What it indexes
Each event becomes a decoded SQL table.
BountyPosted, BountyDistributed, BountyCancelled, BountyRefunded
The BountyBoard is Lodestar's contract, not part of the protocol; it pays an indexer on the SubgraphService's own record of a presented POI. One real bounty had been through the views on 2026-11-11, open, and no paid, cancelled or refunded one. A copy is hosted at nuthatch-indexer.com/nests/bounty-nest.
Run it yourself
The nest is a git repository: ABIs, views and a manifest. One command scaffolds a local copy, and
nuthatch dev in it backfills and follows the chain against your own RPC.
nuthatch init --from https://github.com/nuthatch-org/bounty-nest Source: nuthatch-org/bounty-nest.
Published data
This nest’s data is not on the public mirror, so there is nothing of it to query from this page. Running it yourself is the way to its data.
Limits of the hosted copy
- No uptime promise. It is one process on one box, and a nest you run yourself answers to nobody else’s outage.
- Read-only. Anything that would write, or spend the operator’s RPC, is refused at the proxy.