BlockDB/ERC1155-Tokens-Ethereum-And-EVM-Cryptocurrency-Data

Sample Notice

This dataset contains a small sample of the full BlockDB ERC-1155 Tokens 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 directly:

📧 support@blockdb.io
🌐 https://www.blockdb.io

Dataset Overview

Catalog of ERC-1155 Multi Token contracts discovered on-chain. Each row represents a unique ERC-1155 contract with its optional metadata (name, symbol, decimals, uri) and detection metadata. Primary detection uses ERC-165 supportsInterface(0xd9b67a26); a fallback heuristic is applied when ERC-165 is unavailable.

Every token record includes deterministic tracing IDs that link the record to its genesis event and upstream sources, enabling full provenance tracking for downstream analytics.

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.

Schema

List of columns exactly as delivered:

•	contract_address BYTEA – 20-byte address of the ERC-1155 contract (primary key)
•	block_number BIGINT – Block of the log attributed as the genesis/recognition point
•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
•	tx_index INTEGER – Transaction index within the block
•	name TEXT – Contract name from name() (optional in EIP-1155; may be null)
•	symbol TEXT – Contract symbol from symbol() (optional in EIP-1155; may be null)
•	decimals SMALLINT – Contract decimals from decimals() (optional in EIP-1155; may be null)
•	uri TEXT – URI from uri(uint256) (optional ERC1155Metadata_URI); clients replace {id} with token ID in hex (64 chars)
•	supports_metadata_uri BOOLEAN – Whether the contract supports the ERC1155Metadata_URI extension; null when detection was via fallback
•	_tracing_id BYTEA – Tracing ID of this ERC-1155 token record
•	_genesis_tracing_ids BYTEA[] – Tracing IDs of the genesis records leading to this token record
•	_parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this token record
•	_created_at TIMESTAMPTZ – Record creation timestamp
•	_updated_at TIMESTAMPTZ – Record last update timestamp

Notes

•	Primary key: contract_address guarantees uniqueness per contract.
•	name, symbol, decimals, and uri are all optional per EIP-1155 and may be null.
•	uri uses {id} placeholder per EIP-1155 spec; substitute the token ID (zero-padded 64-char hex) before fetching.
•	Binary values can be rendered as hex via encode(column, 'hex') in SQL for display or downstream joins.

Lineage

Each token record includes deterministic _tracing_id, _genesis_tracing_ids, and _parent_tracing_ids, providing:

•	Provenance tracking from raw logs to decoded multi-token contract metadata
•	Reproducible analytics and signal extraction
•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases

•	Multi-token and semi-fungible contract registry
•	Game asset and metaverse item catalog construction
•	Metadata resolution via uri(uint256) with {id} substitution
•	Portfolio and transfer analytics for ERC-1155 holdings

Quality

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