Verifiable Execution
How does Catalyst ensure that step records are tamper-evident?
Catalyst ensures tamper-evidence by signing each step record with a private key and chaining hashes between steps. This creates a cryptographically linked chain where altering any step breaks the hash chain and invalidates subsequent signatures. External verifiers can detect tampering by recomputing hashes and checking signatures against a public key. The record’s integrity relies on key security; compromised keys undermine the proof.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Verifiable Execution
What is a verifiable execution record in Catalyst?
A signed, immutable sequence of agent steps enabling auditors to prove run integrity through independent replay. It does not validate decision correctness.
- Verifiable Execution
Can an auditor independently replay a Catalyst agent run to verify its outcome?
Auditors can replay runs using signed step records and initial state to verify output consistency, though non-determinism may limit exact reproduction.
- Verifiable Execution
Who can verify the integrity of a Catalyst agent execution?
Any party with the public key can verify the signed step chain, enabling independent auditability without trusting the execution system.