ERC-1155 Tokens | Ethereum EVM Blockchain Data

**Dataset Overview**

BlockDB ERC-1155 Token Registry provides a comprehensive catalog of every ERC-1155 multi-token contract discovered across Ethereum and EVM-compatible chains - covering gaming assets, semi-fungible tokens, and mixed-standard collections. Detection uses ERC-165 supportsInterface(0xd9b67a26) as the primary method; a fallback heuristic based on balanceOf(address,uint256) applies when ERC-165 is unavailable, with SUPPORTS_METADATA_URI flagged NULL to indicate detection method. Optional EIP-1155 metadata fields - name, symbol, decimals, and URI - are stored when present, and the URI field uses the standard {id} placeholder for token ID substitution.

<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-1155 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 → TOKEN_ADDRESS in BLOCKDB0304_TOKEN_TRANSFERS_V1 for ERC-1155 transfer analytics. URI provides the metadata base URI; substitute the token ID as a zero-padded 64-character hex string per EIP-1155 spec.

<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