DNA-Messenger is the communication layer of the CPUNK protocol: a post-quantum, P2P messenger that uses DNA identities instead of phone numbers, and is designed to resist both classical and quantum attacks.
Most messengers depend on central servers and classical cryptography. DNA-Messenger focuses on three things: identity, quantum safety, and real P2P communication.
DNA-Messenger uses DNA identifiers (your CPUNK identity) as the addressing layer. Messages are encrypted using NIST-selected post-quantum algorithms and routed peer-to-peer whenever possible, with support for offline delivery via distributed storage.
DNA-Messenger uses a combination of ML-KEM / ML-DSA (Kyber/Dilithium family), AES-256-GCM, and SHA-3 to protect session keys, message contents, and identities. Uses only 20 bytes header (metadata) and collects no personal information.
When both parties are online, messages flow peer-to-peer. When one party is offline, messages can be stored in distributed mailboxes so they can be retrieved later without relying on a single central server.
DNA-Messenger is designed around a local-first, P2P architecture with a minimal bootstrap layer. A simplified view of how a message is sent:
The objective is to combine the convenience of modern messaging apps with infrastructure that remains viable in a post-quantum world.
DNA-Messenger is for privacy maximalists, and communities who want secure communication without compromise. We collect nothing, store nothing, and leak nothing. Your identity and messages stay yours — protected for the future.
Developers who want to integrate post-quantum messaging into their own apps, tools, or bots using DNA identities as the addressing layer.
Groups that need communication channels which are not tied to Big Tech accounts and are resistant to large-scale surveillance or deplatforming.
Users and organizations that want to stay ahead of the curve on quantum-era threats and avoid harvesting of encrypted traffic today that could be decrypted tomorrow.
DNA-Messenger is being developed step-by-step, starting from the core protocol and progressively adding user-facing clients and features.
The goal is to keep the protocol open and flexible so that third-party clients and integrations can emerge around the core CPUNK stack.
DNA-Messenger is the communication backbone of the CPUNK ecosystem. If you are interested in integrating it into your own project, start from the protocol docs and join the community channels for technical discussion.
As the protocol matures, this page can be extended with client download links, public APIs, and integration examples.
