How Event Ledger works.
An append-only, signed record of the business events you may need to prove later. This page covers the mechanism: what happens to a request, what is signed, and how someone outside your company checks it.
- Post the eventFrom your backend, at the moment the action happens
- Canonicalize and hashThe payload is normalized to canonical JSON and hashed with SHA-256
- Sign and appendA worker signs the canonical bytes with your Ed25519 key and inserts the row
- Verify any timeSubmit the payload or its hash
Post the event
From your backend, at the moment the action happens.
Canonicalize and hash
The payload is normalized to canonical JSON and hashed with SHA-256.
Sign and append
A worker signs the canonical bytes with your Ed25519 key and inserts the row. Deletes are blocked at the database.
Verify any time
Submit the payload or its hash. The response says whether it matches what was anchored.
| Hash | SHA-256 over canonical JSON |
|---|---|
| Signature | Ed25519, per-organization key |
| Delivery | At-least-once queue, idempotent inserts |
| Deletes | BEFORE DELETE and TRUNCATE triggers raise an error |
| Limits | event_type 128 chars, payload 64 KB |
| Verify | POST /v1/events/{id}/verify |
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.