How it works · Traces
How Traces works.
Group events, documents and AI attestations into one sealed record of a whole process. This page covers the mechanism: what happens to a request, what is signed, and how someone outside your company checks it.
Traces filling and sealing, live
Live
The path of a request
- Open a traceCreate it with a label
- Attach recordsPass trace_id when you post events, documents or attestations
- SealInvoance orders the items by time and computes SHA-256 over their hashes, then signs the result
- Share the proofExport JSON or PDF, or make the proof page public
Step by step
Open a trace
Create it with a label. You get a trace_id.
Attach records
Pass trace_id when you post events, documents or attestations.
Seal
Invoance orders the items by time and computes SHA-256 over their hashes, then signs the result.
Share the proof
Export JSON or PDF, or make the proof page public.
Technical factsAPI reference
| Composite hash | SHA-256(h1 ‖ h2 ‖ … ‖ hN), chronological |
|---|---|
| Seal | Ed25519 signature over the canonical seal payload |
| After sealing | New items are rejected with 409 trace_sealed |
| Proof | GET /v1/traces/{id}/proof and /proof/pdf |
| Empty traces | Cannot be sealed |
How a third party verifies
Verification does not need an Invoance account or access to your systems. The verifier recomputes the hash from what they hold and compares it with the signed record.
- Opens the proof linkNo account, no dashboard access
- Recompute the hashSubmitted payload against anchored hash
- match_result: truePlus issuer domain and signing time
Try it against a real record.
Open the verifier, or create a record of your own on the free plan.