Drop in a claim id, name, URL, or a raw transaction id
(txid or txid:nout — render-by-ID, no
locator involved). Every step below is re-verified in this browser —
the HyperBEAM node is treated as an untrusted courier, and every
request it answers is on display under each step.
Each row is one verification step, with three layers of detail:
the one-line outcome is always visible, clicking a row tells the
story of what that step proves and what a lying node would look
like, and “proof” inside holds the raw values the verdict rests
on. “requests” lists every HTTP exchange the step caused, with
the commitment structure of each response parsed and classified —
no network tab required. The identity panel below the ladder
shows each evidence object's native LBRY id next to its HyperBEAM
commitment id, and can fetch the committed form straight from the
node's store, where the lbry-*@1.0 commitment device
appears in Signature-Input. The chips mean:
Every evidence object's native LBRY identifier, its HyperBEAM commitment id (with the conversion rule), and — once observed — its message id. “fetch committed form” reads the object back through the node's store path and parses the signature structure on screen.