The current route is loading its editorial surface, data, and workspace context.
Authentication
Wallet access for the editorial launch workspace
Base Account and injected wallets both terminate at the same server-owned nonce, signature verification, and HTTP-only session boundary. The visual shell is lighter, but the auth contract stays unchanged.
Sign in with Base Account or a standard injected wallet. Both paths terminate at the same server-issued nonce, signature verification, and HTTP-only session boundary.
Server-issued nonce then signature, then signed cookie session.
Secure access
Authentication artwork stays supportive here so the wallet controls, session state, and next action remain the primary focus.
No session
No session yet
The authenticated studio session remains server-owned. Wallet connection state is a client convenience for sign-in and later onchain actions.
Authenticated
No
Session wallet
Not signed in
Studio access
Redirects to sign-in
Flow
Server auth contract
The server remains the source of truth: it issues the nonce, verifies either the classic wallet signature or the SIWE message returned by Base Account, and sets the HTTP-only session cookie.
POST /api/auth/noncePOST /api/auth/verifyGET /api/auth/sessionPOST /api/auth/logout
Boundary
Shared wallet UX
The same wallet connection layer also feeds collection deployment and minting, so the signed-in owner can stay on a single Base Account or browser-wallet path from auth through onchain execution.
