ZeqAudit — Computation Audit Trail

HITE encryption, TESC channels, ZeqProof, firewall primitives.

• Protocol ID — zeq-audit
• Category — Security
• Endpoint — GET /api/security/audit/chain
• Auth — api-key
• Rate limit — 30/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Immutable computation audit trail. Every ZeqProof is chained — each proof references the previous one, creating an unforgeable computation history.

Signature

Request

GET /api/security/audit/chain

Param	Type	Required	Default	Description
zid	string		—	Filter by ZID.
from	number		—	Start zeqond.
to	number		—	End zeqond.

Response

{ chain: [{ zeqProof, operatorIds, R_t, zeqond, previousProof }], length, integrity }

Runnable example

curl -sS \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  "https://api.zeq.dev/api/security/audit/chain"

Integrate

1. E2E channel — pair with HITE/TESC for encryption that locks to the HulyaPulse.
2. Integrity stamp — hash-bind every message to its Zeqond for replay-resistant audit.
3. Key rotation — tie rotation windows to pulse multiples for deterministic policy.

Seeds

• Near — wrap /api/security/audit/chain in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqAudit — Computation Audit Trail alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqAudit — Computation Audit Trail as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.