Upload 5 files

README.md

@@ -1,3 +1,86 @@
----
-license: cc-by-nc-4.0
----
+---
+license: cc-by-nc-4.0
+tags:
+- ethereum
+- evm
+- blockchain
+- cryptocurrency
+- crypto
+- onchain-data
+- tabular
+- timeseries
+- datasets
+- pandas
+- polars
+- duckdb
+pretty_name: BlockDB Raw Contracts - Sample
+size_categories:
+- 10M<n<100M
+---
+
+![BlockDB Banner](./assets/banner.jpg)
+
+## Sample Notice
+
+This dataset contains **a small sample** of the full BlockDB Raw Contracts 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
+Canonical smart contract registry built from CREATE and CREATE2 internal transactions. Each row represents a single contract incarnation with its deployment block, creator address, and call type. A composite 26-byte primary key (address + creation block + tx index) correctly handles metamorphic contracts that self-destruct and redeploy at the same address.
+
+
+## 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_id BYTEA – Primary key: 20 bytes (address) + 4 bytes (creation block, big-endian) + 2 bytes (tx_index, big-endian)
+	•	contract_address BYTEA – Deployed contract address (20 bytes); separate column for efficient lookups
+	•	block_number BIGINT – Block number where the contract was deployed
+	•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
+	•	tx_index INTEGER – Transaction index within the block
+	•	trace_address TEXT – Position in the call tree (e.g., "0", "0.0", "0.1.2")
+	•	creator_address BYTEA – Address that deployed the contract (msg.sender of CREATE/CREATE2, 20 bytes)
+	•	creation_call_type TEXT – Type of creation call: CREATE or CREATE2
+	•	_tracing_id BYTEA – Deterministic tracing ID of this contract record
+	•	_created_at TIMESTAMPTZ – Record creation timestamp
+	•	_updated_at TIMESTAMPTZ – Record last update timestamp
+
+
+### Notes
+	•	contract_id uses a composite key to handle metamorphic contracts (CREATE–SELFDESTRUCT–CREATE2 at the same address in the same block).
+	•	Use encode(contract_address, 'hex') or encode(creator_address, 'hex') to convert binary values to hex.
+	•	FK: (block_number, tx_index) → blockdb_evm.b0102_transactions_v1.
+	•	Indexes on contract_address and (block_number, tx_index) support fast lookups.
+
+
+## Lineage
+Each contract record includes a deterministic _tracing_id, providing:
+
+	•	Provenance tracking from raw CREATE/CREATE2 traces to contract deployment events
+	•	Reproducible analytics and signal extraction
+	•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)
+
+
+## Common Use Cases
+	•	Contract registry and address validation
+	•	Deployment tracking and contract lifecycle analysis
+	•	Factory pattern analysis and contract creation flows
+	•	Security research and contract classification
+	•	Foundation for contract interaction and metadata analysis
+
+
+## Quality
+	•	Verifiable lineage: deterministic cryptographic hashes per row
+	•	Reorg-aware ingestion: continuity and consistency across forks
+	•	Complete historical coverage: from chain genesis to present

data/blockdb0121_contracts_v1.parquet

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b75069cdc7b0ce97699f0249ea3fc16edd376f5aabfc764b36d7e12942968f1c
+size 130111