The QNet Protocol,
measured.
Two devices, connected directly. No server in between.
Normally your traffic passes through a company's server. Even when the content is encrypted, that server still sees who talks to whom, and how often. QNet connects the two devices directly, so there is no such record, because there is nowhere to write it down.
Sovereignty
No middleman means no dependency on someone else's prices, terms, outages or jurisdiction.
Privacy
Who you talk to often reveals more than what you say. Direct connections leave no such trail.
Quantum-safe
Traffic recorded today can be decrypted later, once quantum computers mature. QNet can add a quantum-safe key exchange (ML-KEM-768) to the connection setup.
Recorded now,
opened later.
An attacker does not need a quantum computer today. They only need to store your encrypted traffic until they have one. Anything with a long shelf life (contracts, health records, source code, state communication) is therefore already at risk now.
The defence has to be in place before that day, not after it. Adding it later does not help: the recording already happened.
How we compare
Three questions decide whether a protocol is usable in practice: what protection costs, how often you still need someone else's server, and how long it takes to connect.
Cost of protection
Encryption costs us under 8 %, while doing more than the others.
Every protocol adds overhead on top of raw, unprotected data. WireGuard is leaner because it runs inside the operating system kernel and does far less: no peer discovery, no NAT traversal. QNet does all of that in userspace and still stays close.
Independence from third-party servers
We never fall back to a relay. The others do, for up to a third of all sessions.
This is the number that decides sovereignty. A relay sees the metadata, costs money per gigabyte, and is a single point that can fail or be shut down. For QNet it is not a rare fallback: there is none.
Inside the protocol
Four measurements, taken separately so it stays visible where the time actually goes.
Cryptography
Connection setup
Direct connections
Reconnect
Encryption throughput
A fresh key per message: 11.3 million times an hour.
Most systems keep one key for minutes at a time. If it leaks, everything sent in that window is readable. QNet replaces the key constantly, so a stolen key unlocks a single message. That is only possible because a full cycle costs 0.29 milliseconds.
Averages hide the bad cases. Here even the slowest 1 in 100 stays under half a millisecond: the speed holds up under load, it is not just a flattering average.
Recovery after an IP change
Switching network does not drop the session.
Walking out of the office moves a phone from Wi-Fi to mobile and changes its address. Most systems rebuild the whole connection. QNet restores the existing session instead, fast enough that a call or a transfer keeps running.
Scaling with hardware
Twice the hardware, nearly twice the throughput.
Many systems stop improving once cores are added, because the parts start waiting for each other. QNet still reaches 82 % of perfect scaling at sixteen parallel workers: capacity can be bought with hardware instead of redesigned.
at 16 workers
Twelve hours without a stumble
Fast for a second is easy. We ran it for half a day.
A benchmark measures seconds. Real deployments run for months, and that is where slow leaks and rare races surface. So we left a fifteen-node network running unattended for twelve hours and took a sample every fifteen minutes. All 49 samples found every node connected to every other one: no restarts, no failed decryptions, no silent degradation.
- Duration
- 12 hours, unattended
- Network
- 15 nodes, full mesh
- Samples
- 49, every 15 minutes
- Mesh alive
- 49 of 49 samples at 100 %
- Restarts
- 0
- Decryption failures
- 0
A separate three-hour run with the quantum-safe key exchange switched on produced the same result: full mesh, no restarts, no decryption errors.
How we measured
- Machine
- 12 dedicated cores, 55 GB memory
- Throughput run
- 5 runs × 10 s per dimension
- Endurance run
- 12 h, 15 nodes, 49 samples
- Date
- Throughput 7 Sep 2026 · endurance Jul 2026
- Setup
- Local connections, no internet in between
- Not included
- Internet travel time