Hemera Doc
  • 👋Welcome
    • Introduction
    • Quick Start
    • Account Centric Indexing Protocol
      • What is Account-Centric Indexing?
      • Why "account-centric" indexing?
      • The advantages of Account-Centric Indexing
      • What's next for account-centric indexing?
      • Why create a new protocol here?
      • The Hemera Network
        • Network Roles
        • Indexers
        • Validators
        • Proprietary models & knowledge
        • Proprietary data and labels
        • Smart Contracts
        • Key roadmap items
        • Supported blockchains
      • Example Hemera use cases
        • SocialScan Explorers
        • Anti-sybil UML algorithm
        • Ethereum long term DA
        • EVM chain history preservation
        • Ecosystem AI Agents
        • User-defined AI Agents
  • 👩‍💻Developer Resources
    • Smart Contract Developers
    • EVM-compatible chains
      • Blockchain explorers
      • SocialScan explorer API doc
      • Ecosystem AI Agents
    • Dapp developers
    • User-defined Agent creators
    • AVS Operator
  • 🖥️Hemera Indexer
    • Introduction
    • Installation
      • Prerequisites
      • Install & Run
      • Export Result
    • Configurations
    • Benchmark
    • Data Class
      • Raw Data Tables
        • Blocks
        • Transactions
        • Logs
        • Traces
      • Generated Tables
        • Contract Internal Transactions
        • ERC20 Token Transfers
        • Tokens
        • ERC20 Token Holders
        • ERC721 Token Transfers
        • ERC721 Token Holders
        • ERC1155 Token Transfers
        • ERC1155 Token Holders
        • Address Coin Balances
        • Address Token Balances
        • Address Current Token Balances
        • Daily Wallet Address Stats
        • Contracts
      • Other Tables
        • Inscriptions
        • Bridges
          • L1 to L2 Transactions
          • L2 to L1 Transactions
          • Optimistic Rollup Data Availability Batches
          • Optimistic Rollup State Batches
    • Use Cases
      • UniSwap V3
        • Data Class
        • Trigger and Function
        • Run & Query
      • ENS
        • Data Class
        • Trigger and Function
        • Run & Query
      • OpenSea
        • Data Class
        • Trigger and Function
        • Run & Query
      • Deposit to L2
        • Data Class
        • Trigger and Function
        • Run & Query
      • User Profile
  • UDFs - User Defined Functions
    • Introduction
    • Components of UDFs
    • Building User Defined Functions(UDF)
    • Testing and Running UDF
    • Troubleshooting and Support
    • Supported UDFs
    • FAQs
  • 😄About us
    • The story behind building Hemera
    • Partners & Backers
    • Partnership inquiries
    • Hemera Powered Explorers
    • Active Developer Hackathons
    • Developer Contribution
  • Documentation feedback
Powered by GitBook
On this page
  1. Hemera Indexer
  2. Use Cases
  3. Deposit to L2

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.

PreviousDeposit to L2NextTrigger and Function

Last updated 8 months ago

🖥️