Protocolo
OMEGA
Experimental communication architecture over Tor onion services. The project explored browser-side cryptography, relay minimization and ephemeral session state. It is presented as a dated research record, not as a production-ready protocol.
Research question
OMEGA examined whether a small relay could transport application ciphertext while leaving message encryption and session-key operations at the endpoints. The archived assessments document several revisions to that model.
Assumptions and limits
- Endpoint integrity. Client-side cryptography does not protect an already compromised endpoint.
- Metadata. Tor routing and traffic-shaping ideas were design inputs, not proof of anonymity.
- Memory handling. Explicit buffer clearing can reduce exposure but cannot establish complete erasure across the platform.
Current status
The published OMEGA documents are archived. They remain available to show the design process, identified errors and subsequent changes; no current deployment claim is made.
Archived design outline
Endpoint operations
WebCrypto and native-client experiments using AES-GCM, ECDH and password-derived inputs across different revisions.
Transport
Node.js relay experiments over Tor onion services.
State model
Session-oriented in-memory state with explicit cleanup paths; no claim of complete persistence elimination.
Evidence
Source reviews, targeted tests and migration notes tied to dated repository states.