i liked keystone if its not taken already by someone already logoi liked keystone if its not taken already by someone already

KEYSTONE / Identity protocol concept

Your identity.
Not your phone number.

A new approach to staying connected: device-native passkeys, an independent identity, and recovery shared with people you trust. Designed to leave passwords and SMS lockouts behind.

Explore the recovery model How it works

Early-stage concept. Not a live authentication service.

i liked keystone if its not taken already by someone already hero

Our design commitments

No password to remember

No SMS dependency

No single recovery gatekeeper

01 / The architecture

Less friction.
More ways back in.

For everyday sign-ins, international SIM changes, and the day a device goes missing. Access should follow you—not your carrier.

The everyday experience
A familiar touch.
A different foundation.

The proposed FIDO2 / WebAuthn sign-in uses Face ID, Touch ID, or Windows Hello to approve a cryptographic signature. Your device holds the private key; you don’t type a password.

Device-native authentication
01

An identity independent of your SIM

A decentralized identifier is intended to anchor access without relying on your phone number. Switch carriers without making SMS your recovery plan.

02

Recovery through shared approval

The proposed threshold model distributes recovery shares across trusted guardians and devices. No single guardian can restore your identity alone.

03

A new device. A coordinated handoff.

Signed key rotation is designed to update participating apps when you replace a device. This requires app integration; it does not change access to every existing account.

02 / A way back

Lost device.
Not a lost identity.

Imagine a recovery policy with five guardians and three required approvals. Shamir’s Secret Sharing provides the basis for distributing recovery material without handing one person the whole key.

Illustrative flow only. Recovery timing, guardian verification, and security safeguards still need implementation and review.

Example recovery policy3 of 5
  1. 01

    Request recovery on a new device

    Start a recovery request for your existing identity.

  2. 02

    Gather guardian approvals

    Three designated guardians approve under your chosen policy.

  3. 03

    Re-establish access

    Restore key access and rotate credentials for integrated apps.

Built around continuity

Your next phone shouldn’t mean starting over.

Explore the thinking behind KEYSTONE: passkey-first access, identity independence, and a recovery path you choose.

Explore the protocol