Getting started
MYTHASE documentation
What MYTHASE is, the problem it addresses and how its privacy infrastructure is put together.
MYTHASE is a privacy-native infrastructure layer. Instead of only encrypting what you say, it is designed to reduce what the network can learn about who is talking, where traffic goes and how systems relate to each other.
Most privacy tools protect content. MYTHASE starts one layer lower. Routes, endpoints, compute and storage are treated as things that should not stay still long enough to become a map. The engine that coordinates this movement is called RAVID.
Start here
01
The metadata problem
Why encryption alone leaves a detailed trail behind.
02
Design principles
The rules every component of the system follows.
03
RAVID architecture
Four layers that keep infrastructure in motion.
04
Threat model
Who we defend against, and who we don't.
What's inside
| Area | What it covers | Status |
|---|---|---|
| RAVID | Orchestration, stealth routing, ephemeral infrastructure, fragmented storage | Private testnet |
| Private network | Network access over transient, rotating paths | In design |
| Private messenger | Metadata-minimal communication | Planned |
| Stealth wallet | Local-key asset interface with a reduced footprint | Planned |
How to read these docs
- Getting started explains the problem and the reasoning behind the design. No technical background needed.
- Architecture goes layer by layer through RAVID: what each part does and how they fit together.
- Products describes the applications built on top of the infrastructure.
- Security is the honest part: the threat model, what is out of scope and the known limits.
- Project holds the roadmap, FAQ, glossary and brand assets.