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.

Protocol Primitives

Four core primitives.

EORElydora Operation Record

Signed operation envelope submitted by an agent. Contains agent_id, operation_type, subject, action, payload_hash, nonce, issued_at, prev_chain_hash, and an Ed25519 signature.

ECHElydora Chain Hash

Per-agent chain linkage hash. SHA-256 over prev_chain_hash, payload_hash, operation_id, and issued_at, linking each operation to its predecessor.

EARElydora Acknowledgment 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 Record

Epoch record anchoring a batch of operations under a single SHA-256 Merkle root. Optionally anchored through an RFC 3161 timestamping authority.

Architecture

Data flow.

Agent SDK
↓
Workers API
↓
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 TreesSHA-256

Epoch roots and inclusion proofs

TSPRFC 3161

Trusted timestamping for epoch root anchoring

Build on the protocol.

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