> For the complete documentation index, see [llms.txt](https://docs.tomo.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomo.inc/tomo-sdk/tomo-web-sdk/embedded-wallet-ui-component.md).

# Embedded Wallet (UI Component)

### What is the Tomo Embedded Wallet

Tomo Embedded Wallet offers seamless and visually engaging login experiences tailored for crypto-native users and easy onboarding for everyone else. Key features include:

* **Unified Account System**: Tomo provides a unified wallet for your social account. That is, if you log in to dApp A with your Gmail and buy X tokens, when you log in to dApp B, you can directly use the previously purchased token. This feature is the core of the Tomo wallet, allowing users to smoothly use their assets in one wallet with one social account.
* **Multi-Blockchain Support**: Tomo wallet supports most mainstream blockchains, including Bitcoin, Ethereum, Solana, etc. We support built-in swap functionalities between different on-chain assets, so users can easily invest in new assets within our embedded wallet.
* **Secure and Reliable**: We take security as our highest priority in wallet design. The embedded wallet stores your private key into a secure hardware wallet and dApp. The dApps will have no access to the user's private key, and only the user can authorize the transaction signing or private key exports through Multi-Factor Authorization (MFA)

<figure><img src="/files/7mkbrAJ4PkWGV850nuxr" alt=""><figcaption><p>Social Login</p></figcaption></figure>

With simplified developer tools and cryptographic security measures, Tomo embedded wallet is designed to provide user-friendly wallets while maintaining the highest security for web3 developers and users.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tomo.inc/tomo-sdk/tomo-web-sdk/embedded-wallet-ui-component.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.