Encryption hides what you say. The Veil hides who you say it to.
Even a perfectly private payment can be traced by watching the network: which computer sent it, and when. The Veil is MoneroUSD's own post-quantum mix network, built so that watching the wires tells an observer as little as watching the chain.
Partly built · in testing on real nodes
Three hops, one layer each.
Your wallet wraps a packet in three layers of encryption, one per relay. Each relay can remove only its own layer, so it learns only the hop before and after it. Every packet has the same size; each hop checks a MAC and refuses replays and tampered packets.
Relays send cover traffic at a constant rate, so a real packet is one among many identical ones. And your payment never leaves from your own node: it's pushed through the mix to a random node, which announces it as its own.
Private reads: the server doesn't learn what you asked for.
Hiding who asked is half the job; a server that knows which page or record you fetched still learns something. The Veil reads with private information retrieval (PIR), in tiers, fastest first:
- Local: data every node already holds — an instant read, nothing leaves your device.
- Two-server PIR: two nodes each scan a whole bucket with a key that looks random; combined, the answers give you your item. Neither learns which item it was.
- Single-server PIR with a small client hint, for sublinear server work.
- The mixnet, for anything else.
Attacks, and where each defence stands.
Every defence is listed with its real status. "Built" means it runs on test nodes; none of this is outside-audited yet.
| Attack | The Veil's answer | Status |
|---|---|---|
| Take down a directory | There are no directory authorities. Relay records are gossiped; a node needs one live peer. | Built |
| Record now, decrypt later | ML-KEM-768 links and packets, ML-DSA records — no pre-quantum key exchange to harvest. | Built |
| Tag or replay packets | A MAC per hop, a per-epoch replay set, fixed packet size. | Built |
| Flood a relay | Load-priced link puzzles, per-link rates, bounded queues that drop cover first. | Built |
| Tor goes down | Nodes move to the Veil in about 10 s and back in about 2 s. | Built |
| Global timing analysis | Constant-rate cover, per-hop delays, the private push, private reads. | Partly built |
| Isolate one node (eclipse) | Pinned first hops, peers from several sources, rotation. | Partly built |
| Block by address list | Relays drawn from a view nobody publishes whole; onion faces and BLE links. | Partly built |
| Block by fingerprint (DPI) | A handshake encoded so every byte looks uniformly random, with fixed frames. | Design |
| Sybil relays | Routes weighted by bonded SAT, so owning half the routing costs half the bonds. | Design |
The limits, stated plainly.
No network can promise perfect anonymity against everyone. Anonymity is bounded by the crowd you hide in, and there is a proven trade-off between anonymity, bandwidth and delay. Someone who cuts every link a node has can stop any network — the Veil's aim is that nothing short of that takes it down, and that it heals by itself once links return.
The Veil's own launch gate: every row above built with a real-node check, an outside audit of the mix code, a run over real internet links, and a public soak.