Velix ID first
Accounts are designed around a Velix ID instead of starting with a phone number, email address, or public social profile.
Velixnet private messaging
Encrypted messaging with the keys kept on your device.
Velixnet is a one-to-one messaging app built around libsodium encryption, device-held identity keys, and a PHP delivery server that stores sealed message envelopes instead of plaintext.
How E2EE works here
Velixnet encrypts the message before the server ever sees it.
End-to-end encryption means the useful message content is protected on the sending device and opened on the receiving device. The server still helps deliver the message, but it is handling an encrypted envelope rather than readable text.
Velixnet uses a fresh per-message session key, XChaCha20-Poly1305 authenticated encryption, and Curve25519 key wrapping so the recipient can open the message locally. The sender also receives a wrapped copy, which allows sent history to be recovered after restart without storing plaintext on the server.
QR identity verification gives two users a direct way to compare contact keys. That matters because encryption is only meaningful if the key belongs to the person you think it belongs to.
- Your device encrypts the message content.
- The server receives and forwards a sealed envelope.
- The recipient device verifies and decrypts locally.
- Routing metadata is still treated as sensitive server-side data.
The difference
A private line, not another social platform.
Velixnet is built for direct encrypted exchange: two people, long-term identity keys on their devices, and a server that moves sealed envelopes instead of reading message content.
The app is intentionally narrow. It is not a feed, not a public profile system, and not an advertising product wearing a chat interface. The technical work is focused on message authenticity, key trust, and keeping plaintext out of the server boundary.
Small choices change the feeling of trust.
libsodium at the core
Messages use XChaCha20-Poly1305 for authenticated encryption, with Curve25519 crypto_box keys for identity and session-key wrapping.
QR verifies identity keys
Velixnet includes QR identity verification so two users can compare contact keys directly instead of trusting only what the server returns.
No attention economy
The purpose is private conversation, not engagement loops, ad targeting, social scoring, or learning how to sell more from what you say.
Honest privacy
Privacy is a boundary, not a spell.
Velixnet’s boundary is specific: the client encrypts UTF-8 message content before upload, wraps the per-message key for sender and recipient, and sends the server a compact Base64URL JSON envelope. PHP authenticates, validates public routing fields, and stores the unchanged encrypted payload.
- Curve25519 identity keys created by the client.
- Fresh 32-byte session key and 24-byte XChaCha nonce per message.
- Android Keystore or macOS Keychain-backed private key storage.
- Honest handling of routing metadata, the weak point of every delivery server.
Why it matters
Because strong encryption should still feel human.
For users who want private messaging without tying every conversation to a social profile or attention system.
For technical reviewers who want named primitives, clear server boundaries, QR key verification, and honest current limitations.
For controlled testing of a smaller messaging model: direct, authenticated, encrypted, and explicit about trust.
Quick view
Quick facts.
Verified: July 2026.
| End-to-end encryption | Yes. Message content is encrypted on the device before server delivery. |
|---|---|
| Identity verification | QR verification helps users compare contact keys directly instead of relying only on the server. |
| Phone number required | No. Velixnet is designed around a Velix ID. |
| Email sign-up required | No. The current design does not require an email address for account creation. |
| Metadata collection | Limited by design, not zero. Routing facts are the weak point of every delivery server. |
| Privacy shield | A quiet screen mode for active threads when the conversation needs to fade from view. |
| Independent security audit | Planned before beta launch. |
| Best for | Private direct communication without phone-number identity. |
Contact
Release-date updates without social feeds.
Leave a name and email if you want a direct message when Velixnet testing, release access is available or a note about another matter
Velixnet does not currently use social media accounts for official updates. Treat posts from social accounts claiming to be Velixnet as unverified unless this site lists them.