Update README.md
Browse files
README.md
CHANGED
|
@@ -16,79 +16,12 @@ tags:
|
|
| 16 |
pretty_name: BlockDB Token Transfers - Sample
|
| 17 |
size_categories:
|
| 18 |
- 10M<n<100M
|
|
|
|
|
|
|
| 19 |
---
|
| 20 |
|
| 21 |
-
|
| 22 |
|
| 23 |
-
|
| 24 |
|
| 25 |
-
|
| 26 |
-
It is provided **for evaluation, research, and interoperability testing only**.
|
| 27 |
-
|
| 28 |
-
If you need full historical coverage, real-time streaming, or end-of-day (EOD) exports
|
| 29 |
-
please contact us directly:
|
| 30 |
-
|
| 31 |
-
📧 **support@blockdb.io**
|
| 32 |
-
🌐 https://www.blockdb.io
|
| 33 |
-
|
| 34 |
-
|
| 35 |
-
## Dataset Overview
|
| 36 |
-
Unified token transfer table covering all transfer types in a single normalized schema. Each row represents one transfer event sourced from transactions, internal transactions, or transfer logs — covering native ETH, ERC-20, ERC-721, and ERC-1155 transfers. Only transfers for identified contract addresses are included.
|
| 37 |
-
|
| 38 |
-
Every transfer record includes deterministic tracing IDs that link the record to its genesis event and upstream sources, enabling full provenance tracking for downstream analytics.
|
| 39 |
-
|
| 40 |
-
|
| 41 |
-
## Chains and Coverage
|
| 42 |
-
ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request).
|
| 43 |
-
Full history from chain genesis; reorg-aware real-time ingestion and updates.
|
| 44 |
-
|
| 45 |
-
|
| 46 |
-
## Schema
|
| 47 |
-
List of columns exactly as delivered:
|
| 48 |
-
|
| 49 |
-
• id BIGINT – Surrogate primary key (auto-generated)
|
| 50 |
-
• block_number BIGINT – Block where the transfer occurred
|
| 51 |
-
• block_time TIMESTAMPTZ – UTC timestamp when the block was mined
|
| 52 |
-
• tx_index INTEGER – Transaction index within the block
|
| 53 |
-
• log_index INTEGER – Log index within the transaction receipt; null for native or internal tx transfers
|
| 54 |
-
• trace_address TEXT – Trace address for internal tx transfers (e.g., "0", "0.1"); null for other types
|
| 55 |
-
• from_address BYTEA – Sender address (20 bytes)
|
| 56 |
-
• to_address BYTEA – Recipient address (20 bytes)
|
| 57 |
-
• token_address BYTEA – Token contract address (20 bytes); null for native ETH transfers
|
| 58 |
-
• amount_raw NUMERIC(78,0) – Raw amount in smallest unit (wei for native, raw uint256 for ERC-20/1155)
|
| 59 |
-
• amount_adj TEXT – Decimal-adjusted amount; null if decimals unknown or NFT
|
| 60 |
-
• token_id NUMERIC(78,0) – Token ID for ERC-721 and ERC-1155; null for native/ERC-20
|
| 61 |
-
• transfer_type TEXT – Transfer type: native_tx, native_internal, erc20, erc721, erc1155
|
| 62 |
-
• _tracing_id BYTEA – Tracing ID of this transfer record
|
| 63 |
-
• _parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this transfer record
|
| 64 |
-
• _created_at TIMESTAMPTZ – Record creation timestamp
|
| 65 |
-
• _updated_at TIMESTAMPTZ – Record last update timestamp
|
| 66 |
-
|
| 67 |
-
|
| 68 |
-
### Notes
|
| 69 |
-
• transfer_type distinguishes native ETH from top-level transactions (native_tx) vs. internal calls (native_internal).
|
| 70 |
-
• amount_adj is null for NFTs (ERC-721) and when token decimals cannot be determined.
|
| 71 |
-
• FK: (block_number, tx_index) → blockdb_evm.b0102_transactions_v1.
|
| 72 |
-
• Binary values can be rendered as hex via encode(column, 'hex') in SQL.
|
| 73 |
-
|
| 74 |
-
|
| 75 |
-
## Lineage
|
| 76 |
-
Each transfer record includes deterministic _tracing_id and _parent_tracing_ids, providing:
|
| 77 |
-
|
| 78 |
-
• Provenance tracking from raw transactions, internal calls, and logs to normalized transfer events
|
| 79 |
-
• Reproducible analytics and signal extraction
|
| 80 |
-
• Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)
|
| 81 |
-
|
| 82 |
-
|
| 83 |
-
## Common Use Cases
|
| 84 |
-
• Wallet balance and flow analytics across all token standards
|
| 85 |
-
• Token movement and holder tracking
|
| 86 |
-
• Compliance and attribution (native + ERC-20/721/1155 in one table)
|
| 87 |
-
• MEV and arbitrage flow reconstruction
|
| 88 |
-
• Portfolio tracking and tax reporting
|
| 89 |
-
|
| 90 |
-
|
| 91 |
-
## Quality
|
| 92 |
-
• Verifiable lineage: deterministic cryptographic hashes per row
|
| 93 |
-
• Reorg-aware ingestion: continuity and consistency across forks
|
| 94 |
-
• Complete historical coverage: from chain genesis to present
|
|
|
|
| 16 |
pretty_name: BlockDB Token Transfers - Sample
|
| 17 |
size_categories:
|
| 18 |
- 10M<n<100M
|
| 19 |
+
dataset_info:
|
| 20 |
+
homepage: https://docs.blockdb.io/data-catalog/evm/transfers/token-transfers
|
| 21 |
---
|
| 22 |
|
| 23 |
+
*Small evaluation sample.*
|
| 24 |
|
| 25 |
+
**`0304`** · `blockdb_evm.b0304_token_transfers_v1` - Token transfer events (native ETH, ERC-20, ERC-721, ERC-1155) produced by TokenTransfersEngine from transactions, internal transactions, and transfer logs.
|
| 26 |
|
| 27 |
+
**🌐 [BlockDB docs — schema, API, WebSocket & signup](https://docs.blockdb.io/data-catalog/evm/transfers/token-transfers)**
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|