Privacy guides
LVR1 and LGS1 are Livara-specific protocols. This overview describes the current client implementation; it is not a proof of protocol security or confirmation that every deployed client uses the same version.
Content reviewed ·
Plaintext and encryption keys
AES-256-GCMCiphertext and routing metadata
LVR1 / LGS1Decrypt and display locally
AES-256-GCMLVR1 combines P-256 key agreement with ML-KEM-768 key encapsulation. HKDF-SHA-256 derives key material, and AES-256-GCM protects messages and authenticates their context. Sending and receiving chains advance message keys; the implementation also includes classical and post-quantum epoch updates.
Each sender maintains a signed sender-key chain. Sender-key material is distributed to members through LVR1-encrypted messages, and AES-GCM protects group content. Membership changes trigger key rotation. Signed membership checks help detect inconsistent group state; they are not an independently witnessed transparency service.
Retained history copies and recoverable identity material affect compromise exposure: a ratchet alone does not establish application-wide forward secrecy. Compare safety numbers to verify a contact's identity. A server still participates in identity delivery and group membership coordination.
ML-KEM-768 is an implemented post-quantum component, not a guarantee that every part of the application resists quantum attacks. LVR1 and LGS1 are not Signal Protocol or MLS.