HTML edition · Version 1.0 · 20 August 2026
Executive summary
M2 is an Android-first communication system for small teams that need a separate, identity-minimizing Channel. It combines accountless participation, device-level encryption, Tor-routed messaging and limited server retention.
Channel-level identity
Ordinary participants can join without a phone number, email address or real-name account. Identity is scoped to each Channel instead of being joined into a global M2 profile. “Identity-minimizing” describes this reduction in centralized identity data; it is not a claim about cryptographic zero-knowledge proofs.
Encryption on the device
Messages and supported files are encrypted for intended recipients before leaving the device. Local history follows the app’s encrypted storage design. M2 Codes and signed invitations carry authority and should be distributed carefully.
Tor and v3 Onion routing
Embedded Tor carries messaging traffic to a v3 Onion Service. This means the messaging gateway does not receive a direct originating clearnet connection. The public Mirage Project website is separate and runs over ordinary HTTPS through Cloudflare.
Authenticated delivery and deletion
The gateway holds encrypted payloads only for delivery. Authenticated durable receipt initiates server-side deletion; undelivered ciphertext expires after a maximum of 48 hours. M2 is designed for active coordination rather than permanent recordkeeping.
Signed release supply chain
The Android client verifies a trusted manifest, compatible package, increasing version, immutable APK SHA-256 and the established signing certificate before asking Android to install. The marketing website is not the update authority.
Operating guidance
M2 is strongest when teams keep Channels short-lived and distinct, protect devices, separate personal and operational identities, and control invitation material. Information visible to an authorized recipient can still be copied, photographed or exposed by a compromised endpoint. Tor reduces direct origin exposure but does not remove every form of traffic analysis.
The public HTML edition uses the owner-provided whitepaper as its editorial source and aligns the language with the current implementation. The source DOCX is not offered for download because its publication metadata and unsupported draft wording have not been approved as a public artifact.