What is live on Base Sepolia.
The app separates product release metadata, confirmed Base Sepolia deployment-only readback, synthetic proof artifacts, and security boundaries.
The chain records references, not private truth.
Status shapes
A solid block means confirmed readback. A half block means unavailable, pending, or synthetic. An outline block means static metadata.
Synthetic data and Base Sepolia testnet only.
No receipt anchoring, challenge verdict, or slashing transaction is claimed.
Deterministic reference resolver for public alpha.
Deployment readback only
Deployment readbackBase Sepolia deployment
Registry: 0x4287f37Fe2Fa07eF5b0D0e19613453ec28B51e89
Escrow: 0x2b37Bf2098D88742f42c015A32f9D1A88084Dc3D
Deployment readback: passed.
Receipt anchoring, challenge verdict writes, and slashing are not confirmed on Base Sepolia for the public demo loop.
Protocol trace boundary
Canonical write trace is pending local role keys and is not exposed through the public browser bundle.
Confirmed protocol-event writes: 0.
Inspect exact Base Sepolia deployment facts
Trace status: Protocol trace pending role keys.
| Registry | 0x4287f37Fe2Fa07eF5b0D0e19613453ec28B51e89 |
|---|---|
| Escrow | 0x2b37Bf2098D88742f42c015A32f9D1A88084Dc3D |
| Setup tx | 0x21aeb97aef002b0ad5c63af95d298f80afdeae5231d22691ea03f016fd1e89ff |
| Source verification | not_confirmed |