Wallets & authentication

A wallet is an identity on the Dual network: its own address and the credentials that prove who controls it. Everything else here — objects, files, keys — belongs to a wallet, or to an organization a wallet is part of. There are four ways to sign in, and you can offer whichever suits your users: | How they sign in | Create the wallet | Return later | | --- | --- | --- | | A passkey — Face ID, Touch ID, Windows Hello | `/wallets/connect/passkey/register/*` | `/wallets/connect/passkey/login/*` | | A crypto wallet they already own | `/wallets/connect/eoa` | `/wallets/connect/eoa` | | Google | `POST /auth/provider/google` | `POST /auth/provider/google` | | Email or phone, with a password | `POST /wallets` inside an existing organization | `POST /auth/login` | All four end in the same place: a signed-in session and a wallet. The `/auth/*` endpoints look after the rest of that session — one-time codes, confirming an email or phone number, resetting a forgotten password, staying signed in, and signing out. `/wallets/sessions` lets someone see where they are signed in and end a session they do not recognise. To create a standalone account that can start a new organization, use `POST /organizations/wallets`, then create the organization with `POST /organizations`.