Atlas Protocol
Password Leaks, SPAM & Phishing
The web still asks you to trust too many forms, too many inboxes, and too many look-alike identities. Atlas protects the real key, delegates limited permission to apps, and gives messages real sender context.
How many times have you reset the same password?
Chances are, at least one of your email-password combos is already circulating in breach datasets. The pattern is broken: the internet keeps asking you to type weak secrets into website after website.
Passwords leak. Emails leak. Phishing pretends to be real. Spam fills every inbox that cannot tell who is actually talking.
Passwords are the wrong primitive
- Every login form is an attack surface. Another place to phish, log, or leak you.
- Email is not a trustworthy identity layer. Providers can read it; look-alike addresses power scams.
- OIDC helps, but partially. It reduces reuse yet keeps identity locked inside major providers.
- Spam and phishing are cheap at scale. Sending costs nothing and identity is barely verified.
Users juggle passwords, providers hold too much data, inboxes fill with noise.
One protected key, limited app permissions, and real identity context before messages reach anyone at scale.
Your Real Key Stays in One Safe Place
Hardware or CustodianYour main key stays in hardware or with a custodian that keeps it encrypted and helps authorize actions without exposing it to apps.
Most apps never need your real key — just temporary permission for a specific job.
Apps Get Delegated Keys, Not Your Main Secret
Scoped AuthorizationYour custodian issues a delegated key — a token with an expiration and allowed actions. One app publishes, another edits your profile, a payment app handles only small transfers.
Each key is narrow, temporary, and purpose-built — much safer than permanent full access.
Leaks Become Smaller Incidents, Not Full Disasters
Short-Lived DamageThe most exposed credential is always the least powerful. Delegated keys have short lifetimes, narrow scope, and can be revoked.
If your main key is ever compromised, key rotation lets ownership follow your new key instead of staying trapped behind the old one.
- Delegated key leak means temporary and limited damage.
- Main key compromise still has a recovery path through rotation and renewed ownership proofs.
Messages Arrive With Real Sender Context
Identity + TrustAn inbox accepting messages from anyone with no identity and no cost is a spam machine. In Atlas, trust is built into the protocol — behind each action is a verified identity.
Clients can require unknown senders to prove more or spend more. Spam and phishing lose their key advantage: reaching everyone while being nobody.
Identities Are Easier to Recognize, Harder to Confuse
Standard Avatars + NamesAtlas uses standard avatars and three-part names derived from hash — visually consistent and hard to confuse with copycat handles.
Before you send a message or transfer, you see a recognizable identity, not a vague string.
Fewer secrets everywhere. More trust where it matters.
Users stop typing their strongest secret into every app on the internet.
Apps get temporary, narrow permissions instead of permanent full access.
Short-lived credentials and key rotation reduce long-term damage.
Unknown senders no longer get free, identity-free access to everyone.
Recognizable identities and trust signals make impersonation less effective.
