How Invoance creates permanent, verifiable proof
Invoance anchors business records using the same cryptographic primitives that secure SSH keys, TLS connections, and digital currencies. Every record is hashed with SHA-256, signed with Ed25519, timestamped at ingestion, and written to append-only storage. The result is tamper-evident, independently verifiable, and permanent.
This page explains the technical mechanics behind every Invoance product. If you need to satisfy an auditor, regulator, or compliance review — this is what you share.
Cryptographic primitives
Every Invoance product uses the same five cryptographic primitives. These are structural guarantees — they hold regardless of which product you use, what plan you're on, or how you access the API.
Every payload — event, document, AI input, AI output — is hashed with SHA-256 before signing. Any alteration to the original data produces a completely different hash. This is the mathematical foundation of tamper detection.
Every hash is signed with an Ed25519 key bound to your organization. The signature proves the record originated from your tenant and has not been altered. Ed25519 is the same algorithm used by SSH, Signal, and TLS 1.3.
Records are written to an append-only Postgres database. This is enforced at the database level — not by application policy. No admin, no API, no override can delete or modify a record after ingestion.
The timestamp is recorded at the moment Invoance receives the data and is included in the signed payload. It cannot be backdated, adjusted, or overwritten after the fact.
Every record produces a public verification URL. Any third party — auditor, regulator, counterparty, court — can verify the record independently without an Invoance account or API key.
The anchoring flow
Regardless of which product you use, the anchoring flow follows the same four-stage process. The data model differs — the cryptographic mechanics are identical.
Send data to the Invoance API — an event payload, document hash, AI attestation bundle, or trace operation.
Invoance computes SHA-256 over the submitted data. For documents, you compute the hash locally — Invoance verifies it.
The hash is signed with your tenant's Ed25519 private key. The timestamp is included in the signed payload.
The signed record is written to the append-only ledger. A public verification URL is generated. The record is now immutable.
How each product works
Each product applies the same cryptographic foundation to a different data model. Select a product to see the complete technical walkthrough — API calls, response schemas, verification flow, and compliance mapping.
POST /v1/eventsSend any business event — payment, approval, delivery, config change — and receive a permanent, cryptographically signed record in return.
POST /v1/document/anchorHash any document locally, submit the hash. Invoance binds it to a timestamp and organizational identity — proving the document existed unchanged at that moment.
POST /v1/ai/attestationsAnchor AI inputs, outputs, and model metadata as tamper-evident records at the moment of generation — proving exactly what the model received and produced.
POST /v1/tracesGroup independently anchored events into a single sealed process proof. When complete, the trace is permanently closed with a composite cryptographic hash covering every event.
How verification works
Every Invoance record can be independently verified — by anyone, without authentication, without contacting Invoance. Verification resolves against cryptography, not a server assertion.
The verifier needs the original document, event payload, or AI output — whatever was anchored.
Apply SHA-256 to the original data. Any standard cryptographic library produces the same result.
If the recomputed hash matches the anchored hash, the data has not been altered since anchoring.
Using the organization's public key and the Ed25519 signature, verify the record was issued by the stated organization.
The timestamp is part of the signed payload. If the signature verifies, the timestamp is authentic — it cannot have been altered independently.
What Invoance proves and does not prove
See it in action
Pick a product and walk through the complete technical flow — from API call to cryptographic proof to public verification.
How Invoance Creates Permanent, Verifiable Proof
Invoance anchors business records using the same cryptographic primitives that secure SSH keys, TLS connections, and digital currencies. Every record is hashed with SHA-256, signed with Ed25519, timestamped at ingestion, and written to append-only storage. The result is tamper-evident, independently verifiable, and permanent.