Skip to main content

10. Implementation Map

Work in progress — not audited

This chapter is part of an initial draft specification. Enkrypted Chat has not been independently audited. Content may change.

10.1 Repositories → normative sections

RepositoryRoleSpec sections
glitr-chatEnkrypted Chat shell — cascade enabledP1.3, ch. 1–2
p2pMLSProvider, messaging, files, callsP3–P8, P4
uiShared UI, QR connectch. 5 (product)
chatSecurity reporting, related appsP1.8, SECURITY.md
signal-protocolRust Signal core, WASMAppendix B
cryptographyMLS, cascade, SFrameP5, Appendix A
websiteThis specificationCHANGELOG-SPEC

10.2 Key implementation files

ConcernLocation
Product cascade configglitr-chat/src/providers/P2PProvider.tsx
WebRTC + encryption corep2p/src/core/MLSProvider.tsx
File transfer / fast pathp2p/src/features/filetransfer/
Group stateglitr-chat + p2p group members state
QR connect UIui/src/components/molecules/ConnectByQRCode/
Security audit notesp2p/security-audit/

10.3 Public APIs

Enkrypted Chat does not expose a stable external SDK or public integration API. The specification describes behavior, not a supported third-party contract.

10.4 Test vectors

See Appendix A:

  • cryptographygolden-vectors.test.js (V1, V2), cascading-cipher-manager.test.js
  • p2pprotocol-golden-vectors.test.js (V4–V7), MLSProvider.*.test.tsx
  • signal-protocol — WASM / ratchet tests

Golden hex V1–V7 are published; live cascade V8 deferred to Profile-v1.

10.5 Build and delivery

  • Webpack Module Federation for remotes
  • Production builds may apply JavaScript obfuscation (does not affect spec semantics)
  • Android/Capacitor scripts exist in glitr-chat but are not production-targeted in this spec