Wallets FAQ

View all the supported chains for wallets on thirdweb chainlist.

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.

Yes, you can easily use account abstraction with in-app wallets to enable sponsored (gasless) transactions. Learn more in our sponsor gas guide.

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.

For a full list of supported authenticated options, we recommending searching the playground. Wallets also supports custom authentication if you want to integrate thirdweb into your own auth system.

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.

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.).

Yes, you can change your Ecosystem Wallet name and icon. However, you cannot change the Ecosystem Wallet slug.

No, the Dedicated Relayer service is an add-on service. View more information on the different tiers on the pricing page.

A single executor will lead to about 20% faster queue to confirmation times and 15% higher throughput.

The premium tier with ten executors instead of one will improve this by 10x.

Our dedicated relayer gives you your very own queue. It is also built for 7702 - meaning both user and server wallets can use it without any code changes and msg.sender still remains as the user.

This is in contrast with an EIP-2771 relayer which requires contract changes.

Dedicated relayer also gives you easier analytics for Dune dashboards and more by just fetching all transactions originating from dedicated executors.

Yes, scaling is managed. You can choose the number of executors and chains through the different standard, premium, or custom tiers.

Infrastructure and automatic funding is already managed by thirdweb.

This depends on the chain stability and features but typically ten executors can handle around 100 TPS.

Learn more about the architecture of how thirdweb wallets are created and stored in the security docs..

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.

Learn how to export the private key for a thirdweb wallet using the Connect modal.

In the event that thirdweb ceases to exist, we have committed to keeping our user 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.