ELYDORA
Elydora Responsibility Protocol

One protocol.
Every agent.

The Elydora Responsibility Protocol (ERP) defines the open standard for binding AI Agent actions to verifiable, tamper-evident, legally defensible responsibility records. ERP is to agent accountability what OAuth is to web identity.

Protocol Primitives

Four core primitives.

EORElydora Operation Record

Signed operation envelope submitted by an Agent. Contains agent_id, operation_type, payload_hash, nonce, timestamp, Ed25519 signature, and prev_chain_hash for sequential chaining.

ECHElydora Chain Hash

Cryptographic chain linkage hash per Agent. SHA-256 hash of the canonicalized operation record that links each operation to its predecessor, creating an immutable per-agent chain.

EARElydora Attestation Receipt

Platform-signed admission receipt returned for every accepted operation. Contains receipt_id, operation_id, chain_hash, seq_no, and the Elydora platform signature.

EERElydora Epoch Root

Merkle root anchoring a batch of operations into a single verifiable hash. Follows RFC 9162 transparency-style trees. Optionally anchored via RFC 3161 TSA.

Architecture

Data flow.

Agent SDK
Workers API (Edge)
Durable Object (per-agent)
Queues
Queue Consumer
D1 + R2
Cryptographic Stack

Built on open standards.

Ed25519 / EdDSARFC 8032

Digital signatures for operation records

SHA-256FIPS 180-4

Hash function for chain linking and content integrity

JCSRFC 8785

JSON Canonicalization for deterministic serialization

Merkle TreesRFC 9162

Certificate Transparency v2 style audit proofs

TSPRFC 3161

Trusted timestamping for epoch root anchoring

Key ManagementNIST SP 800-57

Key lifecycle and rotation guidance

Build on the protocol.

Integrate the Elydora Responsibility Protocol into your agent infrastructure. Read the developer documentation or get in touch.