> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/hemera-indexer/use-cases/deposit/data-class.md).

# Data Class

There are two data classes specifically for `deposit_to_l2_job`, representing:

1. `TokenDepositTransaction`: Transaction details of deposit operations
2. `AddressTokenDeposit`: Aggregated snapshot values of deposit operations across designed dimensions

**TokenDepositTransaction**

| Column Name       | Data Type | Note                                                               |
| ----------------- | --------- | ------------------------------------------------------------------ |
| transaction\_hash | str       | Primary key, hash of the transaction.                              |
| wallet\_address   | str       | Address that initiated the wallet.                                 |
| chain\_id         | int       | pecifies the L2 chain to which the deposit operation is directed.  |
| contract\_address | str       | Represents the contract which user makes deposit operations to L2. |
| token\_address    | str       | The token used in this deposit operation.                          |
| value             | int       | Represents the amount of tokens in this deposit transaction.       |
| block\_number     | int       | Number of the block containing the transaction.                    |
| block\_timestamp  | int       | Timestamp of when the block was mined.                             |

**AddressTokenDeposit**

| Column Name       | Data Type | Note                                                                                                                   |
| ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------- |
| wallet\_address   | str       | Primary key, address that initiated the wallet.                                                                        |
| chain\_id         | int       | Primary key, pecifies the L2 chain to which the deposit operation is directed.                                         |
| contract\_address | str       | Primary key, represents the contract which user makes deposit operations to L2.                                        |
| token\_address    | str       | Primary key, the token used for deposits through this contract.                                                        |
| value             | int       | Represents the total amount of tokens deposited on the specific L2 chain through this contract up to the current time. |
| block\_number     | int       | The block number of which included the last deposit transaction.                                                       |
| block\_timestamp  | timestamp | The block timestamp of when the block was mined.                                                                       |


---

# 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.thehemera.com/hemera-indexer/use-cases/deposit/data-class.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.