Verifiable Execution
How does Catalyst support offline verification of an execution record by a third-party auditor?
Catalyst’s verifiable records are self-contained; an auditor can verify signatures and hash chains using only the public key and the record data, without connecting to the runtime. The record includes all necessary step payloads and signatures. However, offline verification still assumes the public key is authentic and that the record hasn’t been truncated; a complete chain from genesis is required for full confidence.
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
How does Catalyst ensure that step records are tamper-evident?
Catalyst uses a hash chain and digital signatures per step, so any alteration breaks the chain and becomes detectable through signature verification.
- 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.