Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 1.45 KB

File metadata and controls

40 lines (29 loc) · 1.45 KB

Lattice Mesh Protocol (LMP) — Overview

This document provides a guided tour of the protocol specification in MAIN.md.

What LMP is trying to achieve

  • Confidentiality: message contents remain secret.
  • Integrity: messages cannot be modified without detection.
  • Forward secrecy: compromising long-term keys does not reveal old messages.
  • Metadata minimization: relay nodes learn only per-hop routing information.

What LMP does not guarantee

  • Guaranteed availability under sustained DoS.
  • Perfect resistance against a truly global passive adversary.
  • Security if endpoints are permanently compromised.

The moving parts (mental model)

  • Identity layer
    • Long-term identity keys authenticate who you are.
  • Session establishment (handshake)
    • Hybrid key establishment combines classical and post-quantum secrets.
  • Messaging layer
    • Double Ratchet derives one-time message keys.
  • Transport / mesh routing
    • Messages are wrapped into fixed-size cells and forwarded hop-by-hop.

Suggested reading order

  1. MAIN.md → “Threat Model” and “Key Lifecycle”
  2. docs/GLOSSARY.md (reference as needed)
  3. MAIN.md → “Handshake Protocol”
  4. docs/EXAMPLES.md (handshake walkthrough)
  5. MAIN.md → “Message Encryption” and “Metadata Handling”

Conventions

  • MUST / SHOULD / MAY are interpreted per RFC 2119.
  • Example blocks are illustrative; the normative rules are in MAIN.md.