glamsterdam-devnet-7

a thin, self-verifying block explorer — no origin, no database

This page is a Cloudflare Worker bound to an R2 bucket. It stores no chain data. Every request is served by a byte-range read of a content-addressed artifact directly from object storage, and every response re-derives its own consensus commitment (keccak of the block header, of the tx envelope, of the EIP-7928 block access list) before it is returned. The explorer is a view over the bucket, not a service.

chain
glamsterdam-devnet-7 (id 7082904758)
blocks
10336 · [7264 … 17599]
bundles
323
txs indexed
1076220
format
cryo-glam-raw1-bal

Routes

Live: connecting to the head plane…

Don't trust this site — verify it yourself

Download the verification kit (sha256, ~400 KB). It contains the reference reader (wasm), the capsule verifier, the BLS finality verifier (prebuilt + source), and the two pinned trust roots. tar xzf kit.tar.gz && bash kit/verify_all.sh fetches a fresh capsule + finality proof and verifies both with no trust in this site — proven to run in a network-isolated container. 25 checks: keccak, blake3 integrity tree, ed25519 signatures, transparency-log chain, and real BLS sync-committee verification.

Signed manifests + transparency log

Every bundle manifest is ed25519-signed and recorded in an append-only, hash-chained transparency log (both on the bucket, under sign/). This Worker verifies the signed log head, the full chain, and each manifest's signature + log membership against a pubkey pinned in its code on every model load — a bucket compromise cannot silently substitute a different lattice. Per-block status: the X-Manifest-Signed header and the badge on block pages; fleet status in /stats.

The anchor, on every response

Data responses carry the 2-axis anchor (X-Anchor-Consensus × X-Anchor-Payload): everything served here is finalized × included — the compile window is bounded at the CL finality checkpoint, and each block came off the canonical EL chain. Block pages additionally show the slot's PTC verdict (timely / repudiated / no_quorum / unjudged, with vote counts against the absolute 256-of-512 quorum) — consensus metadata that never gates EL inclusion: a repudiated payload is still canonical history if the next builder built on it.

Every byte is verifiable. A /block/N response carries X-Block-Keccak; recompute keccak256(header) over the returned RAW1 header and it equals that value — the block hash the network agreed on. Nothing here is trusted; it is re-derived from the bucket on every read.