This section is about bridge transactions in layerzero. To reach the standard of bridge tables, 2 tables in the aptos database, a table from crosschain database for prices and a table entered manually using the layerzero documentation have been used.

aptos.core.fact_transactions: to check transactions

aptos.core.dim_tokens: to get the decimals and name of each token

chain_id: to match the chain ID in the transaction table and the chain ID obtained from the documentation of the layerzero site to understand the chain name.

Prices: To match the names of the tokens and get the price of each token in the hour when the transaction is done.

The price of the tokens is obtained from the Ethereum network.

The information related to token volume, destination chain, destination wallet address, bridge contract address and bridged token address is extracted from the payload section. The tree diagram of layerzero bridge data structure is shown in this column. The first part of the payload is related to the arguments that are inserted as an array. The first index (index[0]) of this array is the destination chain id, the second index (index[1]) is the wallet address in the destination chain, and the third index (index[2]) is the raw amount of the token. The rest of the indexes in this section do not help to insert bridge data.

The second part is called function, where the bridge address contract and the operation performed in this contract are located. Its structure is as follows: bridge contract address::function

The fourth part is type arguments. In the layerzero bridge, this array does not have one more argument, and that is the address of the bridged token.

layerzero chain documentation: -- resource: https://layerzero.gitbook.io/docs/technical-reference/mainnet/supported-chain-ids

• bloc_number: block number
• block_timestamp: timestamp of transaction
• tx_hash: transaction hash
• payload: raw datas about transaction
• bridge address: bridge platform address
• function: bridge function
• event_name: bridge event name
• platform: brodge platform name
• sender: source wallet address
• destination_chain_receiver: destination chain wallet address
• destination_chain: destination chain name
• destination_chain_id: destination chain id
• token_address: address of token bridged
• token_symbol: symbol of the token
• token_name: name of the token
• amount_unadj: raw token amount
• amount: token amount
• amount_usd: token amount in USD