Skip to content

docs: add blob archive endpoint page - #256

Open
a-thomas-22 wants to merge 1 commit into
mainfrom
docs/blob-archive-endpoint
Open

a-thomas-22 wants to merge 1 commit into
mainfrom
docs/blob-archive-endpoint

Conversation

@a-thomas-22

Copy link
Copy Markdown
Collaborator

Adds a /blob-archive page documenting the newly-public blob archive at https://blobs.blobflow.com, linked from the primary nav and the sitemap.

What the page says

It leads with the point most likely to cost people real time: this is not a beacon blob_sidecars API. The beacon-style path prefix makes it look like one, but there is no blob_sidecars route and the payload carries no KZG commitments, no proofs, and no signed block header. Prysm/Lighthouse/Teku cannot sync or backfill from it. L2 batch reconstruction works because clients like Arbitrum Nitro verify blob data against the versioned hashes already in the L1 transaction, so raw blobs are sufficient there.

The rest is framed around the supported workflow: use the archive to backfill historical blobs, then repoint the node at a live consensus endpoint once synced. Only the root base URL is documented, no profile prefixes.

Covers the Nitro quickstart flag, the three supported paths, response shape, status codes, coverage (mainnet, Deneb slot 8626176 onward, minutes of lag), limits and etiquette, and three copy-pasteable curl examples.

Verification

Every documented behavior was probed against the live endpoint, and all three curl examples run as written. A few things differ from what I was originally told, so the page documents the actual behavior:

Claim Live behavior
head / finalized / 0x-root slots return 400 Return 404 with an empty body
Slots not yet archived return 404 Return 503 with Retry-After: 12
(not mentioned) Slots with no blobs return 200 {"data":[]}
(not mentioned) Pre-Deneb slots return 404 with a JSON error body

Confirmed as stated: 128 KiB per blob (~1 MB per blob on the wire), max-age=900 on root blobs, max-age=86400 on genesis and config/spec, Deneb origin slot 8626176.

The ~512 Mbps cap and 429 behavior are documented as described but not tested, since triggering it would mean deliberately hammering the service.

npm run lint, npm run typecheck, npm test (453 passing) and npm run build all clean. The page prerenders as a static route.

Once merged, the site auto-deploys via ArgoCD after the image tag is bumped.

🤖 Generated with Claude Code

Documents the newly-public blob archive at https://blobs.blobflow.com as a
new /blob-archive page, linked from the primary nav and the sitemap.

The page leads with the point most likely to cost people time: this is not a
beacon blob_sidecars API. The path prefix looks like one, but there is no
blob_sidecars route and the payload carries no KZG commitments, proofs, or
signed block header, so a consensus client cannot sync from it. L2 batch
reconstruction works because clients like Arbitrum Nitro verify blob data
against the versioned hashes already in the L1 transaction.

Framed around the supported workflow: use the archive to backfill historical
blobs, then repoint the node at a live consensus endpoint once synced. Only
the root base URL is documented.

Every documented behavior and all three curl examples were verified against
the live endpoint.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blob-flow Ready Ready Preview Aug 5, 2026 7:33am

Request Review

This branch was successfully deployed

1 active deployment
Preview 22a36ae1 Deployed Aug 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant