Authentication
App-bound, credential-independent authentication with explicit assurance.
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
Browser and native clients#
MoonKey will use authorization code + PKCE with exact redirect matching, state, nonce, audience-bound tokens, rotating refresh tokens, and secure browser cookies. Third-party cookies are not an ecosystem SSO dependency.
- PKCE S256
- Exact origins and redirects
- App-bound authorization codes
- Refresh-token reuse detection
- Recent assurance for sensitive actions
Authentication methods#
The provider adapter layer is designed for email OTP, magic links, passkeys, Google, Apple, phone, external wallets, custom JWT, OIDC, and enterprise SSO. None is implemented as a production verifier yet.
- Passwordless
- Social
- Web3-native
- Enterprise and custom
Safe account linking#
Two credentials are never merged merely because they display the same email. Provider subject semantics, existing-session proof, step-up authentication, risk signals, and explicit user intent determine linking.
Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.