Documentation
Architecture walkthrough
- How BlobArchive works — A guided tour from Ethereum data to a content-addressed archive, signed publication, replicas, and local beacon endpoints.
- How BlobArchive uses IPFS — A plain-language guide to the content addressing, DNSLink/IPNS discovery, DHT rendezvous, libp2p connections, Bitswap transfer, relays, and hole punching used by BlobArchive.
- Heads, shared blobs, and retention — How BlobArchive indexes many logical archives over one content-addressed block store and turns retention policy into pins.
- Discovery and trust — What DNSLink, IPNS, signed publications, profile pins, and durable replay floors each prove—and what they do not.
- Finalized heads and live views — How one bounded unfinalized physical head safely serves chain-specific local live views without becoming a new publication authority.
Operator guides
- Run an embedded follower — Select a production follow profile, preserve durable state, verify readiness, and expose only a local beacon endpoint.
- Attach BlobArchive to Kubo — As a follower/replica operator, use a local Kubo 0.42 node as the sole archive store and optional read-only beacon gateway.
- BlobArchive for L2s — Use a local BlobArchive node as the primary beacon blob API for an L2, from a home node to an RPC fleet or chain-operated service.
- Monitor a BlobArchive node — Role-specific metrics and starting alert conditions for embedded followers, Kubo replicas, and writer deployments.
- Operate and troubleshoot a node — A follower/replica operator's checklist for local consumers, monitoring, storage, discovery, NAT, relay, and fail-closed recovery.
- Independent writer FAQ — Operational detail for anyone considering running an independent BlobArchive writer—independence requirements, signer custody, the measured resource envelope, bootstrap options, compatibility proof, monitoring, and the staged path to authorization.