General FAQs
Our thirdweb In-App Wallet is fully EVM compatible and supports all EVM chains.
No! Since our SDK provides the wallet signer
, you can build a unified experience with the same code to handle how all your users' wallets interact with signatures and smart contracts.
However, you will need to provide a separate flow to create in-app wallets as you would with any wallet provider (WalletConnect, Coinbase Wallet, etc.).
Make sure that you are developing on a secure origin, which includes localhost
and any site on https://
. thirdweb uses cryptography libraries that are unsupported on http://
.
If you continue to run into a console error, please contact us with more details.
thirdweb can create up to 300 wallets/second by default and can support higher limits (up to 3,000 wallets/second) upon request.
We support a lot of authentication options out of the box. For a full list, check out the playground. We also support custom authentication if you want to integrate thirdweb into your own auth system.
Yes, you can easily use account abstraction with in-app wallets to enable sponsored (gasless) transactions.
Thirdweb wallets can be used as a signer to a smart contract account (account abstraction), but it can also be used as a standalone EOA.
Is there a way to display the logged-in email address in the Connect component, similar to the wallet address?
Yes, we show the email by default in the details modal after you connect. To display the email anywhere else using React or React Native, check out the code snippets for all platforms.
In the event that thirdweb ceases to exist, we have committed to keeping our in-app wallet service running for a period of at least 12 months after the shutdown announcement. During this time users will be able to access their wallet and transfer their assets out, or export their private key which they can then import into a different client.
Currently, users will rely on the built-in recovery of their auth method. Refer to the How to recover your Google Account or Gmail article as an example for social and email auths.
Users can also link their account to a different auth method (e.g. email, phone, or social). All linked methods will be able to be used to access their accounts, providing an alternate recovery method in the case where one is lost.
Security FAQs
You can learn more about the architecture of how thirdweb wallets are created and stored here
Using enclave, your customers' assets are safe even if thirdweb or you are compromised. This is because the attacker will only be able to access the encrypted keys, and that is not enough to reconstruct the private key.