Authentication

The client supports passkey-backed accounts and wallet-aware recovery through shared auth modules. The implementation and provider configuration own ceremony details; this page explains the user boundary.

Flow

1. The client establishes the intended presentation and chain context.
2. Shared auth hooks start sign-in or registration with the configured relying party.
3. The resulting account/session becomes the identity used by application and transaction flows.
4. Recovery paths must preserve account continuity and make failure states explicit.

Testing boundary

Passkey ceremonies depend on the configured relying-party domain and cannot be treated as proven by localhost mocks. Use mocks for deterministic component and state tests; use the authenticated Brave profile on the appropriate deployed origin for real ceremony proof. Never log credentials, challenge material, wallet state, or session identifiers.