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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://developers.fireblocks.com/feedback

```json
{
  "path": "/docs/embedded-wallet-wallet",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Wallet

<Note>
  For Fireblocks' recommended embedded wallet solution, see [Dynamic Embedded Wallets](/docs/dynamic-embedded-wallets). The documentation below covers the legacy Embedded Wallet APIs and SDKs.
</Note>

# Overview

A wallet is an object you manage on Fireblocks' servers for your end-users. Wallets can have multiple keys (ECDSA and [EdDSA](https://ncw-developers.fireblocks.com/docs/multiple-algorithms)) and an unlimited number of wallet accounts. Each wallet account has a single asset type under it. For instance:

* `walletId-1`

  * `walletAccount-1`

    * `BTC`
    * `ETH`

  * `walletAccount-2`

    * `FTM`
    * `TRON`

In the new architecture wallet creation is done automatically (if needed) as part of the `assignWallet()` EW SDK method.

## Multiple wallets and wallet accounts

Theoretically, your end-user can have multiple wallets, but that does not matter in the Fireblocks view since Fireblocks does not hold any personally identifiable information (PII) about your end-users. However, for simplicity in our demos, we assume a one-to-one relationship between an end-user and a wallet.