Skip to content

Commit 2ff06e7

Browse files
Merge pull request #276 from sei-protocol/add_gw_faq
Add global wallets FAQ
2 parents 9371414 + 26bbd5a commit 2ff06e7

File tree

1 file changed

+113
-1
lines changed

1 file changed

+113
-1
lines changed

content/evm/sei-global-wallet.mdx

+113-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Integrating is straightforward for developers using EIP-6963-compatible wallets
2121
WalletConnectKit, or Dynamic. Our lightweight SDK allows to easily add Sei Global Wallet to your app with just a
2222
few lines of code.
2323

24-
### Benefits of the Sei
24+
### Benefits of the Sei Global Wallet
2525

2626
- Simplifies onboarding for users
2727
- Provides a seamless way for users to explore onchain apps without a browser extension or native app
@@ -196,6 +196,118 @@ Here are some examples of how to use Sei Global Wallet with some popular librari
196196
);
197197
```
198198

199+
## FAQ
200+
201+
### General
202+
203+
#### Q: What are Sei Global Wallets?
204+
205+
Sei Global Wallets are an embedded wallet experience for the Sei network, enabling wallet creation and authentication
206+
through social logins. Unlike traditional embedded wallets, Sei Global Wallets offer greater flexibility by allowing
207+
users to carry their wallets across different apps within the Sei ecosystem. They also enable Sei to integrate
208+
themselves as a login method across ecosystem apps.
209+
210+
#### Q: What are the key benefits of Sei Global Wallets for developers and users?
211+
212+
**For Developers:**
213+
- **Sei ecosystem front and center:** Developers can add Sei as a login method to their app ("Log in with Sei"),
214+
enhancing brand visibility and creating a unified user experience across the Sei ecosystem.
215+
- **Simple integration:** The Global Wallet Kit is compatible with tools like RainbowKit, ConnectKit, and Appkit,
216+
simplifying the process for developers to integrate Sei Global Wallets into their applications.
217+
- **Enhanced security:** The kit provides robust security features, including multi-factor authentication (MFA) and
218+
secure key management
219+
220+
**For Users**
221+
- **Simplified onboarding:** Users can create wallets and authenticate using familiar social logins, eliminating the
222+
need for browser extensions or prior crypto knowledge.
223+
- **Cross-app connectivity:** Users can navigate seamlessly across various applications within the Sei ecosystem using
224+
a single wallet, enhancing interoperability and user experience.
225+
- **User-friendly flows:** Features like transaction simulation help users understand the impact of each transaction
226+
before confirmation, reducing risks and enhancing transparency.
227+
228+
#### Q: What login methods are currently supported?
229+
230+
Sei Global Wallets support an extensive list of social logins, such as email, Google, X and Telegram.
231+
232+
#### Q: Do Sei Global Wallets conform to EIP standards?
233+
Yes, Sei Global Wallets conform to a specific EIP standard (EIP-6963) for injecting wallets, ensuring compatibility
234+
with aggregated wallet services like RainbowKit and ConnectKit.
235+
236+
#### Q: How do the security considerations of a Sei Global Wallet differ from traditional wallets?
237+
238+
Unlike traditional wallets, which often rely on client-side storage of private keys, Sei Global Wallets prioritize
239+
secure, encrypted interactions. Key differences include:
240+
241+
- **Secure encrypted communication:** All communication between an application and the Sei Global Wallet pop-up is
242+
encrypted, ensuring that there is no exposure of sensitive data during transmission. Decryption only happens within
243+
the wallet pop-up, and private keys are never exposed to the client or any external parties.
244+
- **Protection against replay attacks:** Sei Global Wallets implement encrypted messaging, eliminating opportunities for
245+
replay attacks. This means any intercepted data cannot be reused maliciously.
246+
- **Trusted Execution Environments (TEEs):** Encryption and decryption operations take place inside secure TEEs,
247+
preventing unauthorized access to sensitive material. Even Dynamic, as the wallet provider, does not have access to
248+
private keys, which remain secure within these isolated environments.
249+
- **Only verified origins allowed:** To further enhance security, only verified origins are allowed to interact with
250+
Sei Global Wallets. This ensures that all transactions and requests are made from trusted sources,
251+
252+
253+
In addition to these, Dynamic-powered embedded wallets share the same principles of non-custodial security, ensuring
254+
that only the user has access to their private keys. Dynamic’s multi-layered security architecture includes encrypted
255+
key storage, third-party audits, and ongoing bug bounty programs. Furthermore, wallets are always end-user controlled,
256+
with the option for users to export their private keys to a different provider at any time.
257+
258+
#### Q: Are Sei Global Wallets self-custodial or custodial?
259+
Sei Global Wallets and all Dynamic embedded wallets are self-custodial, giving full control and ownership to the
260+
end-user. An end user can export their keys at any time and import them into a MetaMask or other external wallet.
261+
262+
#### Q: Do Sei Global Wallets require browser extensions?
263+
No, they do not require browser extensions. They function as an embedded wallet that can be taken across the Sei
264+
ecosystem.
265+
266+
#### Q: Can I link my existing external wallet to my Sei Global Wallet?
267+
Not at the moment. In the future you will be able to link external wallets to a Sei global account.
268+
269+
#### Q: Can I put extra protections on my Sei Global Wallet?
270+
While Global Wallets are self-custodial, we always recommend practicing good security hygiene. Here are some ways to
271+
add additional protections:
272+
273+
- **Enable multi-factor authentication (MFA):** Adding an extra authentication layer for sensitive actions can further
274+
secure your account.
275+
- **Be cautious of phishing attempts:** Stay alert when entering security codes online, especially if prompted
276+
unexpectedly. Always verify the source before sharing any sensitive information or interacting with unfamiliar requests.
277+
- **Add additional backup options:** Link additional email or social login methods to your account. This ensures you’ll
278+
always have a way to recover access, even if your primary login method becomes unavailable.
279+
280+
#### Q: Have Sei Global Wallets been audited?
281+
Yes, Sei Global Wallets, built by Dynamic, have been independently audited by Cure53, a leading security firm.
282+
The audit included a comprehensive review of Dynamic’s SDK, backend, and dashboard, with a specific focus on
283+
cryptographic implementations. The auditors concluded that the codebase demonstrates a strong security posture,
284+
modern architecture, and effective protection against common vulnerabilities such as XSS and SQL injection.
285+
286+
#### Q: A user or developer has reported a bug, such as a UI issue. How should they report it?
287+
288+
The person reporting should provide this info:
289+
- Device
290+
- Browser
291+
- Description of the issue
292+
- If possible, a Loom or screen recording
293+
294+
### Integration and Access
295+
296+
#### Q: How can developers using RainbowKit or WalletConnect integrate Sei Global Wallets into their application?
297+
298+
Developers using RainbowKit or WalletConnect can integrate Sei Global Wallets by installing and importing the
299+
Sei Global Wallet. See full docs [here](#library-specific-examples).
300+
301+
#### Q: How can RainbowKit and WalletConnect developers make their Sei Global Wallet a recommended wallet?
302+
You can follow the walkthrough in [Dynamic's docs to guide](https://docs.dynamic.xyz/global-wallets/web3-libraries)
303+
your partners to add Sei Global Wallet as a recommended
304+
wallet in their app.
305+
306+
#### Q: What should developers do if they have filtering issues with their wallet list?
307+
If Sei Global Wallets do not appear in a developer’s wallet list, they should check whether they have applied a custom
308+
filter that might exclude it. Some wallet providers allow developers to modify which wallets are displayed, which could
309+
cause integration issues.
310+
199311
## References and links
200312

201313
- [<ins>Dynamic Global Wallet Documentation</ins>](https://docs.dynamic.xyz/global-wallets/overview)

0 commit comments

Comments
 (0)