> ## Documentation Index
> Fetch the complete documentation index at: https://manuals.cobo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an MPC Wallet 

> Step-by-step guide to creating an MPC Wallet within your vault on Cobo Portal.

## Prerequisites

You have been assigned the [user role](/en/portal/organization/roles-and-permissions) of Operator, Manager, or Admin.

## Steps

1. Log in to [Cobo Portal](https://portal.cobo.com/login).
2. Click **Wallets** in the left sidebar, then select **MPC Wallets**.
3. Select the vault that you created in [Create an MPC vault](/en/portal/mpc-wallets/ocw/create-mpc-vault).
4. Click **Create Wallet**.
5. Name your wallet, then click **Create**.

Now you have created an MPC Wallet.

## Next steps

After creating a wallet, you can:

* Wallets
  * View the transaction history of the wallet.
  * Edit the wallet name.

* Tokens
  * Add token types to your wallet. If you can't find the token you're looking for, you can [request token self-listing](/en/portal/self-service-token-listing).
  * Deposit tokens to the wallet.
  * Withdraw tokens from the wallet.
  * View the transaction history related to the token in the wallet.
  * View the deposit addresses of the token.
  * Search, filter, and sort tokens in the wallet.

* Addresses
  * Generate a unique wallet address.
  * Deposit or withdraw from the address.
  * View the transaction history of the address.
  * Edit the address label.
  * Search, filter, and sort addresses in the wallet.

<Note>
  MPC Wallets use the same address across all supported EVM chains. You only need to create it once. Existing addresses on one EVM chain will automatically work on all other supported EVM chains.

  Currently, query results for EVM chain addresses differ between interfaces:

  * [API](https://www.cobo.com/developers/v2/api-references/wallets/list-wallet-addresses): Query results are limited by chain\_id, so only addresses from that specific chain are returned.
  * Cobo Portal: Displays addresses from all supported EVM chains, so the number of addresses may be larger than the API results.
</Note>