Auditor Path

> Inspect, Reveal, Enforce

Look up anchored commitments, inspect sealed blobs, and only then decide whether the slash path is justified.

SAIL Contract

Lit Protocol

0G Storage

0G Compute

ENS

AXL Mesh

Same backend URL as the operator: Send uses same origin (Next.js → SAIL_API_PROXY_TARGET). The operator's Reveal inbox polls GET /api/axl/recv on that same host — if their Next proxy points elsewhere, their inbox is a different AXL queue than yours. Matching ENS to a peer id only proves DNS/state lines up; it does not route packets across two Railway vs localhost backends or through NAT.

Send a formal SEAL — Audit request to the operator’s AXL peer (from ENS text record axl_peer_id). The operator can Accept or Deny over the same channel (topic sail.seal.audit).

Target

Connect your wallet so the wire message includes your auditor address.

Decrypt & Verify commitment

Calls GET /api/audit/:hash with your wallet as the auditor. Backend decrypts via Lit Chipotle (enforcing SAIL.isAuthorized on-chain inside the TEE) and verifies keccak256(plaintext) === commitmentHash.

Connect wallet — your address is passed as the auditor.