Technical Report: The ZK Protocol
The Zero Knowledge (ZK) Protocol is the architectural foundation of a messaging system engineered for C-Level executives, Investigators, Journalists, and Authorities. It allows users to exchange AES-256-GCM encrypted messages using a locally generated 64-character secret key (derived from SHA-256). The primary objective is to guarantee total privacy by design, shifting the paradigm from “Server-Side Trust” to “Client-Side Certainty.”.
The architecture of the ZK Messenger is built to ensure that the server acts only as a blind relay, never as a custodian of secrets.
1. Client-Side Key Generation (The Zero-Knowledge Vault)
The core axiom of this protocol is: The server never touches the private keys.
- User-Defined Entropy: Encryption keys are generated locally on the user’s terminal using high-entropy seeds.
- Non-Custodial Architecture: At no point in the handshake is the private key (or its derivative) transmitted to the database. The server only stores the Public Proof, which is mathematically sufficient to validate handshake but useless for decryption.
2. Forensic Hashing via SHA-256
To satisfy the ZK Protocol standards, every packet must have a “Digital Birth Certificate”:
- Data Integrity: Each message is hashed into a SHA-256 string before leaving the terminal.
- Immutable Anchoring: This hash is recorded in the Public Ledger. It provides a “Proof of Existence” (PoE) that the communication occurred at a specific nanosecond without revealing a single byte of its content or its sender.
3. The Public Ledger: Real-Time Audit
The ledger is the transparent heart of the ZK protocol. It is a read-only stream of cryptographic events, visible to all but decodable by none except the intended recipient.
- Live Registry: It displays the hexadecimal fingerprints (Hashes) of every successful relay.
- Status: It confirms that the Zero-Knowledge Tunnel is operational, providing a live feed of system integrity.
4. Execution Logic: The Triple-Layer Isolation
The system operates on three independent layers connected only by a Synthetic Email that acts as a Master UID:
- Subscription Layer: Manages sovereign account status.
- Access Layer: Handles the session handshake.
- Audit Layer (ZK Table): Stores the SHA-256 hashes and the public identity tokens.
The Ledger is Live
The protocol is currently executing. By eliminating the “black box” of server-side encryption and placing the keys exclusively in the users’ hands, we have removed the single point of failure.
- Current Protocol Status: Active.
- Encryption Standard: User-Defined / AES-256-GCM.
- Audit Standard: SHA-256 Ledger.