how it works

The password was the bug.

For fifty years, proving who you are has meant a secret stored on someone else's computer. Every breach, every reset email, every "security question" about your first pet is the same design flaw wearing a different costume:
your identity lives with a counterparty, and you rent it back.

Passless deletes the counterparty. A name you choose is transformed — on your own hardware, by open one-way mathematics — into keys that never leave it. Nobody issues your identity. Nobody hosts it. There is nothing to breach, because there is no vault of secrets anywhere but in your hands.

Three moves

1A name becomes keys

Your handle runs thru deterministic, memory-hard derivation on your device. Same name, same identity — derived fresh every time, stored never.

2Your devices are the keyring

Each device holds its own key, bound into a fleet by a signed membership chain. Add a new phone from an old one with a few spoken words or a tap and a confirmation. Lose one? Remove it from any other — the keys rotate away from it cryptographically, and the lost device is locked out of everything sealed after that moment.

3Every app, one identity

A messenger, a calendar, anything built on the stack — the same fleet, the same trust, zero new accounts. Apps ride your identity; they don't own it.

The honest trade

There is no password reset because there is no password. There is no account recovery because there is no account. The first human to claim a name owns it — permanently. That isn't a missing feature; it is what ownership means. We write this in plain language, not terms and conditions, because there is no company on the other side of the agreement. There is only the software, and you.

Proof it works

Passless isn't a whitepaper. The first application is live: a post-quantum, peer-to-peer messenger with no servers holding your words.

For builders

The substrate is open Rust crates. Making your app passless means deleting your accounts table, not adding an SDK login screen.