Developers

Integrate from Depth of Trust (DoT) outward: understand profiles and Sigils, obtain demo receipts through Proof Lab, verify offline, then optionally call the read-only public verifier. This hub is non-normative — the Protocol page and published schemas remain authoritative.

Step 1

Map DoT profiles and Sigils

Start with the DoT ladder (0–6) and domain profiles. Know what offline validity (DoT-4 / Sigil S4) means before you integrate.

Step 2

Obtain receipt bytes via Proof Lab

Proof Lab is the only public signing lane — demo keys, DoT-0/1/4 → S4. For production issuance, contact operators through /contact.

Step 3

Verify offline first

Check signature, canonicalization, declared profiles, and Sigil from receipt bytes alone — no network required for base validity.

Step 4

Optional hosted verifier

POST bounded receipts to read-only /v1/verify when you need a hosted check. The API does not mint, anchor, or disclose — fail closed on ambiguous trust inputs.

Go deeper

DoT ladder, Sigils, verify path, and honest limits.

Each page stays non-normative. Protocol and published schemas remain authoritative.

Depth of Trust Receipt basics Sigils S0–S6 Verify (offline + API) Staged features Limits and boundaries Proof Lab demo Operator contact Protocol reference