CPUNK

Table of Contents

1. 1. Introduction
2. 2. The Problem
3. 3. DNA — Decentralized Network Applications
4. 4. Architecture Overview
5. 5. Cryptographic Primitives
6. 6. The Nodus Network
7. 7. DNA Identity
8. 8. DNA Connect
9. 9. DNA Wallet
10. 10. CPUNK Token
11. 11. Platform Availability
12. 12. Roadmap
13. 13. Community & Governance
14. 14. Disclaimer

1. Introduction

CPUNK is a community-driven project building post-quantum, privacy-first infrastructure for digital identity, encrypted communication, and multi-chain asset management. The project is fully open source.

At its core is DNA (Decentralized Network Applications) — a single application that combines self-sovereign identity, end-to-end encrypted messaging, and a multi-chain cryptocurrency wallet. DNA runs on top of a custom-built, community-operated DHT network called Nodus, requiring zero centralized servers.

The CPUNK token, a CF20 token on the Cellframe blockchain, serves as the governance and utility token within the DNA ecosystem. All components are designed from the ground up to be resistant to quantum computing attacks using NIST-standardized post-quantum algorithms.

2. The Problem

Modern communication and identity systems share a common set of fundamental weaknesses:

• Centralized control — Identity providers (Google, Apple, Meta) can revoke access, censor users, and mine behavioral data at will.
• Metadata exposure — Even "encrypted" messengers leak metadata: who talks to whom, when, how often, and from where. Metadata alone is enough to reconstruct social graphs.
• Quantum vulnerability — RSA and elliptic-curve cryptography, used by virtually every messaging and wallet application today, will be broken by sufficiently powerful quantum computers. NIST has already published post-quantum standards (FIPS 203, 204, 205) as a direct response.
• Fragmented identity — Users maintain separate accounts, separate wallets, separate keys across dozens of platforms with no sovereign control over any of them.

3. DNA — Decentralized Network Applications

DNA is a single application built around three integrated pillars:

All three pillars share a single BIP-39 seed phrase. One backup, one identity, one set of wallets — unified under one cryptographic root.

4. Architecture Overview

DNA is built as a native C library with a Flutter (Dart) UI layer communicating via FFI. The transport backbone is the Nodus network — a custom Kademlia DHT.

The C engine is modular: each domain (identity, messaging, wallet, etc.) is an independent handler that processes tasks from an async queue. This design allows concurrent operations, clean separation of concerns, and easy extensibility.

5. Cryptographic Primitives

All cryptographic operations use NIST-standardized post-quantum algorithms at the highest available security level (Category 5). No classical-only fallbacks are used.

Key Derivation Flow

A single BIP-39 mnemonic is the root of all cryptographic material:

1. User generates (or restores) a 12–24 word seed phrase.
2. The seed derives the Dilithium5 signing key pair (identity).
3. The seed derives the Kyber1024 key encapsulation pair (messaging).
4. The seed derives blockchain-specific wallet keys for CF20, ERC20, SPL, and TRC20.

One seed, one backup, full sovereignty over identity and assets.

6. The Nodus Network

Nodus is a purpose-built, pure-C Kademlia distributed hash table (DHT) that serves as the transport and storage backbone for all DNA operations. It replaces the need for centralized servers entirely.

Design Parameters

Two-Tier Protocol

Nodus separates server-to-server and client-to-server communication into distinct protocol tiers:

• Tier 1 (UDP) — Kademlia peer discovery between Nodus servers: PING, FIND_NODE, PUT, GET.
• Tier 2 (TCP) — Client connections from DNA apps: AUTH, DHT_PUT, DHT_GET, LISTEN, CHANNELS.

Clients authenticate to the nearest Nodus node, which then handles routing, replication, and delivery across the DHT on their behalf.

Core Functions

• Peer discovery — Clients find each other via DHT key lookups. No central directory.
• Offline message delivery — Encrypted messages are stored in distributed mailboxes replicated across the 8 closest nodes. Recipients retrieve them upon reconnection.
• Identity resolution — DNA names resolve to public keys and routing hints via DHT lookups.
• Real-time subscriptions — Clients subscribe to DHT key ranges for instant notification of new messages, presence changes, and group updates.

7. DNA Identity

A DNA identity is a human-readable name (3–20 characters) cryptographically bound to a post-quantum key pair. Registration happens entirely on the Nodus DHT — no blockchain transaction, no central registrar, no fee.

Properties

• Self-sovereign — Ownership is defined by the private key. No entity can revoke, reassign, or censor a DNA name.
• Pseudonymous — No phone number, email, or real-world identity required.
• Permanent — Once registered, a DNA name is immutable and globally unique across the Nodus network.
• Ecosystem-wide — The same DNA name is used for messaging, wallet operations, governance, and all future CPUNK services.

Registration Flow

1. User creates or restores a wallet from a BIP-39 seed phrase inside the DNA app.
2. User chooses a unique DNA name. The app checks availability on the DHT.
3. The name is bound to the user's Dilithium5 public key and published to the Nodus network.
4. The identity is immediately usable for messaging, wallet, and all ecosystem interactions.

8. DNA Connect

DNA Connect is a fully decentralized, end-to-end encrypted messenger with no central servers, no phone number requirement, and no metadata collection. All message transport runs over the Nodus DHT.

Feature Set

Message Delivery

• Both online: Messages are delivered instantly via direct TCP connections. Each client subscribes to its contacts' DHT keys for real-time push.
• Recipient offline: The ciphertext is written to distributed mailboxes across the 8 closest Nodus nodes. The sender can go offline immediately after — Nodus handles the rest.
• Recipient returns: The client queries the DHT, retrieves pending messages, and decrypts them locally.

Encryption Model

Every message is encrypted with Kyber1024 + AES-256-GCM. The message envelope carries only 20 bytes of routing header — no sender identity, no timestamps, no IP addresses. Group messages use a Group Encryption Key (GEK) that is rotated on membership changes and distributed to members via individual Kyber1024-encrypted channels.

9. DNA Wallet

DNA Wallet is a multi-chain cryptocurrency wallet built directly into the DNA app. It derives all blockchain-specific keys from the same BIP-39 seed phrase as the identity and messaging keys.

Supported Chains

Key Properties

• One seed, all chains — A single mnemonic controls all wallets. No separate backups needed.
• Non-custodial — Private keys never leave the device. No server holds custody.
• In-chat transfers — CPUNK tokens can be sent directly within messenger conversations.
• Integrated DEX — Live swap quotes from Jupiter (SOL) and Uniswap (ETH) displayed natively.

10. CPUNK Token

CPUNK is a CF20 token on the Cellframe blockchain. It serves as the governance and utility token within the DNA ecosystem.

Utility

• Governance — CPUNK holders vote on protocol decisions and improvement proposals.
• Feed/Wall access — Posting to the public feed or personal wall requires burning CPUNK, preventing spam and giving posts economic weight.
• In-chat transfers — CPUNK is the only token transferable directly within messenger conversations.
• Ecosystem alignment — Holding CPUNK signals commitment to the privacy and decentralization values of the project.

11. Platform Availability

All builds are produced by CI/CD pipelines. The entire codebase — C engine, Flutter UI, Nodus server, and shared crypto layer — is open source and publicly auditable.

12. Roadmap

Completed

• Post-quantum identity system (Dilithium5 + Kyber1024)
• E2E encrypted 1:1 messaging, groups, channels, and feeds
• Multi-chain wallet (CF20, ERC20, SPL, TRC20)
• Nodus DHT network with PBFT consensus
• In-chat CPUNK transfers
• DEX integration (Jupiter, Uniswap, Cellframe DEX)
• Linux, Android, and Windows builds

In Progress

• iOS build pipeline
• Enhanced group management and admin controls
• DHT backup and restore for identity portability
• Network monitoring and node operator tooling

Planned

• File and media sharing (encrypted attachments)
• Voice messaging
• Extended governance framework (on-chain proposals)
• Node operator incentive mechanisms
• Additional blockchain integrations

13. Community & Governance

CPUNK is a community-driven project with no corporate entity behind it. Development is coordinated openly, and all code is available for public review.

• Open source — Full source code is hosted on GitLab (gitlab.cpunk.io) and mirrored on GitHub.
• Community governance — CPUNK holders participate in decision-making through on-chain voting.
• Node operators — Community members run Nodus nodes that form the network backbone.
• Contribution model — Anyone can contribute code, documentation, translations, or infrastructure.

Links