Siavash Sameni
65f639052e
Append WZP integration tasks to FUTURE_TASKS.md (238→676 lines)
...
featherChat side (10 tasks):
WZP-FC-1: CallSignal WireMessage variant (2-4h)
WZP-FC-2: Call state management + sled tree (1-2d)
WZP-FC-3: WS handler for call signaling (0.5d)
WZP-FC-4: Auth token validation endpoint (2-4h)
WZP-FC-5: Group-to-room mapping (1d)
WZP-FC-6: Presence/online status API (0.5-2d)
WZP-FC-7: Missed call notifications (0.5d)
WZP-FC-8: Cross-project identity verification test (2-4h) CRITICAL
WZP-FC-9: HKDF salt investigation — VERIFIED: no mismatch (b""→None == None)
WZP-FC-10: WZP web bridge shared auth (1-2d)
WZP side suggestions (9 items):
WZP-S-1 through WZP-S-9 covering auth, signaling bridge,
room access control, proto publishing, CLI flags, and
6 hardcoded assumptions that conflict with integration.
All tasks reference specific file:line in both codebases.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com >
2026-03-28 08:50:13 +04:00
Siavash Sameni
de1ce77fea
IDP_SMART_CONTRACT.md: featherChat as IdP + on-chain ACL (1111 lines)
...
featherChat as Identity Provider:
- OIDC provider endpoints (/auth/oidc/authorize, /token, /userinfo)
- JWT tokens with fingerprint, alias, eth_address, groups claims
- Authentik integration (featherChat as upstream IdP, group sync)
- SAML support for enterprise
Smart Contract Access Control:
- FeatherChatACL Solidity contract (server/group/feature access)
- secp256k1 address from same BIP39 seed = on-chain identity
- NFT-gated access (ERC-721/ERC-1155 membership)
- Token-gated access (ERC-20 staking)
- DAO governance for group membership decisions
- UUPS upgradeable proxy pattern
Hybrid architecture:
- OIDC token carries on-chain permissions as claims
- Event-driven sync (WebSocket RPC + periodic poll + sled cache)
- L2 deployment (Arbitrum/Base/Polygon) for low gas costs
Feasibility: 7-11 weeks across 4 phases.
Comparison with SpruceID, Ceramic, Lens, XMTP.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com >
2026-03-28 08:07:34 +04:00
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
Siavash Sameni
2dbbc61dfe
Comprehensive documentation: architecture, usage, integration, progress, security
...
docs/ARCHITECTURE.md (531 lines):
System design, ASCII diagrams, crypto stack, dual-curve identity,
wire protocol (7 WireMessage variants), server/client architecture,
data flow diagrams, storage model, extensibility points
docs/USAGE.md (550 lines):
Complete user guide: installation, all CLI commands (10),
all TUI commands (20+), all web commands, file transfer,
identity management, aliases, groups, multi-device, backup,
keyboard shortcuts
docs/INTEGRATION.md (542 lines):
WarzonePhone concept, Ethereum/Web3, OIDC, DNS federation,
transport abstraction, multi-server mode, custom clients,
ntfy, how-to guides for extending message types/commands/storage
docs/PROGRESS.md (234 lines):
Timeline, Phase 1 (16 features), Phase 2 (16 features),
v0.0.20, 28 tests, bugs fixed, known limitations, Phase 3-7 roadmap
docs/SECURITY.md (438 lines):
Threat model, 8 crypto primitives, key derivation paths,
forward secrecy, Sender Keys trade-offs, seed security,
server trust, WASM security, known weaknesses,
comparison with Signal/Matrix/SimpleX
Total: 3,751 lines across 8 doc files.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com >
2026-03-28 05:25:46 +04:00
Siavash Sameni
60a7006ed9
Add documentation: protocol spec, server admin, client guide
...
docs/PROTOCOL.md (520 lines):
- Identity model (seed → Ed25519 + X25519 via HKDF)
- X3DH key exchange (4 DH operations, ASCII flow diagram)
- Double Ratchet (chain/DH ratchet, skipped keys, state machine)
- KDF chains with domain separation strings
- AEAD (ChaCha20-Poly1305)
- Wire format (WireMessage enum, bincode serialization)
- Pre-key bundle format and lifecycle
docs/SERVER.md (429 lines):
- Build and run instructions
- Full API reference with request/response examples
- Database structure (sled trees)
- Deployment (nginx reverse proxy, systemd unit)
- Security considerations
- Backup and recovery
docs/CLIENT.md (507 lines):
- Quick start guide
- All CLI commands with examples
- Identity management and mnemonic backup
- Web client usage and limitations
- Session and pre-key management
- Threat model table
- Troubleshooting guide
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com >
2026-03-26 21:59:19 +04:00
