> For the complete documentation index, see [llms.txt](https://mission-doc.ultiverse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mission-doc.ultiverse.io/concept/wallet.md). # Wallet Two types of wallets are associated with an Ultiverse account: * Game Wallet * Asset Wallet ## Game Wallet: After registering an Ultiverse account, Ultiverse will automatically generate a [Particle wallet ](https://particle.network/)for you as a game wallet. {% hint style="danger" %} Game wallet is an MPC wallet, Ultiverse does not have any way to get the user's private key. {% endhint %} Currently, an Ultiverse account can only have one game wallet. The game wallet is the primary wallet for users to interact with various Ultiverse gaming products, including game interactions and airdrop rewards. The game wallet is multi-chain supported, and you can interact with different chains through the same address game wallet in the game. Currently supported chains: * Ethereum * BNB Chain ## Asset Wallet Ultiverse is an open metaverse platform, and many assets outside the Ultiverse ecosystem can be widely used in Ultiverse. Users can bind an asset wallet to prove asset ownership. The asset wallet can establish a relationship between your on-chain assets and your Ultiverse account. Ultiverse will grant you different rights and bonuses in Ultiverse products based on the on-chain assets you hold. A typical scenario is when you bind your Ethereum wallet. If your wallet has an Electric Sheep NFT, you will have more rights and bonuses in Ultiverse products compared to other accounts. The asset wallet also supports multi-chain binding, and you can bind different asset wallets in your Ultiverse account according to your needs. Currently supported chains: * Ethereum * BNB Chain --- # 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://mission-doc.ultiverse.io/concept/wallet.md?ask=&goal= ``` `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.