For verifiers and integrators
Witnessed evidence, in formats you already verify
If your systems already consume verifiable credentials or attestations, Trooth's signed evidence maps onto the same shapes. You do not have to learn a new trust model to consume a Trooth signal. This page is the crosswalk.
Two objects, two roles
Trust Ledger Token
A portable, signed receipt a company can hand to a buyer or an agent. It behaves like a verifiable credential: a subject, an issuer, a set of claims, and a proof that re-verifies offline. Trooth co-signs it as a notary, witnessing the signing event rather than the claims.
Audit-chain block
An internal, hash-linked record of a witnessed read, signed by Trooth's attestation key. It behaves like an attestation: a statement that a specific observation was produced by Trooth OS at a specific time, replayable end to end.
The crosswalk
Verifiable-credential vocabulary on the left, the Trooth field that plays that role on the right.
| Verifiable credential | Trooth |
|---|---|
| Credential subject | The company the profile is about, by domain or Trooth slug. |
| Issuer | Trooth signs the witnessing event with its runtime attestation key. The customer signs the declared payload with a key held on their side. |
| Claims | The declared state at issuance: audit-root hash, tier, applicable frameworks, and classification. Trooth records these byte-for-byte; it does not warrant they are true. |
| Proof | Two Ed25519 signatures in the Trust Ledger Token (tlt2): the customer's over the payload, and Trooth's over the witnessing event. Both re-verify independently. |
| Issuance and expiry | The signed wall-clock timestamp and the token's expiry. An expired token needs re-issuing, which is not a failure of trust. |
| Revocation | A revocation record keyed by the token id. The public verify endpoint reports a revoked token as revoked. |
| Anchoring | A hash of the evidence is anchored to a public time-stamp authority, so the witnessing time is independently checkable. |
What the signature means
The mapping is honest about scope. A notary stamps the act of signing; a notary does not vouch for the truthfulness of the document. Trooth's outer signature attests that the customer's signature existed at the witnessed timestamp, and that the payload was recorded byte-for-byte at issuance. It does not attest that the declared state is true, and its signing input does not contain the claim bytes. A verifier assesses the underlying claims independently, exactly as it would for any credential whose issuer is a notary rather than an auditor.