ethereum.beacon_chain Table: fact_validators Type: View
What
This table contains information about the validators. For more info, please visit The Ethereum OrganizationColumns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_NUMBER | NUMBER | Deprecating soon! The name of this column will be replaced with slot_number. The values remain the same and are currently accurate, representative of the Beacon Chain Slot Number. Please migrate queries to the new column by 11/13/23. |
| SLOT_NUMBER | NUMBER | The Beacon Chain slot this block represents. |
| STATE_ID | TEXT | The hash-tree-root of the BeaconState. |
| INDEX | NUMBER | Each Validator receives their own unique index. |
| BALANCE | FLOAT | Balance of Validator |
| VALIDATOR_STATUS | TEXT | Status of Validator (ie. are they Active) |
| ACTIVATION_ELIGIBILITY_EPOCH | NUMBER | Refers to pending validators. The deposit has been recognized by the ETH2 chain at the timestamp of “Eligible for activation”. If there is a queue of pending validators, an estimated timestamp for activation is calculated |
| ACTIVATION_EPOCH | NUMBER | A period of 32 slots, each slot being 12 seconds, totaling 6.4 minutes. |
| EFFECTIVE_BALANCE | FLOAT | The effective Balance represents a value calculated by the current balance. It is used to determine the size of a reward or penalty a validator receives. The effective balance can **never be higher than 32 ETH. |
| EXIT_EPOCH | NUMBER | A period of 32 slots, each slot being 12 seconds, totaling 6.4 minutes. |
| PUBKEY | TEXT | Validator public key. |
| SLASHED | BOOLEAN | In Phase 0, a validator can be slashed (a more severe penalty) if they violate the Casper FFG rules or if they create two beacon blocks in one epoch. |
| WITHDRAWABLE_EPOCH | NUMBER | When Validator can withdraw funds |
| WITHDRAWAL_CREDENTIALS | TEXT | Commitment to pubkey for withdrawals |
| VALIDATOR_DETAILS | VARIANT | Information about the validator |
| FACT_VALIDATORS_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: |