ZeqText

HITE encryption, TESC channels, ZeqProof, firewall primitives.

• Protocol ID — zeq-text
• Category — Security
• Endpoint — POST /api/tesc/send
• Auth — api-key
• Rate limit — 60/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

TESC-encrypted messaging protocol. End-to-end AES-256-GCM with Phase-Locked Authentication Tags (PLATs) that expire every 0.777s. TESC UID serves as your phone number. WebSocket real-time delivery, typing indicators, read receipts, offline message queue, entanglement chain replay protection.

Signature

Request

POST /api/tesc/send

Param	Type	Required	Default	Description
message	string	✓	—	Plaintext message to encrypt and send via TESC channel
channelId	string		—	TESC channel ID (auto-generated if omitted)
recipientUid	string		—	TESC UID of recipient

Response

{ protocol, channelId, encrypted, iv, plat, zeqond, phase, R_t, entanglementChain, expiresAt, ttlMs }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "message": "<value>",
  "channelId": "<value>",
  "recipientUid": "<value>"
}' \
  "https://api.zeq.dev/api/tesc/send"

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