Start from history, not from block zero

A backfill is the expensive part of running a nest: about a million RPC credits for the Lodestar allocations nest (the 4.9.0 release notes), every one of them buying history somebody has already indexed. The public mirror holds that history. nuthatch seed downloads it, checks every file against its content address, and leaves your nest following the chain from the block where the mirror ends.

1 · the nest

Clone the nest and check out the commit it was published from. The mirror is found by the nest's data identity, so any other version finds nothing.

2 · the history

Seed downloads the sealed segments, refuses any file that does not hash to its address, and resumes if interrupted.

3 · the tip

Dev follows the chain from the next block, over your own RPC. Seeding graph-gns-nest and catching up to the tip took six RPC calls (4.9.0 release notes).

  • graph-gns-nest

    published 2026-11-19
    chain
    Arbitrum One
    history
    42,008,725 to 525,601,538
    rows
    75,568
    files
    165 segments, 7 tables
    shell
    git clone https://github.com/nuthatch-org/graph-gns-nest
    git -C graph-gns-nest checkout 33d010ff69b5
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir graph-gns-nest
    nuthatch dev --dir graph-gns-nest
    nuthatch-org/graph-gns-nest ↗
  • graph-allocations-nest

    published 2026-11-19
    chain
    Arbitrum One
    history
    42,449,227 to 525,638,388
    rows
    6,432,175
    files
    7,489 segments, 75 tables
    shell
    git clone https://github.com/nuthatch-org/graph-allocations-nest
    git -C graph-allocations-nest checkout 7795a335a910
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir graph-allocations-nest
    nuthatch dev --dir graph-allocations-nest --state-rpc <archive RPC URL>
    nuthatch-org/graph-allocations-nest ↗

    This nest samples contract state, so dev needs an archive endpoint for eth_call.

  • dips-nest

    published 2026-11-19
    chain
    Arbitrum One
    history
    486,895,281 to 525,659,597
    rows
    156
    files
    56 segments, 22 tables
    shell
    git clone https://github.com/nuthatch-org/dips-nest
    git -C dips-nest checkout 0cf0ec2c7b1a
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir dips-nest
    nuthatch dev --dir dips-nest
    nuthatch-org/dips-nest ↗
  • data-services-nest

    published 2026-11-19
    chain
    Arbitrum One
    history
    456,917,519 to 525,659,597
    rows
    7
    files
    4 segments, 4 tables
    shell
    git clone https://github.com/nuthatch-org/data-services-nest
    git -C data-services-nest checkout 9696cb4beb1d
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir data-services-nest
    nuthatch dev --dir data-services-nest
    nuthatch-org/data-services-nest ↗
  • defi-pulse-nest

    published 2026-11-19
    chain
    Ethereum
    history
    24,136,053 to 26,449,080
    rows
    1,810,824
    files
    2,057 segments, 10 tables
    shell
    git clone https://github.com/nuthatch-org/defi-pulse-nest
    git -C defi-pulse-nest checkout f066c02d21c2
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir defi-pulse-nest
    nuthatch dev --dir defi-pulse-nest
    nuthatch-org/defi-pulse-nest ↗
  • betswirl-bnb-nest

    published 2026-10-07
    chain
    BNB Chain
    history
    16,689,819 to 126,307,900
    rows
    403,093
    files
    346 segments, 89 tables
    shell
    git clone https://github.com/nuthatch-org/betswirl-bnb-nest
    git -C betswirl-bnb-nest checkout 92d6588a3ad3
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir betswirl-bnb-nest
    nuthatch dev --dir betswirl-bnb-nest --state-rpc <BNB archive RPC URL>
    nuthatch-org/betswirl-bnb-nest ↗

    Retired 2026-10-07 (no users); the hosted endpoint is off. Still seedable: run it with the nuthatch-graph download from 4.12.0 or later, which serves its GraphQL.

  • qos-reo-nest

    published 2026-11-19
    chain
    Gnosis
    history
    46,700,000 to 49,362,117
    rows
    162,071,161
    files
    15,898 segments, 5 tables
    shell
    git clone https://github.com/nuthatch-org/qos-reo-nest
    git -C qos-reo-nest checkout cd83cef4ec5b
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir qos-reo-nest
    nuthatch dev --dir qos-reo-nest
    nuthatch-org/qos-reo-nest ↗
  • grt-supply-arbitrum-one

    published 2026-11-19
    chain
    Arbitrum One
    history
    42,449,227 to 525,632,589
    rows
    7,000,919
    files
    3,069 segments, 3 tables
    shell
    git clone https://github.com/nuthatch-org/grt-supply-nest
    git -C grt-supply-nest checkout ce2292e48337
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir grt-supply-nest/arbitrum-one
    nuthatch dev --dir grt-supply-nest/arbitrum-one
    nuthatch-org/grt-supply-nest ↗
  • grt-supply-mainnet

    published 2026-11-19
    chain
    Ethereum
    history
    11,446,769 to 26,450,099
    rows
    2,975,936
    files
    2,314 segments, 1 tables
    shell
    git clone https://github.com/nuthatch-org/grt-supply-nest
    git -C grt-supply-nest checkout ce2292e48337
    nuthatch seed --from https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev --dir grt-supply-nest/mainnet
    nuthatch dev --dir grt-supply-nest/mainnet
    nuthatch-org/grt-supply-nest ↗

What the hashes prove

That every file is the one the mirror's catalogue names, so nothing changed on the way or at rest. They do not prove who wrote that catalogue, or that it is true to the chain. Seed from a mirror run by someone you would trust to run the nest for you, or re-index a sample of it yourself and compare.

Publish your own

Any nest can be a mirror. Run it with --publish-target s3://your-bucket/prefix, or run nuthatch publish sync on a stopped one, and point people at the bucket's public address. The mirror is append-only and costs nothing to read from a bucket that does not charge for downloads. The operator guide has the bucket policy.

Read it without Nuthatch

The mirror is plain Parquet, so DuckDB, Trino or anything else that reads Parquet over HTTPS can query it directly. A public bucket cannot be listed: each dataset's manifest.json names its tables and, for every segment, a hash, and the file is at <dataset>/<table>/<hash>.parquet. The manifest's file field is the name inside a nest directory, not the address here.

duckdb
SELECT count(*), min(block_number), max(block_number)
FROM read_parquet('https://pub-bc282d5016f242a783a6c28cbcd4401a.r2.dev/494ce630fa704ee504e6cdfb8f732c66d585843face32fbbc6b7bf115a9b15c7/gns__subgraph_published/e03958df317ac9e39634669f04c7fc1c6e6caed29e7b5f37630235acd8c9f7f2.parquet');