BlockDB ERC721 Tokens / NFT Collections Details | Ethereum & EVM Chains | Historical, EOD, ...

🟦 What this is
Canonical ERC-721 NFT collection reference with deterministic tracing at the row level.
One row per deployed NFT contract, providing audit-grade lineage to the first recognition event and parent/genesis derivations.

Key traits
• Schema-stable, versioned, and audit-ready
• Historical + real-time ingestion from chain genesis
• Verified on-chain metadata (name, symbol) from contract ABI reads

🌐 Chains / 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 the columns exactly as delivered. Keep names/types consistent with files.
• contract_address BYTEA - PK; 20-byte ERC-20 contract address
• tracing_id BYTEA - deterministic row-level hash (proof-of-derivation)
• parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph
• genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path)
• genesis_block_number BIGINT - first block where the token was recognized
• genesis_tx_index INTEGER - tx index for that event
• genesis_log_index INTEGER - log index for that event
• name TEXT - NFT collection name (from ABI call name())
• symbol TEXT - NFT symbol (from ABI call symbol())
• base_token_uri TEXT NULL - Base token URI (from ABI call baseTokenURI())

Notes
• Use encode(contract_address,'hex') for hex presentation.
• Metadata is obtained deterministically via ABI calls; records are included only when both name and symbol are successfully decoded.
• Additional token-level data (e.g. token_id, token_uri) are stored in dependent tables such as erc721_items.

🔑 Keys & Joins
• Primary key: contract_address
• Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index)

🧬 Lineage & Reproducibility
Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph:
• tracing_id - this row’s identity
• parent_tracing_ids - immediate sources
• genesis_tracing_ids - original on-chain sources
This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses
• Token registry to normalize joins for swaps, transfers, pools, and prices
• Amount scaling via decimals for analytics, PnL, and model features
• App backends: display names/symbols and validate token addresses

🚚 Delivery
By default
• WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day).
• SFTP server for archives and daily End-of-Day (EOD) snapshots.
• Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage).
Optional
• Integrations to Amazon S3, Azure Blob Storage, Snowflake, and other enterprise platforms on request.

🗂️ Files (time-partitioned in UTC, compressed)
• Parquet
• CSV
• XLS
• JSON

💡 Quality and operations
• Reorg-aware ingestion.
• 99.95% uptime target SLA.
• Backfills to chain genesis.
• Versioned, schema-stable datasets; changes are additive and announced.

🔄 Change policy
Schema is stable. Any breaking change ships as a new version (e.g., erc721_tokens_v2) with migration notes. Content updates are additive (new rows/fields filled); types aren’t changed in place.