How Traces creates sealed, verifiable process proof
Traces groups independently anchored events into a single sealed process record. When you seal a trace, Invoance computes a composite SHA-256 hash over every event hash, signs it with Ed25519, and permanently closes the trace. The result is a single proof covering an entire multi-step process.
Trace lifecycle
A trace moves through three distinct states, each with specific guarantees about the events it contains.
Accepting new events, mutable
Composite hash computed, Ed25519 signed, permanently closed
Any party has independently confirmed the proof
Step 1: Create a trace
Start by creating a trace. Provide a name and optional reference and metadata fields.
{
"name": "Loan Application #4021",
"reference": "loan_app_4021",
"metadata": {
"applicant": "jane_doe",
"loan_type": "commercial",
"amount": 500000
}
}{
"id": "trc_a1b2c3d4",
"name": "Loan Application #4021",
"status": "open",
"created_at": "2025-03-15T10:00:00Z"
}Step 2: Anchor events to the trace
Events are submitted via POST /v1/events with a trace_id field. Each event is independently hashed and signed (same as standalone events). Events can be added over hours, days, or weeks.
Step 3: Seal the trace
When you're ready to close the trace permanently, seal it. This triggers a deterministic cryptographic operation that binds all events together.
All event hashes are gathered in chronological order.
SHA-256(event_hash_1 + event_hash_2 + ... + event_hash_n) is computed over the concatenated event hashes.
Composite hash is signed with your tenant's Ed25519 private key.
Trace status is permanently changed to 'sealed'. No more events can be added.
The exact moment of sealing is recorded for audit purposes.
{
"id": "trc_a1b2c3d4",
"status": "sealed",
"event_count": 5,
"composite_hash": "9f8e7d6c5b4a...",
"signature": "a1b2c3d4e5f6...",
"sealed_at": "2025-03-20T16:45:00Z",
"verification_url": "https://www.invoance.com/proof/trace/trc_a1b2c3d4"
}Proof bundle export
Once sealed, you can export the trace as a self-contained proof bundle. Two formats are available: JSON for machines and systems, PDF for auditors, regulators, and legal review.
Machine-readable proof artifact. Contains trace metadata, all events with their hashes and signatures, composite hash, seal signature, and public keys. Ideal for programmatic verification and system integration.
Human-readable proof document. Includes a formatted summary, event timeline, all cryptographic values in readable form, and step-by-step verification instructions. Perfect for regulatory submission.
The proof bundle is self-contained. Anyone can verify it without an Invoance account.
How verification works
Trace verification confirms that the sealed record contains exactly the events it claims, in the order recorded, with no modifications after sealing.
The critical guarantee: The sealed trace proves the complete sequence of events. Removing or inserting an event would change the composite hash, making the proof invalid. This is the strongest form of process integrity proof.
Compliance mapping
Traces provide the strongest proof model in Invoance. When a regulator asks "prove this process happened exactly as described", this is what you hand them.
CC6.1, CC7.2, CC8.1Process integrity, change management, and technology infrastructure. Traces prove that authorized processes executed in documented sequence with no tampering.
§164.312(b), §164.312(c)Audit controls and integrity controls. Sealed traces create immutable audit logs of all events in a healthcare process with cryptographic proof of completeness.
A.12.4, A.14.2Logging and change management. Traces document process changes with timestamps and cryptographic proof, satisfying information security logging requirements.
SOX, Basel IIIProcess documentation and audit trail. Traces prove regulatory-required process execution and can be exported for regulator review without Invoance infrastructure dependency.
Traces use the same cryptographic primitives as all Invoance records — SHA-256, Ed25519, and append-only storage. The composite hash binding is deterministic and verifiable offline, independent of Invoance infrastructure.
How Traces Works — Invoance
Technical walkthrough of how Invoance Traces groups independently anchored events into sealed, cryptographically verified process proof bundles. Create a trace, add events, seal with a composite hash, and export verifiable proof bundles for auditors or regulators.