> ## 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/data-model",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# Data Model

<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

Fireblocks end user wallets (EUWs) are hierarchical deterministic (HD) wallets. With our REST API, customers can easily create new wallets for their end users and add multiple accounts under them. Each account can contain different assets, and all transactions are signed using the end-user key generated for a specific wallet.

# Data Model

<img src="https://mintcdn.com/fireblocks-43c4b3ee/8uV7V_rBjqF0ZDAg/images/docs/a6ef7c0-Data_Model.png?fit=max&auto=format&n=8uV7V_rBjqF0ZDAg&q=85&s=6b80d0c19ef3eb1aab68dafe60a4c80e" alt="" width="800" height="596" data-path="images/docs/a6ef7c0-Data_Model.png" />

* **User:** Represents the end user of your application. Kindly note that this entity is external to Fireblocks and is reflected only on the customer's side.
* **Device:** A logical identifier representing an entity that stores an end-user key share and can participate in MPC operations for a given wallet.
* **Wallet:** Represents an end user wallet created via the Fireblocks API.
* **Transaction:** Represents the transactions created in Fireblocks.
* **Account:** Represents the different accounts under a single end user wallet.
* **Asset:** Represents the different assets under a single account.

# Relationships

* User > Device: **One to Many** relation
* Wallet > Device: **One to Many** relation
* Wallet > Account: **One to Many** relation
* Wallet > Transaction: **Many to Many** relation
* Device > Message: **One to Many** relation
* Account > Asset: **One to Many** relation

<Info>
  ### Device ID and wallet correlation

  Each user can have multiple `deviceId` values, each correlating to a different end user wallet in Fireblocks. Each `deviceId` represents an entity that stores an end-user key share.
</Info>