FAQ

General

What is 1auth?

1auth is a passkey-based authentication and transaction signing SDK for smart accounts. It lets users authenticate and sign transactions using biometrics (Face ID, Touch ID, Windows Hello) instead of seed phrases or browser extensions.

Do users need a wallet extension?

No. 1auth uses passkeys which are built into modern browsers and operating systems. No extensions or apps required.

Which chains are supported?

1auth supports any EVM-compatible chain. Transactions are executed via cross-chain intents, so users can pay from any chain.

Accounts

What type of account do users get?

Each user gets a smart contract account (ERC-7579 modular account) controlled by their passkey. The account is fully self-custodial—only the user can authorize transactions.

Is my account address the same on every chain?

Yes. Your 1auth account has the same address on all EVM chains. You can receive funds on any chain to the same address.

What is chain abstraction?

Chain abstraction means users don't need to think about which chain they're on. Powered by Rhinestone, 1auth handles bridging assets and executing transactions across chains automatically. Users see a unified balance and can pay from any chain.

Do I need to bridge tokens manually?

No. When you make a transaction, 1auth automatically bridges assets as needed. You never need to manually bridge or worry about having the right tokens on the right chain.

Can I use the same account across different apps?

Yes. Your 1auth account works across all apps that integrate 1auth. Because authentication happens on a shared provider domain (passkey.1auth.box), you stay logged in across apps—no need to re-authenticate for each one.

Compatibility

Which browsers are supported?

Passkeys work in all modern browsers:

Which devices support passkeys?

Do password managers work with passkeys?

Yes. These password managers support passkey storage and sync:

Using a password manager lets you sync passkeys across all your devices and browsers.

Integration

Do I need viem or wagmi?

No. The React components work standalone without any web3 libraries. If you already use viem/wagmi, we provide adapters for those too.

Can I test against 1auth from localhost?

No. Passkeys (WebAuthn) require a secure context, and browsers block passkey operations on plain http:// origins other than localhost itself. Because 1auth authenticates on a separate provider domain (passkey.1auth.box), the cross-origin iframe and credential scoping make http://localhost unreliable or non-functional for the full authentication flow.

To develop locally, use one of these approaches:

• Self-signed certificate + /etc/hosts — Generate a self-signed TLS cert, add an entry like 127.0.0.1 local.myapp.dev to /etc/hosts, and serve your app over HTTPS on that hostname.
• Tailscale — Tailscale can provision valid HTTPS certificates for your machine via tailscale cert, giving you a *.ts.net domain that works out of the box.
• Caddy — Use Caddy as a local reverse proxy; it automatically provisions locally-trusted TLS certificates.

Is there a testnet?

Yes, testnets are currently available.

Security

How are passkeys secured?

Passkeys use public key cryptography. The private key never leaves the user's device and is protected by the device's secure enclave (TPM, Secure Enclave, etc.).

What happens if a user loses their device?

Passkeys sync across devices via iCloud Keychain, Google Password Manager, or Windows Hello. Users can also register multiple passkeys as backup.