ERC-20 Crypto Tokens | Ethereum EVM Blockchain Data

**Dataset Overview**

BlockDB ERC-20 Tokens provides a production-grade catalog of every fungible token contract discovered across Ethereum and EVM-compatible chains. Each record represents a unique token contract with its ABI-decoded metadata - name, symbol, and decimals - alongside the genesis block where the token was first recognized. Detection requires all three mandatory EIP-20 functions (totalSupply, balanceOf, allowance) to return valid results; contracts that fail the check are excluded, keeping the registry clean and reliable as a JOIN anchor for swap, transfer, price, and portfolio datasets.

<p><br/></p>

**Metamorphic contracts & proxies:** Rows use stable contract_id (per deployment incarnation), not contract_address alone—so metamorphic redeployments at the same address and upgradeable proxies are handled correctly. Prefer joins on contract_id over address alone.

<p><br/></p>

**Sample Notice**

This dataset contains **a small sample** of the full BlockDB ERC-20 Token Registry dataset. It is provided **for evaluation, research, and interoperability testing only**. If you need full historical coverage, real-time streaming, or end-of-day (EOD) exports please contact us via contact form on Snowflake Marketplace.

<p><br/></p>

**Chains and Coverage**

ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full history from chain genesis; reorg-aware real-time ingestion and updates.

<p><br/></p>

**Join Keys**

CONTRACT_ADDRESS links to TOKEN_IN / TOKEN_OUT in swap and price tables, TOKEN_ADDRESS in BLOCKDB0304_TOKEN_TRANSFERS_V1, and the TOKENS array in BLOCKDB0211_LIQUIDITY_POOLS_V1. The DECIMALS field is the standard input for scaling raw uint256 amounts across all BlockDB numeric datasets.

<p><br/></p>

**Lineage**

Each token record includes deterministic _TRACING_ID and _PARENT_TRACING_IDS, providing verifiable provenance from the raw log where the contract was first recognized through to the decoded metadata stored here.

<p><br/></p>

**Quality**

- Verifiable lineage: deterministic cryptographic hashes per row
- Reorg-aware ingestion: continuity and consistency across forks
- Complete historical coverage: from chain genesis to present