Open identity layer

Prove who you are. Keep what you own.

SL1 Connect lets a website ask for a passkey sign-in and receive a verifiable proof — not your password, not your seed phrase, and not permanent access to your wallet.

You stay in control Sites get proof, not keys One identity, many apps

Most apps blur identity, permission, and money into one login button.

SL1 keeps them separate so each step can be checked.
Sign in

Passkey, not a shared password.

You approve access with the device you already trust. The site learns who you are — not how to impersonate you later.

Permission

Every action has a reason.

Purchases, payouts, and sensitive changes leave a trail: who approved what, for which app, and when.

Wallet

Balances stay with you.

Rewards and receipts on the protocol ledger live here. Crypto and bank balances live in linked providers.

How it works

Three steps sites and people can actually follow.

01 Ask A site opens SL1 Connect
->
02 Approve You sign in on pass.simplelayer.one
->
03 Return The site gets a one-time proof
For developers

Built for real integrations, not demo logins.

SL1 Connect uses short authorize links, audience-bound proofs, and a registry of known clients so redirects stay predictable.

Connect Passkey sign-in Identity proof for your domain
Policy Checks before money moves Clear allow / deny decisions
Wallet Portable balances Receipts and rewards in one place
Settlement Recorded state changes Auditable after the fact
SL1 Identity

Who you are — not where your money is custodied.

Your passkey controls this identity. USDC, BTC, and other instruments live in linked providers such as Meanly Vault — not inside the protocol node.

Linked providers

none
Checking provider attachments

Providers own instruments. The protocol only lists what you have linked.

Link Meanly Vault

Passkeys

-- active

Add or rotate passkeys without giving custody to a marketplace.

Protocol activity

0 receipts
Syncing identity history --
For websites

Send people to pass.simplelayer.one to sign in.

The public site explains the protocol. The pass host handles passkeys only — so users always know when they are approving access.

pass.simplelayer.one

SL1 Connect issuer — passkey sign-in and short authorize links.

Open sign-in