Security
Security here isn't a layer bolted onto the framework — it is the framework, expressed in the same mathematics as everything else. Your identity is an equation only you can reproduce. Your secrets live in a sealed context that computation can use but never read. Your encryption binds to the clock, so a ciphertext is tied to the Zeqond it was made at. And your defenses are mapped onto real operators, not heuristics.
Three concerns
Identity
Who you are is a mathematical object — an equation that derives your ID deterministically, with a recovery file as the only way back in.
Secrets
Keys and credentials live in the ZSC — a sealed context that hands computation what it needs without ever exposing the raw value.
Defense
Phishing, tampering, and quantum adversaries are handled with named, auditable mechanisms — including post-quantum posture.
Explore
Identity
Your account as a mathematical object.
- ZeqID — your identity derived from an equation, the same on every node
- The account equation — equation login and the
.ZEQrecovery file - Identity tiers — Simple and Expert tiers, and what each key can do
Secrets & encryption
Where secrets live, and how payloads are sealed.
- ZSC — the secure context — the sealed key vault
- HITE encryption — AES-256-GCM with the Zeqond bound into the ciphertext
- Vault & password manager — zero-knowledge secret storage and derived passwords
- QM3 shared custody — M-of-N signatures as |ψ⟩ = ∑cᵢ|ϕᵢ⟩
Defense
Resisting phishing, tampering, and quantum attack.
- Phish-Guard — phishing detection on the forensic operators
- Post-quantum posture — what breaks, what doesn't, and why
Communication
Talk without pooling your content.
- Messaging & mail — peer-relayed messaging and mail that retain as little as possible
The identity and auth APIs live in the reference; the encryption and protection APIs in the security reference.