ethereum.beacon_chain Table: fact_attestations Type: View
What
Validators are expected to create, sign, and broadcast an attestation during every epoch. Data in this table contains details around these attestations. 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. |
| ATTESTATION_SLOT | NUMBER | The slot number in which the validator is attesting on |
| ATTESTATION_INDEX | NUMBER | A number that identifies which committee the validator belongs to in a given slot |
| AGGREGATION_BITS | TEXT | AGGREGATION_BITS column |
| BEACON_BLOCK_ROOT | TEXT | Root hash of the block the validator sees at the head of the chain (the result of applying the fork-choice algorithm) |
| SOURCE_EPOCH | NUMBER | Part of the finality vote indicating what the validators see as the most recent justified block |
| SOURCE_ROOT | TEXT | Part of the finality vote indicating what the validators see as the most recent justified block |
| TARGET_EPOCH | NUMBER | Part of the finality vote indicating what the validators see as the first block in the current epoch |
| TARGET_ROOT | TEXT | Part of the finality vote indicating what the validators see as the first block in the current epoch |
| ATTESTATION_SIGNATURE | TEXT | A BLS signature that aggregates the signatures of individual validators |
| FACT_ATTESTATIONS_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: |