Saltar al contenido principal

ZeqZK — Zero-Knowledge Proof

HITE encryption, TESC channels, ZeqProof, firewall primitives.

  • Protocol ID — zeq-zk
  • Category — Security
  • Endpoint — POST /api/security/zk/prove
  • Auth — api-key
  • Rate limit — 20/min
  • Version — 1.0
  • Precision — ≤0.1% (KO42-enforced)

What it does

Zero-knowledge proof using HULYAS field evaluation. Prove you know an equation that produces a specific R(t) value without revealing the equation. Based on the Zeq Auth principle: the equation is never transmitted.

Signature

Request

POST /api/security/zk/prove
ParamTypeRequiredDefaultDescription
commitmentstringSHA-256 hash of the equation + evaluation result (the ZID derivation).
challengenumberVerifier's challenge value. If omitted, server generates one.

Response

{ proof, commitment, challenge, verified, zeqond, protocol }

Runnable example

curl -sS -X POST \
-H "Authorization: Bearer $ZEQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"commitment": "<value>",
"challenge": 0
}' \
"https://api.zeq.dev/api/security/zk/prove"

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/zk/prove in a language SDK so builders can call it in three lines.
  • Medium — publish a reference integration demonstrating ZeqZK — Zero-Knowledge Proof alongside a real workload, with pulse-aligned metrics.
  • Far — propose ZeqZK — Zero-Knowledge Proof as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

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