SerenityVault Protocol™ — architecture project•ML-KEM-1024 + ML-DSA-87 (NIST FIPS 203/204)•TRINITY: defense, governance, coordination•AURA and METATRON: integration in progressSerenityVault Protocol™ — architecture project•ML-KEM-1024 + ML-DSA-87 (NIST FIPS 203/204)•TRINITY: defense, governance, coordination•AURA and METATRON: integration in progressSerenityVault Protocol™ — architecture project•ML-KEM-1024 + ML-DSA-87 (NIST FIPS 203/204)•TRINITY: defense, governance, coordination•AURA and METATRON: integration in progress
Privacy and zero-knowledge

Privacy and zero-knowledge

Accueil›zero-knowledge

Architecture — limits to document

The architecture explores reducing the data accessible to operators. Client-side encryption and zero-knowledge proofs are distinct mechanisms: their presence and scope must be demonstrated separately.

Key management

The model must specify who can create, use and recover keys, and the effects of losing a device or access.

Scope of proofs

A cryptographic proof concerns a specific statement and assumptions. By itself, it does not establish the security of the whole service or the absence of metadata collection.

Evaluation needed

Scope, dependencies and compromise scenarios must be published with test results. This page does not present a completed audit.

Discuss the project