Wallets
A wallet login proves that the user holds a blockchain address: the wallet signs a message that names your app, the address and a one-time nonce, and SeekAuth checks the signature. Nothing is sent to a chain and nothing costs a fee.
Turn Solana wallet (solana) or EVM wallet (evm) on in Login methods, or add them to the environment’s login methods. With both on, the login UI shows one chooser, each wallet labelled with its family.
Solana
Section titled “Solana”Sign In With Solana:
- The login UI names the address (base58, a 32-byte public key) in a
wallet_challengestep. - SeekAuth answers with what to sign: the domain and URI of the page (your app’s page, or the login address on the hosted page), the address, the statement “Sign in to {your app}.”, version
1, chain idmainnet, a 128-bit nonce, the time it was issued and its expiry. - The wallet signs it (with
solana:signIn, orsolana:signMessagewhere the wallet has no sign-in), and the UI sends the signed message and the signature inwallet_verify.
SeekAuth checks the signature first, then the message: the domain, the address, the nonce, the chain id where the message has one (it must be mainnet), the expiry and any “not before” time. Messages wrapped in Solana’s off-chain message envelope are accepted too.
Sign In With Ethereum (EIP-4361):
- The login UI names the address (
0xand 40 hex digits) and the wallet’s chain id in awallet_challengestep. - SeekAuth writes the EIP-4361 message itself and answers with it, the address in its checksummed form and the chain id.
- The wallet signs it with
personal_sign, and the UI sends the signature inwallet_verify. SeekAuth recovers the signer’s address from it.
Any chain id is accepted (1 when none is given), and a login does not depend on it. Only externally owned accounts can log in: contract wallets that sign through EIP-1271 are not supported.
- A challenge expires 5 minutes after it was made, and its nonce is used up by the first
wallet_verify, whatever the answer. - The identity is the chain and the address (an EVM address in lower case). The same address always reaches the same account.
- A wallet nobody has used before makes a new account, if sign-up is open. The account has no email address, and a wallet is never linked to an existing account by an address.
- At most 10 new wallet accounts are made per IP address per hour in an environment. Where the plan or the environment asks for a captcha on every sign-up, a new wallet solves one before its account is made. See Bot protection.
- A wallet login is
aal1withamr["wallet"]. A user who has a second factor still completes it.
Wallet accounts and email addresses
Section titled “Wallet accounts and email addresses”A wallet account starts without an address. If an app writes to its users, make it require an email address on its Access page (email_required): someone without an address is then asked for one, and proves it with a code, before the login completes. See Apps that need an email address.
How the SDK finds wallets
Section titled “How the SDK finds wallets”auth-react looks for wallets in the browser:
- Solana: wallets registered with the Wallet Standard that support
solana:signInandstandard:connect. - EVM: wallets that announce themselves with EIP-6963, or
window.ethereum(shown as “Browser wallet”) when none does.
listWallets(chain?) returns what it found, loginWithWallet(name?, { chain }) logs in without the modal, and <LoginFlow wallets={…}> takes a source of your own. See auth-react.