HITE Encryption

HITE encryption, TESC channels, ZeqProof, firewall primitives.

• Protocol ID — hite-encrypt
• Category — Security
• Endpoint — POST /api/hite/encrypt
• Auth — api-key
• Rate limit — 30/min
• Version — 2.0
• Precision — ≤0.1% (KO42-enforced)

What it does

HULYAS Information-Theoretic Encryption — AES-256-GCM with PBKDF2-SHA256 key derived from HulyaPulse constants. Includes Landauer certificate.

Signature

Request

POST /api/hite/encrypt

Param	Type	Required	Default	Description
plaintext	string	✓	—	Data to encrypt (max 64KB).

Response

{ ciphertext, iv, tag, algorithm, keyDerivation, landauerCertificate }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "plaintext": "<value>"
}' \
  "https://api.zeq.dev/api/hite/encrypt"

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/hite/encrypt in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating HITE Encryption alongside a real workload, with pulse-aligned metrics.
• Far — propose HITE Encryption 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.