Update README.md
Browse files
README.md
CHANGED
|
@@ -36,25 +36,25 @@ Full history from chain genesis; reorg-aware real-time ingestion and updates.
|
|
| 36 |
|
| 37 |
## Schema
|
| 38 |
List of columns exactly as delivered:
|
| 39 |
-
|
| 40 |
-
|
| 41 |
-
|
| 42 |
-
|
| 43 |
-
|
| 44 |
-
|
| 45 |
-
|
| 46 |
-
|
| 47 |
-
|
| 48 |
-
|
| 49 |
-
|
| 50 |
-
|
| 51 |
-
|
| 52 |
-
|
| 53 |
|
| 54 |
|
| 55 |
### Notes
|
| 56 |
-
|
| 57 |
-
|
| 58 |
|
| 59 |
|
| 60 |
## Lineage
|
|
@@ -63,13 +63,13 @@ This ensures verifiable traceability, reproducibility, and proof-of-derivation f
|
|
| 63 |
|
| 64 |
|
| 65 |
## Common Use Cases
|
| 66 |
-
|
| 67 |
-
|
| 68 |
-
|
| 69 |
-
|
| 70 |
|
| 71 |
|
| 72 |
## Quality
|
| 73 |
-
|
| 74 |
-
|
| 75 |
-
|
|
|
|
| 36 |
|
| 37 |
## Schema
|
| 38 |
List of columns exactly as delivered:
|
| 39 |
+
• block_number BIGINT - Sequential block number
|
| 40 |
+
• block_hash BYTEA - 32-byte block hash
|
| 41 |
+
• parent_hash BYTEA - 32-byte parent block hash
|
| 42 |
+
• receipts_root BYTEA - Root hash of all receipts in the block
|
| 43 |
+
• miner BYTEA - 20-byte miner (beneficiary) address
|
| 44 |
+
• gas_limit NUMERIC(78,0) - Maximum gas allowed for the block
|
| 45 |
+
• extra_data BYTEA - Arbitrary ≤32-byte payload embedded by the block producer
|
| 46 |
+
• size BIGINT - Total block size in bytes (header + transactions + receipts)
|
| 47 |
+
• timestamp_utc TIMESTAMPTZ - UTC timestamp when the block was mined
|
| 48 |
+
• _tracing_id BYTEA - Deterministic tracing ID of this block record
|
| 49 |
+
• _computed_receipt_root BYTEA - Recomputed receipts root (BlockDB integrity check)
|
| 50 |
+
• _computed_receipt_timestamp_utc TIMESTAMPTZ - Timestamp when the receipts root was computed or revalidated
|
| 51 |
+
• _created_at TIMESTAMPTZ - Record creation timestamp
|
| 52 |
+
• _updated_at TIMESTAMPTZ - Record last update timestamp
|
| 53 |
|
| 54 |
|
| 55 |
### Notes
|
| 56 |
+
• Use encode(block_hash, 'hex') to convert binary values to hex for presentation or joins.
|
| 57 |
+
• Every block record is verified against the node RPC.
|
| 58 |
|
| 59 |
|
| 60 |
## Lineage
|
|
|
|
| 63 |
|
| 64 |
|
| 65 |
## Common Use Cases
|
| 66 |
+
• Benchmarking node or indexer consistency across chains
|
| 67 |
+
• Establishing canonical ground truth for analytics or compliance systems
|
| 68 |
+
• Foundation layer for derived token, swap, and liquidity datasets
|
| 69 |
+
• Validating receipts and state integrity with recomputed roots
|
| 70 |
|
| 71 |
|
| 72 |
## Quality
|
| 73 |
+
• Verifiable lineage: deterministic cryptographic hashes per row
|
| 74 |
+
• Reorg-aware ingestion: continuity and consistency across forks
|
| 75 |
+
• Complete historical coverage: from chain genesis to present
|