2 Commits

Author	SHA1	Message	Date
Siavash Sameni	1c7b39c395	Rewrite WZP_INTEGRATION.md with confirmed code references (1209 lines) ... All [SPECULATIVE] markers replaced with [CONFIRMED] from actual WZP code. Key discoveries: - HKDF info string mismatch: featherChat uses "warzone-ed25519", WZP uses "warzone-ed25519-identity" — same seed, different keys. Requires 2-line fix in wzp-crypto/src/handshake.rs before integration. - Media is NOT DTLS-SRTP: WZP uses ephemeral X25519 DH + ChaCha20-Poly1305 with deterministic nonces (WireGuard-like, not WebRTC-like) - Transport is QUIC (quinn), not WebRTC/ICE - FEC is RaptorQ fountain codes, not Opus inband - 5 codecs: Opus 24k → Codec2 1200bps with adaptive switching - Relay operates on encrypted packets (zero-knowledge relay) 18 sections with concrete API contracts, code file:line references, and phased implementation roadmap. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-28 08:02:30 +04:00
Siavash Sameni	f7a517d8ea	WZP_INTEGRATION.md: featherChat ↔ WarzonePhone integration spec (1001 lines) ... Covers: shared identity model (same BIP39 seed), authentication flow (Ed25519 signed tokens), call signaling via WireMessage::CallSignal, DTLS-SRTP media encryption bootstrapped from Double Ratchet, group calls (SFU + Sender Keys), warzone scenarios (voice messages as attachments, mule delivery for missed calls). Phased roadmap: shared identity → signaling → encrypted calls → group calls. featherChat-side details confirmed against code. WZP-side details marked [SPECULATIVE] (WZP codebase was inaccessible). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-28 05:38:45 +04:00