How it works · Document Anchoring
How Document Anchoring works.
Proof that an exact file existed at a given time, without handing the file over. This page covers the mechanism: what happens to a request, what is signed, and how someone outside your company checks it.
Document anchors, live
Live
The path of a request
- Hash the fileThe SDK reads the file and computes SHA-256 locally
- Anchor the hashSend the hash, a reference and optional metadata
- Sign and storeThe anchor is signed with your Ed25519 key and appended to the ledger
- Re-hash to verifyAnyone with the file can hash it and compare against the anchor
Step by step
Hash the file
The SDK reads the file and computes SHA-256 locally.
Anchor the hash
Send the hash, a reference and optional metadata. Include the bytes only if you want them stored.
Sign and store
The anchor is signed with your Ed25519 key and appended to the ledger.
Re-hash to verify
Anyone with the file can hash it and compare against the anchor.
Technical factsAPI reference
| Hash | SHA-256, 64 hex characters |
|---|---|
| Signature | Ed25519, per-organization key |
| Original file | Optional, encrypted object storage |
| Verify | POST /v1/document/{id}/verify |
| Privacy | In hash-only mode Invoance never receives the content |
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.