Web3 & Sign in with Ethereum

For web3 and crypto-native products, Atlas supports Sign in with Ethereum (SIWE) — authentication with a user's wallet instead of an email or password.

How SIWE works

1. The user connects their wallet (e.g. MetaMask, WalletConnect).

2. Atlas issues a unique, single-use challenge message to sign.

3. The wallet signs the message with the account's private key — nothing secret is transmitted.

4. Atlas verifies the signature against the wallet address and issues a session.

The wallet address becomes an identifier on the user, so a returning user is recognized by their address.

Enable it

1. Sign-in methods → Web3 / Sign in with Ethereum → toggle on.

2. Optionally require a verified email in addition to the wallet, if your product needs to reach users off-chain.

Combining with other methods

SIWE can be a user's only method, or one of several. A user might connect a wallet and add an email code as a recovery path. All the same MFA and session rules apply.

Good practice

• Because a lost private key can't be reset, encourage users to add a recoverable factor if your app holds anything they'd hate to lose access to.

• Treat the wallet address as an identifier, not a profile — collect a display name separately.

Next

Require a strong second factor → Multi-factor authentication.