Skip to content

Commit c5cff26

Browse files
pinkhoodiepinkhoodie
authored
Docs Revisions: In-app & ecosystem wallet FAQs page, Pay -> Univ Bridge, Wallets Get Started (#6494)
Signed-off-by: pink hoodie. <[email protected]>
1 parent 7890145 commit c5cff26

File tree

9 files changed

+800
-77
lines changed

9 files changed

+800
-77
lines changed

‎apps/portal/src/app/connect/pay/get-started/page.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Log in to [the thirdweb dashboard](https://thirdweb.com/team). Navigate to the *
4646

4747
## Option 1: ConnectButton
4848

49-
Pay is available by default with our `ConnectButton` component. When users log in with Connect, they'll be able to onramp and purchase crypto directly from the logged in Connect interface. You can read more about `ConnectButton` [in this guide](/connect/sign-in/ConnectButton).
49+
Universal Bridge is available by default with our `ConnectButton` component. When users log in with Connect, they'll be able to onramp and purchase crypto directly from the logged in Connect interface. You can read more about `ConnectButton` [in this guide](/connect/sign-in/ConnectButton).
5050

5151
```tsx
5252
import { ThirdwebProvider, ConnectButton } from "thirdweb/react";

‎apps/portal/src/app/connect/pay/testing-pay/page.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ import { createMetadata, Callout } from "@doc";
33

44
export const metadata = createMetadata({
55
image: {
6-
title: "thirdweb Pay - Test Mode",
6+
title: "thirdweb Universal Bridge - Test Mode",
77
icon: "thirdweb",
88
},
99
title: "Enable Test Mode for Universal bridge — thirdweb docs",

‎apps/portal/src/app/connect/sidebar.tsx

+8
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,10 @@ export const sidebar: SideBar = {
7575
name: "Guest Mode",
7676
href: `${walletSlug}/sign-in-methods/guest`,
7777
},
78+
{
79+
name: "FAQ",
80+
href: `${walletSlug}/in-app-wallet/faq`,
81+
},
7882
{
7983
name: "Custom Authentication",
8084
links: [
@@ -130,6 +134,10 @@ export const sidebar: SideBar = {
130134
name: "Register with WalletConnect",
131135
href: `${walletSlug}/ecosystem/register-walletconnect`,
132136
},
137+
{
138+
name: "FAQ",
139+
href: `${walletSlug}/ecosystem/faq`,
140+
},
133141
],
134142
},
135143
//Account abstraction

‎apps/portal/src/app/connect/wallet/ecosystem/faq/page.mdx

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
import { createMetadata } from "@doc";
2+
3+
export const metadata = createMetadata({
4+
title: "Ecosystem Wallet FAQs",
5+
description: "Frequently asked questions about thirdweb's Ecosystem Wallet",
6+
image: {
7+
title: "FAQs for thirdweb Ecosystem Wallet",
8+
icon: "wallets",
9+
},
10+
});
11+
12+
# Ecosystem Wallet FAQs
13+
14+
### What is an Ecosystem Wallet?
15+
16+
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.
17+
18+
### How do Ecosystem Wallets work?
19+
20+
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.
21+
22+
### What is an Ecosystem Partner?
23+
24+
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.
25+
26+
You can manage ecosystem partners in the Permissions tab of your Ecosystem Wallet dashboard.
27+
28+
### Which login providers can display my Ecosystem Wallet?
29+
30+
thirdweb Connect, with WalletConnect and any wagmi- or viem-based login providers coming soon.
31+
32+
### How can Partners integrate my Ecosystem Wallet?
33+
34+
Partners can integrate your Ecosystem Wallet in three different ways:
35+
36+
**Login System**
37+
38+
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.
39+
40+
**Branded Wallet Connector**
41+
42+
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.
43+
44+
**WalletConnect (Coming Soon)**
45+
46+
Partners using WalletConnect will automatically display your wallet as a WalletConnect option on any domains they've whitelisted.
47+
48+
### What is the difference between Anyone and Allowlist scopes for Ecosystem Wallet?
49+
50+
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.
51+
52+
The **Allowlist** scope allows developers that you have explicitly added to your list of Partners to display your wallet as a login option.
53+
54+
You can manage scope in the Permissions tab of your Ecosystem Wallet dashboard.
55+
56+
### How does billing work for Ecosystem Wallets?
57+
58+
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.

‎apps/portal/src/app/connect/wallet/faq/page.mdx

-57
Original file line numberDiff line numberDiff line change
@@ -57,63 +57,6 @@ Currently, users will rely on the built-in recovery of their auth method. Refer
5757

5858
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.
5959

60-
# In App Wallet FAQs
61-
62-
### How do users connect to their in-app wallet in a third-party app?
63-
64-
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.
65-
66-
### How is pricing calculated for in-app wallets?
67-
68-
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.
69-
70-
# Ecosystem Wallet FAQs
71-
72-
### What is an Ecosystem Wallet?
73-
74-
An ecosystem wallet is a managed in-app wallet service that allows you to create a branded wallet and login system, manage your 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.
75-
76-
### How do Ecosystem Wallets work?
77-
78-
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.
79-
80-
### What is an Ecosystem Partner?
81-
82-
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.
83-
84-
You can manage ecosystem partners in the Permissions tab of your Ecosystem Wallet dashboard.
85-
86-
### Which login providers can display my Ecosystem Wallet?
87-
88-
thirdweb Connect, with WalletConnect and any wagmi- or viem-based login providers coming soon.
89-
90-
### How can Partners integrate my Ecosystem Wallet?
91-
92-
Partners can integrate your Ecosystem Wallet in three different ways:
93-
94-
**Login System**
95-
96-
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.
97-
98-
**Branded Wallet Connector**
99-
100-
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.
101-
102-
**WalletConnect (Coming Soon)**
103-
104-
Partners using WalletConnect will automatically display your wallet as a WalletConnect option on any domains they've whitelisted.
105-
106-
### What is the difference between Anyone and Allowlist scopes for Ecosystem Wallet?
107-
108-
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.
109-
110-
The **Allowlist** scope allows developers that you have explicitly added to your list of Partners to display your wallet as a login option.
111-
112-
You can manage scope in the Permissions tab of your Ecosystem Wallet dashboard.
113-
114-
### How does billing work for Ecosystem Wallets?
115-
116-
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.
11760

11861
# Security FAQs
11962

0 commit comments

Comments
 (0)