الانتقال إلى المحتوى الرئيسي

Transport & Messaging

Every hop witnesses the Zeqond. Replay, reordering, and loss are all observable, not guessed.

  • Theme — transport-messaging
  • Protocol count — 29 (mail-seal, mail-deliver, msg-frame, msg-reassemble, mesh-gossip, mesh-route, relay, queue, stream, ws-upgrade variants)
  • Anchor operators — KO42 · CS47 · CS43
  • Verification — bit-exact message round-trip, per-hop phase attestation

What it solves​

Messaging needs four guarantees at once: confidentiality (inherited from the Encryption theme), integrity, ordering, and delivery-witness. Classical stacks give you the first three; Zeq adds the fourth by binding every hop to a Zeqond. That makes "did the recipient actually receive this" a question answerable by walking the attestation log rather than trusting the relay.

The theme groups four sub-families:

  • Mail — store-and-forward envelopes with sender + relay + recipient Zeqonds. Powers Zeq Mail.
  • Message — real-time double-ratchet frames with per-frame phase_at_send. Powers Zeq Message.
  • Mesh — peer-to-peer gossip over the Zeq mesh; each forward is a signed Zeqond record.
  • Stream — long-lived TESC-wrapped transports for media, telemetry, and continuous logs.

CS43 bounds framer complexity (sort / reorder / reassemble are all O(n log n)), CS47 is the entropy policer rejecting malformed or injected frames.

Operator map​

OperatorFormulaRole
KO42.1ds² = g_μν dx^μ dx^ν + α sin(2π · 1.287 t) dt²Mandatory — per-hop phase
CS47E(n) = −∑ p(x) log p(x)Entropy policing + flow-control
CS43T(n) = O(n log n)Frame ordering / reassembly bound

Runnable worked example — mesh gossip​

curl -s -X POST https://api.zeq.dev/api/playground/compute \
  -H "Authorization: Bearer $ZEQ_DEMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operators": ["KO42", "CS47"],
    "inputs": {
      "protocol": "mesh-gossip",
      "topic": "pulse/1287",
      "message": "hello mesh"
    }
  }'

Expected:

{
  "gossip_id": "gsp_01H...",
  "topic": "pulse/1287",
  "fanout": 8,
  "phase_at_emit": 0.5511,
  "zeqond": 1745125000.302
}

Each receiving peer adds its own signed (peer_id, phase_at_forward, zeqond) to the record; the sender can walk the attestation log to confirm delivery.

Extend it​

  • QUIC + TESC — wrap TESC frames in QUIC datagrams for low-latency media streaming with preserved Zeqond provenance.
  • Federated mail gateways — two organisations running Zeq Mail federate by exchanging tether roots; mail between them is end-to-end bound without a third-party relay.
  • Mesh recovery — if a sibling is lost, the remaining mesh can re-tether via a signed quorum gossip.

Seeds​

  • Anonymous broadcast — drop sender identity, keep only the Zeqond stream. Useful for privacy-preserving telemetry.
  • Planet-scale paging — a global low-bandwidth pulse channel that every peer can hear.
  • Interplanetary messaging — ZTB1 already bridges Unix↔Zeq; extend to Barycentric Dynamical Time for deep-space store-and-forward.

Papers​

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