InAppWallet
InAppWallet
is the ultimate persistent wallet provider option for your game. It supports email, phone, social and custom authentication schemes, and will persist across devices, platforms, and other SDKs.
It makes for a fantastic SmartWallet admin/signer and will make sure your users can have the same wallet address across all your games, apps and blockchains.
In-App Wallets support a variety of login methods:
- Email (OTP Login)
- Phone (OTP Login)
- Socials (Google, Apple, Facebook, Telegram, Farcaster, Line, Github, Twitch, Steam etc.)
- Custom Auth (OIDC Compatible)
- Custom Auth (Generic Auth Endpoint)
- Guest (Onboard easily, link other accounts later)
- Backend (Server Wallets)
- Siwe (Login with a seperate wallet supported by the SDK)
- SiweExternal (Login with an external wallet that only supports web using a browser loading a static thirdweb React page temporarily)
Will instantiate InAppWalletModal
or resume the session - a simple prefab that will verify the user OTP.
Will instantiate InAppWalletModal
or resume the session - a simple prefab that will verify the user OTP.
Will open a native browser or oauth session to authenticate the user and redirect back to the game.
Will use a separate wallet to sign a message and login to the InAppWallet.
Will open a browser and load a static thirdweb React page to authenticate the user and redirect back to the game.
You can pass forceSiweExternalWalletIds
to force the page to use one or more wallets.
Example:
InAppWallets support linking multiple authentication methods to a single wallet, for instance linking Google to your Email-based In-App-Wallet. This is useful to have a unified identity across platforms.