Peer Discovery
Nodus nodes help peers find each other and establish direct connections. No central directory — the DHT is the directory.
Infrastructure
Decentralized routing & discovery
Nodus Network
The Backbone of CPUNK
The Nodus Network is CPUNK's decentralized routing and discovery layer. It connects peers, delivers offline messages, and resolves DNA identities — all without central servers.
The Network
What Nodus nodes do
Every Nodus node contributes to a distributed hash table that keeps the CPUNK ecosystem reachable, resilient, and private.
Offline Delivery
When a recipient is offline, encrypted messages are stored in distributed mailboxes replicated across the 8 closest Nodus nodes. 7-day TTL.
Identity Resolution
Resolves DNA names to public keys and routing hints. Look up any identity on the network without a central registrar.
Zero Knowledge
Nodus nodes only store and forward encrypted blobs. They cannot read message contents, identities, or metadata. Privacy by architecture.
Real-Time & Offline Delivery
DNA-Messenger uses the Nodus Network for all message routing. The delivery path depends on whether the recipient is currently online.
- Both online: Messages arrive instantly via direct TCP connection. Each client listens to their contacts' DHT keys.
- Recipient offline: The ciphertext is written into distributed mailboxes replicated across the 8 closest Nodus nodes.
- Recipient comes back: Their client queries the DHT, pulls pending messages, and decrypts locally.
All messages are E2E encrypted (Kyber1024 + AES-256-GCM) with only 20 bytes of header metadata. The sender can go offline after sending — Nodus handles the rest.
Run a Nodus Node
Nodus nodes are operated by community members, validators, and infrastructure partners who want to strengthen the network. The node software is lightweight and designed for unattended operation.
- Deploy on any Linux server (bare metal or VPS)
- Expose only the required TCP ports for discovery
- No access to message contents — only encrypted blobs and routing metadata
- Stable uptime and bandwidth are the main requirements
Operator guides, systemd service files, and monitoring tooling will be published as the network matures.
Join the CPUNK movement
Download DNA Connect, join the conversation, and find a piece of the project you want to improve. Every meaningful contributor once started as a community member.