Docs Revisions: In-app & ecosystem wallet FAQs page, Pay -> Univ Bridge, Wallets Get Started #6494
+800
−77
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,58 @@ | ||||||
| import { createMetadata } from "@doc"; | ||||||
|
|
||||||
| export const metadata = createMetadata({ | ||||||
| title: "Ecosystem Wallet FAQs", | ||||||
| description: "Frequently asked questions about thirdweb's Ecosystem Wallet", | ||||||
| image: { | ||||||
| title: "FAQs for thirdweb Ecosystem Wallet", | ||||||
| icon: "wallets", | ||||||
| }, | ||||||
| }); | ||||||
|
|
||||||
| # Ecosystem Wallet FAQs | ||||||
|
|
||||||
| ### What is an Ecosystem Wallet? | ||||||
|
|
||||||
| An ecosystem wallet is a managed in-app wallet service that allows platforms to create a branded wallet and login system, manage their partners, and allow any number of partners to spin up in-app wallets. End users that create in-app wallets through your partner applications (either with email, phone number, passkey, or socials) will receive **one account and wallet address** that they can access across the entire ecosystem. | ||||||
|
|
||||||
| ### How do Ecosystem Wallets work? | ||||||
|
|
||||||
| Ecosystem Wallets are a fully managed and containerized in-app wallet backend service that is white labeled to your application. By giving you access to this backend service, you can power any application with in-app wallets just like thirdweb does for over 70,000 developers. | ||||||
|
|
||||||
| ### What is an Ecosystem Partner? | ||||||
|
|
||||||
| Ecosystem partners are games or applications that you have permissioned to spin up in-app wallets underneath your brand. They will have access to the same account (funds, assets, etc.) for any end users that 1) use your branded login system or 2) log in with your wallet. | ||||||
|
|
||||||
| You can manage ecosystem partners in the Permissions tab of your Ecosystem Wallet dashboard. | ||||||
|
|
||||||
| ### Which login providers can display my Ecosystem Wallet? | ||||||
|
|
||||||
| thirdweb Connect, with WalletConnect and any wagmi- or viem-based login providers coming soon. | ||||||
|
|
||||||
| ### How can Partners integrate my Ecosystem Wallet? | ||||||
|
|
||||||
| Partners can integrate your Ecosystem Wallet in three different ways: | ||||||
|
|
||||||
| **Login System** | ||||||
|
|
||||||
| Partners can install thirdweb SDK and use the Partner ID you created for them to display your branded sign in flow. All login options in this sign in flow will create an in-app wallet. | ||||||
|
|
||||||
| **Branded Wallet Connector** | ||||||
|
|
||||||
| Partners can add your wallet as a wallet connector option in their existing sign in flow on any domains they've whitelisted by calling the follow endpoint from their application. | ||||||
|
There was a problem hiding this comment. There appears to be a small typo in this sentence. "calling the follow endpoint" should be "calling the following endpoint" to maintain proper grammar.
Suggested change
Spotted by Diamond |
||||||
|
|
||||||
| **WalletConnect (Coming Soon)** | ||||||
|
|
||||||
| Partners using WalletConnect will automatically display your wallet as a WalletConnect option on any domains they've whitelisted. | ||||||
|
|
||||||
| ### What is the difference between Anyone and Allowlist scopes for Ecosystem Wallet? | ||||||
|
|
||||||
| The **Anyone** scope allows any developer to integrate your ecosystem wallet, even if you have not given them permission. Any developer with thirdweb Connect, for example, would now display your wallet as a login option. | ||||||
|
|
||||||
| The **Allowlist** scope allows developers that you have explicitly added to your list of Partners to display your wallet as a login option. | ||||||
|
|
||||||
| You can manage scope in the Permissions tab of your Ecosystem Wallet dashboard. | ||||||
|
|
||||||
| ### How does billing work for Ecosystem Wallets? | ||||||
|
|
||||||
| As the ecosystem admin, you will be billed $250 monthly for your Ecosystem Wallet. This allows any application or game in your ecosystem generate in-app wallets. Each month, we allow you and your ecosystem partners to generate 30,000 wallets for free. Once you've generated 30,000 wallets, you will be charged $0.02 per in-app wallet. At the end of each month, we will provide you with an invoice with a usage breakdown across all partners. | ||||||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| import { createMetadata } from "@doc"; | ||
|
|
||
| export const metadata = createMetadata({ | ||
| title: "In-App Wallet FAQs", | ||
| description: "Frequently asked questions about thirdweb's In-App Wallet", | ||
| image: { | ||
| title: "FAQs for thirdweb In-App Wallet", | ||
| icon: "wallets", | ||
| }, | ||
| }); | ||
|
|
||
| # In-App Wallet FAQs | ||
|
|
||
| ### How do users connect to their in-app wallet in a third-party app? | ||
|
|
||
| Users can access it by doing a manual connection via wallet connect. They will then have to use the connect button or embed and select manage wallet -> connect an App. | ||
|
|
||
| ### How is pricing calculated for in-app wallets? | ||
|
|
||
| In-app wallets are billed based on "monthly active wallets". An active wallet is defined as a wallet where a user logs in during the billing period. In-app wallets are completely free up to 1,000 monthly active wallets, and $0.02 per wallet after that. | ||
|
|
||
| ### What security measures should users take when connecting their in-app wallet? | ||
|
|
||
| Users should always verify they are connecting to legitimate websites by checking the URL carefully. Never connect to unverified or suspicious websites. The connection process should only be initiated through the official WalletConnect interface or trusted dApp integrations. | ||
|
|
||
| ### Can developers integrate both in-app wallets and external wallets in the same application? | ||
|
|
||
| Yes, developers can build a unified experience that supports both in-app wallets and external wallets (like MetaMask) using the same code base. The SDK provides a wallet signer that handles how all wallet types interact with signatures and smart contracts consistently, though the initial connection flow will differ by wallet type. | ||
|
|
||
| ### What blockchain networks are supported for in-app wallet connections? | ||
|
|
||
| In-app wallets are fully EVM (Ethereum Virtual Machine) compatible and support all EVM chains. This includes major networks like Ethereum Mainnet, Polygon, Optimism, Base, and other EVM-compatible blockchains. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The capitalization of "Universal bridge" should be standardized to "Universal Bridge" to maintain consistent capitalization throughout the documentation. This inconsistency appears only in this title while other instances use the proper capitalization format.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.