Evmos

Chain ID: evmos

For Evmos you'll find the following tables:

1. Raw Tables (Cosmos)

2. Filtered Tables (Cosmos)

   1. Staking

   2. IBC

   3. Liquidity Pools

   4. Governance

   5. Distribution

3. Additional Data Tables (Cosmos)

4. Raw Tables (EVM)

5. Aggregated Tables (EVM)

Working with Numia's Evmos Dataset

Quick tutorial on how to use Big Query to access Numia's Evmos Dataset

Evmos is the team behind the leading EVM Module Ethermint, and they were the first EVM-based chain in Cosmos. Because of its nature, Evmos consists of two layers when it comes to consensus and transactions, 1) the EVM layer runs the Ethereum virtual machine, and 2) the Cosmos layer which runs on the Cosmos-SDK and Tendermint. They both have different data models and it's important that you understand both data models so that you know what data to query to extract the data you need.

Cosmos Data Model

The Cosmos layer tracks every single transaction of the chain, including all Cosmos-SDK modules like DElegations, Governance, Banks,s and others. It also contains the wrapped EVM transactions, but these need to be decoded in order for them to be consumable.

Evmos EVM Data Model

In essence, EVM transactions take place and then get wrapped and passed to the Cosmos layer so these get validated there too. However not all EVM data is passed or if it is, it's still encoded.

Numia is the only indexer that provides indexing solutions for both layers at the time. You will be able to run queries to not only understand what's happening at the Cosmos layer but also at the EVM layer. Keep in mind we are gradually expanding to more and more tables in the coming weeks.

Evmos Message Types

Before you start querying the data you need to know what data you want to extract. Remember the whole data schema for Cosmos is based on different message types. We have created this extensive overview for all evmos message types that will allow you to know what events and what attributes correspond to different messages. Click here to access the document.

Raw Tables (Cosmos)

evmos_blocks

Contains each validated block in the Cosmos Layer of Evmos. block_timestamp. is only available in this table, so you need to do an inner join on block_height to get block_timestamp to the other tables.

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
chain_id	STRING
proposer_address	STRING
validators_hash	STRING

evmos_event_attributes

Contains all events and their corresponding attributes partitioned by tx_id. Events and their corresponding event_index are relative to the parent transaction , not the message. Events are identified by the event_type column and attributes by the attribute_key. Events are linked to transactions via column tx_id.

Field	Type
block_height	INTEGER
chain_id	STRING
tx_id	STRING
event_index	INTEGER
event_type	STRING
attribute_key	STRING
attribute_value	STRING
attribute_index	INTEGER
ingestion_timestamp	TIMESTAMP

evmos_message_event_attributes

Contains all events and their corresponding attributes partitioned by message_index. Events and their corresponding event_index are relative to the parent message_index which is relative to the tx_id. Events are identified by the event_type column and attributes by the attribute_key. Events are linked to transactions via column tx_id.

Field	Type
block_height	STRING
chain_id	STRING
tx_id	STRING
message_index	INTEGER
event_index	INTEGER
event_type	STRING
attribute_key	STRING
attribute_value	STRING
attribute_index	INTEGER
ingestion_timestamp	TIMESTAMP

evmos_transactions

Contains relevant data associated with a transaction.

Field	Type
block_height	STRING
chain_id	STRING
tx_id	STRING
tx_status	STRING
fee	STRING
tx_code	INTEGER
tx_index	INTEGER
gas_used	INTEGER
gas_wanted	INTEGER
ingestion_timestamp	TIMESTAMP

Filtered Event-Based Tables (Cosmos)

Beyond the raw tables, we have sub-tables for different relevant types of events, such as delegations, redelegations, swaps & voting. You can find them in their respective area (delegations in staking, swaps in liquidity pools, etc.)

Staking Tables

evmos_delegate

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
validator	STRING
moniker	STRING
delegator	STRING
parsed_EVMOS_amount	FLOAT64
new_shares	STRING
ingestion_timestamp	TIMESTAMP

evmos_redelegate

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
source_validator	STRING
source_moniker	STRING
destination_validator	STRING
destination_moniker	STRING
delegator	STRING
evmos_amount	BIGNUMERIC
new_shares	STRING
ingestion_timestamp	TIMESTAMP

evmos_undelegate

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
validator	STRING
moniker	STRING
delegator	STRING
evmos_amount	BIGNUMERIC
new_shares	STRING
ingestion_timestamp	TIMESTAMP

IBC Tables

evmos_ibc_transfer

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
packet_src_channel	STRING
packet_dts_channel	STRING
packet_connection	STRING
sender	STRING
receiver	STRING
amount	FLOAT64
token_path	STRING
token_alias	STRING
token_denom	STRING
ingestion_timestamp	TIMESTAMP

evmos_ibc_receive

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
packet_src_channel	STRING
packet_dts_channel	STRING
packet_connection	STRING
sender	STRING
receiver	STRING
amount	FLOAT64
token_path	STRING
token_alias	STRING
token_denom	STRING
ingestion_timestamp	TIMESTAMP

Liquidity Pools Tables

evmos_join_pool

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
sender	STRING
pool_id	STRING
tokens_in	STRING
ingestion_timestamp	TIMESTAMP

evmos_exit_pool

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
sender	STRING
pool_id	STRING
tokens_out	STRING
ingestion_timestamp	TIMESTAMP

evmos_swaps

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
event_index	INTEGER
sender	STRING
pool_id	STRING
amount_in	BIGNUMERIC
parsed_amount_in	FLOAT64
denom_in	STRING
native_denom_in	STRING
amount_out	BIGNUMERIC
parsed_amount_out	FLOAT64
denom_out	STRING
native_denom_out	STRING
ingestion_timestamp	TIMESTAMP

Governance Tables

evmos_voting

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
voter	STRING
proposal_id	STRING
proposal_option	STRING
ingestion_timestamp	TIMESTAMP

Distribution Tables

evmos_withdraw_rewards

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
validator	STRING
moniker	STRING
receiver	STRING
token_amount	FLOAT64
token_amount_in_usdc	FLOAT64
token_denom	STRING
ingestion_timestamp	TIMESTAMP

evmos_withdraw_commissions

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
tx_id	STRING
message_index	INTEGER
nth_action	INTEGER
validator	STRING
moniker	STRING
token_amount	FLOAT64
token_amount_in_usdc	FLOAT64
token_denom	STRING
ingestion_timestamp	TIMESTAMP

Additional Data Tables (Cosmos)

Additional tables have data that is not event based but relevant when working with event based data.

validators

Purpose: This table maps validator addresses to moniker & other metadata.

Field	Type
account_address	STRING
operator_address	STRING
consensus_pubkey	STRING
status	FLOAT
moniker	STRING
identity	STRING
rate	STRING
max_rate	FLOAT
min_self_delegation	FLOAT
Network	STRING
Snapshot_date	TIMESTAMP

message_types_transactions

Each record is a single message triggered within the chain. We include it's type, sender and the corresponding tx_id.

Raw Tables (EVM)

evm_blocks

Evm Blocks

Field	Description
height	block height (Integer)
timestamp	block timestamp (timestamp)
hash	block hash (string)
ingestion_timestamp	time record was ingested (timestamp)

evm_transactions

A table containing high-level data about the evm transactions.

Field	Description
block_height	block of the txn
hash_evm	hash of the evm txn
evm_index	index of txn within evm block
gas_used	amount of gas used in aevmos
amount	amount of evmos value in txn
sender	bech32 address of the sender
evm_sender	HEX address of the sender
recipient	HEX address of recipient
code	txn status code, 0 = success.
data	data of the txn is nullified and put into evm_logs
index	index of the txn in Cosmso block
gas_limit	gas limit
tx_json	json of the txn - nullified and put in evm_logs
ingestion_timestamp	ingestion timestamp in Numia
MsgEthereumTx	Txn data if txn of type MsgEthereumTx
LegacyTx	Txn data if txn of type LegacyTx
AccessListTx	Txn data if txn of type AccessListTx
DynamicFeeTx	Txn data if txn of type DynamicFeeTx
raw_data	encoded raw logs
TxRaw	encoded raw bytes
gas_price	gas price at time of txn

evm_logs

This table contains the raw event logs that we encode to build most of the aggregated tables for the EVM. Each log record consists of both topics and data. Topics are 32-byte (256 bit) “words” that are used to describe what’s going on in an event.

Field	Description
address	smart contract that emitted events
topics	The first part of a log record consists of an array of topics. These topics are used to describe the event.
data	The second part of a log record consists of additional data.
block_hash	hash of the block of the txn
log_index	index of the log within txn
tranasction_hash_evm	hash of the evm txn
ingestion_timestamp	time ingested into Numia

Additional tables have data that is not event-based but relevant when working with event-based data.

Aggregated Tables (EVM)

evm_token_sales

Records erc1155 or erc720 token sales from specific contracts (marketplaces).

evm_transfer_event

Records individual token transfers that happen every time an ERC20 or ERC721 token standard smart contract registers one of these transfers. Multiple transfers can happen on the same txn.

evm_uniswap_v2_dex_swaps

Records individual trades of the swapExactTokensForTokens method of all Uniswap V2 forks. Each record corresponds to a swap of each individual pair that was hopped during the trade. If the swapExactTokensForTokensac generated a multi-hop trade, then you will see multiple records for the same tx_hash.