| EPOCH | NUMBER | A period of time consisting of 432,000 blocks, which represents a higher-level timekeeping unit within the Solana network |
| VOTE_PUBKEY | TEXT | Account address of voter |
| IDENTITY_PUBKEY | TEXT | The validator’s identity public key (node pubkey) as recorded in Jito’s system. This is the validator’s main identity used for network communication and block production. |
| ACTIVATED_STAKE_LAMPORTS | NUMBER | Amount of stake actively participating in consensus as reported by Jito, in lamports. May differ slightly from on-chain values due to API timing. |
| ACTIVATED_STAKE_SOL | NUMBER | Amount of stake actively participating in consensus as reported by Jito, converted from lamports to SOL. Provides human-readable stake amounts. |
| MEV_COMMISSION_BPS | NUMBER | The validator’s MEV commission rate in basis points (1 bps = 0.01%). This is the percentage of MEV rewards retained by the validator before distribution to delegators. |
| MEV_COMMISSION_RATE | NUMBER | The validator’s MEV commission rate as a decimal (e.g., 0.10 = 10%). Calculated from basis points for easier percentage calculations. |
| MEV_EARNED_EPOCH_LAMPORTS | NUMBER | Total MEV rewards earned by this validator during the epoch, in lamports. Includes all MEV from transaction ordering, arbitrage, and other value extraction. |
| MEV_EARNED_EPOCH_SOL | NUMBER | Total MEV rewards earned by this validator during the epoch, converted from lamports to SOL. Provides a clear view of MEV earnings. |
| PRIORITY_FEE_COMMISSION_BPS | NUMBER | The validator’s priority fee commission rate in basis points. This is the percentage of priority fees retained by the validator. |
| PRIORITY_FEE_COMMISSION_RATE | NUMBER | The validator’s priority fee commission rate as a decimal. Calculated from basis points for easier calculations and comparison. |
| PRIORITY_FEE_REWARDS_LAMPORTS | NUMBER | Total priority fee rewards earned by this validator during the epoch, in lamports. Priority fees are additional payments for faster transaction processing. |
| IS_RUNNING_JITO | BOOLEAN | Boolean flag indicating whether the validator is running Jito’s MEV client software. Validators running Jito participate in the MEV auction system. |
| IS_RUNNING_BAM | BOOLEAN | Boolean flag indicating whether the validator is running Jito’s Block Auction Mechanism (BAM). BAM is Jito’s system for auctioning block space to searchers. |
| JITO_DIRECTED_STAKE_LAMPORTS | NUMBER | Amount of stake directed to this validator through Jito’s directed stake program, in lamports. This represents stake specifically allocated through Jito’s staking mechanisms. |
| JITO_DIRECTED_STAKE_TARGET | BOOLEAN | Boolean flag indicating whether this validator is a target for Jito’s directed stake program. Target validators may receive additional stake allocations from Jito. |
| FACT_VALIDATORS_JITO_ID | TEXT | A unique, stable identifier for each record in this table. The primary key (PK) ensures that every row is uniquely identifiable and supports efficient joins, lookups, and data integrity across models. The PK may be a natural key (such as a blockchain transaction hash) or a surrogate key generated from one or more fields, depending on the table’s structure and requirements. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was first inserted into the analytics database. Used for data freshness tracking and incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when this transaction record was last updated in the analytics database. Used for tracking updates and supporting incremental model logic. Format: YYYY-MM-DD HH:MI:SS. Not derived from the blockchain, but from the ETL process. |