Resource Name Service over ZAP — service naming bound to KEM keypair.
zap-proto.io · Spec · Paper · Discord
zap-rns layers service discovery semantics over the ZAP transport. Post-quantum confidentiality, mutual authentication, and zero-copy parse come from the wire; this repo only adds the service discovery message shape.
v0.1 — schema-first. This repo currently ships:
schema/zap_rns.zap— wire format spec in ZAP schema language
Reference implementations (Go, Rust, TS) land in v0.2 once zap-proto/spec provides cross-language codegen for the schema.
| Property | DNS / mDNS / SPIFFE | zap-rns |
|---|---|---|
| Confidentiality | TLS (classical) | X-Wing hybrid PQ (default) |
| Authentication | bearer / TLS cert | KEM keypair at transport |
| Wire encoding | text or per-protocol binary | ZAP wire, zero-copy |
| Identity binding | DNS / cert chain | zap-rns keypair |
| Future-quantum | classical only | hybrid by construction |
By the composability theorem, zap-rns inherits ZAP-base's PQ confidentiality and mutual auth automatically — no rns-specific PQ analysis required.
zap-http— HTTP request/response over ZAPzap-ws— multi-stream pubsubzap-fix— FIX 4.4 / 5.0 trading channelzap-rns— KEM-bound service namingzap-mcp— Model Context Protocol over ZAPzap-acp— Agent Communication Protocolzap-a2a— Google Agent2Agent over ZAP
MIT OR Apache-2.0