HITE Decryption

HITE encryption, TESC channels, ZeqProof, firewall primitives.

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

What it does

Decrypt HITE-encrypted data. GCM authentication tag verified — integrity guaranteed.

Signature

Request

POST /api/hite/decrypt

Param	Type	Required	Default	Description
ciphertext	string	✓	—	Encrypted data (hex).
iv	string	✓	—	Initialization vector (hex).
tag	string	✓	—	GCM auth tag (hex, 32 chars).

Response

{ plaintext, verified, algorithm }

Runnable example

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

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