Wibble Client Core

wibble-client-core is the public client-side security and protocol core for the Wibble ecosystem. It covers MLS/OpenMLS-based security primitives, message canonicalization, and cryptographic hashing utilities. Current bootstrap uses an OpenMLS single-engine architecture with placeholder contracts for phase-0.

• Core modules: Security core, protocol logic, and shared utilities
• Responsibility: MLS/OpenMLS-based security primitives, canonicalization, and hashing
• Design: Platform-agnostic core
• Note: Tech stack to be determined per protocol-spec requirements

Scope

• Client-side security/protocol core only
• RFC 9420 lifecycle concepts mapped as scaffold placeholders (phase-1 wires real OpenMLS types)
• No backend implementation details, runbooks, or secrets

Bootstrap Architecture

Phase-0 scaffold is organized as a Rust workspace:

crates/
  wibble-core-domain/
  wibble-openmls-engine/
  wibble-client-core/
docs/
  adr/
  architecture/
specs/
  compatibility-matrix.yaml

Architecture docs:

• docs/architecture/openmls-single-engine.md
• docs/architecture/mls-protocol-checklist.md

Important:

• Current domain structs represent bootstrap intent types, not full RFC/OpenMLS wire-level models.
• OpenMLS integration and provider/storage wiring are phase-1 tasks.

References

• MLS protocol (RFC 9420): https://github.com/mlswg/mls-protocol/blob/main/rfc9420.md
• MLS architecture draft: https://github.com/mlswg/mls-architecture/blob/main/draft-ietf-mls-architecture.md
• OpenMLS repository: https://github.com/openmls/openmls
• OpenMLS book: https://book.openmls.tech/
• Implementation inspiration: https://github.com/signalapp/libsignal/

Build and Test

cargo check --workspace
cargo test --workspace

Contributing

• CONTRIBUTING.md
• CODE_OF_CONDUCT.md
• SECURITY.md
• SUPPORT.md: coming soon

Security

Security and privacy considerations follow the governance framework. Review the SECURITY.md for vulnerability reporting procedures.

License

Apache-2.0