An ordinary browser fetches a holon from the mesh — and checks the proof itself.
What this page does. It reads the peer pinned in
/dl/peers.json,
opens a direct WebRTC data channel to it, asks for the authority’s
signed root, and verifies that
signature against the pinned key. Then it fetches a holon and accepts it only under an
Urkel inclusion
proof chaining to that root. Four outcomes, kept apart on purpose:
PROVEN,
REFUSED (an answer that did not check out),
UNAVAILABLE (nobody answered — nothing proven, nothing disproven), and
MISSING (the peer answered and does not hold it).
peelr.lol serves this JavaScript, so this page is not magic: what it buys is that every claim above is
checked here, against a key you can read, and an answer that fails is refused rather than shown.
Want the same guarantee without trusting this server at all?
Download Peelr, which ships the verifier and the key with it.
Or see the weaker rung: the same holon
through the gateway,
where each authority gets its own origin and the proof is checked in your tab — by JavaScript that gateway
served you, which is exactly the part it cannot prove about itself.