Verifiable Execution
What cryptographic algorithms does Catalyst use to create tamper-evident step signatures?
Catalyst signs step records using asymmetric cryptography; typical implementations rely on Ed25519 or ECDSA with SHA-256 hashing. Each step’s payload, metadata, and predecessor hash are hashed and signed, producing a detached signature that can be verified without the signing key. However, the strength of the evidence depends on the security of the key management and the chosen elliptic curve.
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.