ethereum.beacon_chain Table: fact_deposits Type: View
What
This table contains information about the deposits made to the beacon chain. For more info, please visit The Ethereum OrganizationColumns
| Column Name | Data Type | Description |
|---|---|---|
| SLOT_NUMBER | NUMBER | The Beacon Chain slot this block represents. |
| SLOT_TIMESTAMP | TIMESTAMP_NTZ | Timestamp of Beacon Chain slot. |
| EPOCH_NUMBER | NUMBER | A period of 32 slots, each slot being 12 seconds, totaling 6.4 minutes. |
| DEPOSIT_AMOUNT | FLOAT | Decimal adjusted Ether deposit amount. |
| PUBKEY | TEXT | Validator public key. |
| SIGNATURE | TEXT | Signature of Validator deposit. |
| WITHDRAWAL_CREDENTIALS | TEXT | A 32-byte field verifying the destination of valid withdrawals. |
| PROOFS | VARIANT | The merkle path to the deposit root. In other words, the merkle proof against the current state.eth1_data.root in the BeaconState. Note that the + 1 in the vector length is due to the SSZ length mixed into the root. |
| FACT_DEPOSITS_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example: |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: |