Browser wallet

Connecting requests the account address. Sign-in asks the server for a one-time challenge before requesting a signature. Auth receives that signature only after the stored challenge is consumed. A wallet session is not a confirmed email and does not link this address to an email account.

Not connected in this browser.

1. Connect an Ethereum browser wallet. Connecting does not create a session.
2. Request a one-time server challenge for this address, origin, and chain.
3. Sign that exact message in the wallet. Rejecting it creates no session.
4. A session exists only after Supabase Auth accepts the signature. The dashboard still requires a confirmed email.

A connected address is not a session. This page reports a session only after Auth returns one. Sign-in does not save a wallet link.

A wallet session is not a saved link to an email account.