mirror of
https://github.com/zap-proto/dev.git
synced 2026-10-30 15:05:18 +00:00
zeekay
4738ffea2f
Red-team review (this session) caught half the protocol pages were AI
slop — describing Go APIs that don't exist in repos that contain only
schemas, plus performance tables contradicted by the only real bench
harness in tree. This is the surgery:
post-quantum:
- Drop the Z-Wing brand from public docs (user feedback: confusing).
- Reframe PQ as ZAP's stack: IETF X-Wing KEM (transport) + hybrid
Ed25519+ML-DSA-65 (identity) + PQ-RNS (name service). One canonical
story; layers are independent.
- Per-language status matrix shows realistic state (X-Wing KAT shipped
in 4 SDKs, sigs in all, resolver in progress).
protocols/{a2a,acp,fix,ws}:
- Marked "Status — spec-only, January 2026". Schema exists; runtime
doesn't. Removed every Go code snippet that called a non-existent
function. Replaced with a roadmap section.
protocols/rns:
- Rewrote against the actual schema at zap-proto/rns/schema/zap_rns.zap
(Record / Query / Response / signed-by-registry).
- Added the PQ-RNS end-to-end flow diagram and the DID definition
(base32(SHA3-256(kemPk || sigPk))).
- Documents the cross-language KAT fixture published at
zap-proto/rns/testdata/pqrns_kat.json.
protocols/mcp:
- Rewrote against the actual bridge.go API: NewBridge(*zap.Node),
AddServer, GetTools, CallTool, CallToolByName. Bridges existing
stdio MCP servers (it's a bridge, not a from-scratch impl).
- Dropped the invented zmcp.NewServer / Connect / ListTools API.
protocols/http:
- Killed the 6× req/s / 19× p99 / 6.2× RSS table — contradicted by
bench-results.txt which shows ZAP-HTTP currently ~10% slower.
- Replaced with honest current numbers + the value-prop statement.
protocols/native:
- Killed the 18× / 38× / 6.7× / 9.2× gRPC table — the bench harness
has no gRPC comparator, the numbers were fabricated.
- Replaced with the actual concurrency=32 numbers from bench-results
+ an explanation that the win is semantic, not currently latency.
transports:
- Killed the @zap-proto/wasm and Cloudflare-Worker code snippets that
referenced a non-existent npm package.
- Replaced with the honest pattern: browser→TLS→Worker→ZAP-over-X-Wing
to origin. Points readers at the SDK status table.
app/page.tsx:
- Dropped Z-Wing from the home page cards.
41 lines
2.0 KiB
Plaintext
41 lines
2.0 KiB
Plaintext
---
|
|
title: FIX over ZAP
|
|
description: FIX 4.4 / 5.0 trading channel — schema published, runtime in progress.
|
|
---
|
|
|
|
# FIX over ZAP
|
|
|
|
> **Status — spec-only, January 2026.** The wire schema is published; the Go acceptor / initiator runtime hasn't shipped. The target use case is sub-µs trading where FIX semantics are required but the SSL/TCP transport overhead isn't acceptable.
|
|
|
|
`zap-proto/fix` carries the **Financial Information eXchange (FIX) protocol** — versions 4.4 and 5.0 SP2 — over the ZAP wire. The wire encoding will be FIX-compliant (parses with any FIX engine after the transport bridge); the transport will be ZAP.
|
|
|
|
## Why on ZAP
|
|
|
|
- **Mutual KEM auth at the transport** — no per-session FIX Logon/CompID handshake security theater
|
|
- **No head-of-line blocking** — multi-stream framing means a slow market-data subscription doesn't stall order-entry
|
|
- **Lossless audit trail** — every message signed by sender ID and timestamped at wire receipt, not application time
|
|
- **Bridge to classical FIX** is part of the design — interop with QuickFIX engines is non-negotiable for any real venue
|
|
|
|
## Schema
|
|
|
|
Published at [zap-proto/fix/schema/zap_fix.zap](https://github.com/zap-proto/fix/blob/main/schema/zap_fix.zap). Maps every FIX 4.4 message type onto ZAP structs. Generated types via [SDK codegen](/docs/sdks).
|
|
|
|
## Roadmap
|
|
|
|
| Milestone | Target |
|
|
|---|---|
|
|
| Wire schema published (FIX 4.4) | ✅ |
|
|
| FIX 5.0 SP2 schema | in progress |
|
|
| Go acceptor + initiator | in progress |
|
|
| Bridge to QuickFIX TCP/SSL | proposed |
|
|
| Real-world performance harness | once runtime stabilizes |
|
|
|
|
We will not publish performance numbers until they're reproducible from [zap-proto/bench](https://github.com/zap-proto/bench). The current bench harness only covers HTTP-shaped workloads; a FIX-specific harness is part of the runtime delivery.
|
|
|
|
Track progress on [zap-proto/fix](https://github.com/zap-proto/fix).
|
|
|
|
## Related
|
|
|
|
- [Native ZAP RPC](/docs/protocols/native)
|
|
- [Transports](/docs/transports)
|