| 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 |
| NODE_PUBKEY | TEXT | The account for the validator node on the Solana network. This field identifies the specific validator that participates in network consensus and receives stake delegations. Data type: STRING (Solana address) Business context: Used to identify validators, track performance, and analyze stake delegation patterns. Analytics use cases: Validator identification, performance tracking, and stake delegation analysis. Example: ‘9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM’ |
| SFDP_ID | NUMBER | Unique identifier assigned by the Solana Foundation to validators in the SFDP program. This ID is used internally by the foundation to track validator participation and program status. |
| CLUSTER | TEXT | The Solana cluster this validator operates on (e.g., ‘mainnet-beta’, ‘testnet’). Indicates the network environment for the validator’s SFDP participation. |
| VALIDATOR_PK | TEXT | The validator’s public key as recorded in the SFDP system. This should match the node_pubkey and serves as the primary identifier in the foundation’s database. |
| SFDP_STATE | TEXT | Current state of the validator within the SFDP program (e.g., ‘active’, ‘inactive’, ‘pending’). This field indicates whether the validator is currently receiving foundation stake through the program. |
| APPROVAL_STATE | TEXT | The approval status of the validator’s SFDP application (e.g., ‘approved’, ‘pending’, ‘rejected’). Validators must be approved before receiving foundation stake allocations. |
| SFDP2_ONBOARDING_EPOCH | NUMBER | The epoch when the validator was onboarded to SFDP version 2. This marks the beginning of the validator’s participation in the updated delegation program with new matching mechanics. |
| IS_HIDDEN | BOOLEAN | Boolean flag indicating whether the validator is hidden from public SFDP listings. Hidden validators may be in a probationary state or have requested privacy from public rankings. |
| SKIP_RATE | NUMBER | The validator’s slot skip rate for the current epoch, expressed as a decimal. A skip occurs when a validator fails to produce a block in their assigned leader slot. Lower values indicate better performance. |
| FIVE_EPOCH_SKIP_RATE | NUMBER | Rolling average skip rate over the last five epochs. This smoothed metric provides a more stable view of validator performance and is used by SFDP for eligibility assessments. |
| CURRENT_COMMISSION | NUMBER | The validator’s current commission rate charged to delegators, expressed as a percentage. SFDP has commission requirements that validators must meet to remain eligible for foundation stake. |
| COMMISSION_MAX_OBSERVED | NUMBER | The highest commission rate ever observed for this validator. SFDP tracks this to detect validators who may have temporarily raised commissions (commission rugging). |
| COMMISSION_ADVERTISED | NUMBER | The commission rate the validator has advertised or committed to. Discrepancies between advertised and current commission may indicate commission changes. |
| HAS_COMMISSION_RUGGED | BOOLEAN | Boolean flag indicating whether the validator has ever engaged in commission rugging (unexpectedly raising commission rates). Validators flagged for this behavior may be penalized or removed from SFDP. |
| JITO_COMMISSION_PERCENT | NUMBER | The validator’s Jito MEV commission rate as a percentage. This tracks MEV commission separately from standard staking commission for validators running Jito. |
| SELF_STAKE_LAMPORTS | NUMBER | Amount of SOL the validator has self-staked, in lamports (1 SOL = 1,000,000,000 lamports). Self-stake demonstrates the validator’s commitment and is often a factor in SFDP matching calculations. |
| TOTAL_STAKE_LAMPORTS | NUMBER | Total amount of SOL staked to this validator from all sources, in lamports. This includes self-stake, foundation stake, and delegated stake from other parties. |
| ACTIVATED_STAKE_LAMPORTS | NUMBER | Amount of stake that is actively participating in consensus, in lamports. This excludes stake that is warming up, cooling down, or otherwise inactive. |
| SELF_STAKE_SOL | NUMBER | Amount of SOL the validator has self-staked, converted from lamports to SOL. This human-readable format is useful for analysis and reporting. |
| TOTAL_STAKE_SOL | NUMBER | Total amount of SOL staked to this validator from all sources, converted from lamports to SOL. Provides an easy-to-understand view of the validator’s total stake weight. |
| ACTIVATED_STAKE_SOL | NUMBER | Amount of stake actively participating in consensus, converted from lamports to SOL. This represents the validator’s effective voting power in the network. |
| FOUNDATION_STAKE_LAMPORTS | NUMBER | Current amount of foundation stake allocated to this validator, in lamports. This is the actual SOL delegated by the Solana Foundation through the SFDP program. |
| TARGET_TOTAL_FOUNDATION_STAKE_LAMPORTS | NUMBER | Target total foundation stake the validator should receive based on SFDP calculations, in lamports. This combines matching and remainder allocations. |
| TARGET_FOUNDATION_STAKE_FROM_MATCHING_LAMPORTS | NUMBER | Target foundation stake from the matching program, in lamports. SFDP matches validator self-stake up to certain limits to incentivize operator investment. |
| TARGET_FOUNDATION_STAKE_FROM_REMAINDER_LAMPORTS | NUMBER | Target foundation stake from remainder distribution, in lamports. After matching allocations, remaining foundation stake is distributed based on other criteria. |
| DESIRED_TARGET_FOUNDATION_STAKE_FROM_MATCHING_LAMPORTS | NUMBER | The validator’s desired target matching stake, in lamports. This may differ from the actual target if the validator is working toward higher matching levels. |
| DESIRED_TARGET_FOUNDATION_STAKE_FROM_REMAINDER_LAMPORTS | NUMBER | The validator’s desired target remainder stake, in lamports. Represents the validator’s aspirational allocation from the remainder pool. |
| FOUNDATION_STAKE_SOL | NUMBER | Current amount of foundation stake allocated to this validator, converted from lamports to SOL. Provides a human-readable view of foundation delegation. |
| TARGET_TOTAL_FOUNDATION_STAKE_SOL | NUMBER | Target total foundation stake the validator should receive, converted from lamports to SOL. This is the combined target from all SFDP allocation mechanisms. |
| TARGET_FOUNDATION_STAKE_FROM_MATCHING_SOL | NUMBER | Target foundation stake from the matching program, converted from lamports to SOL. Shows the matched stake amount based on validator self-stake. |
| TARGET_FOUNDATION_STAKE_FROM_REMAINDER_SOL | NUMBER | Target foundation stake from remainder distribution, converted from lamports to SOL. Shows allocation from the pool distributed after matching. |
| DESIRED_TARGET_FOUNDATION_STAKE_FROM_MATCHING_SOL | NUMBER | The validator’s desired target matching stake, converted from lamports to SOL. Represents the validator’s goal for matched foundation stake. |
| DESIRED_TARGET_FOUNDATION_STAKE_FROM_REMAINDER_SOL | NUMBER | The validator’s desired target remainder stake, converted from lamports to SOL. Represents the validator’s aspirational remainder allocation. |
| VOTE_ACCOUNT | TEXT | The validator’s vote account public key as recorded in SFDP. This should match vote_pubkey and is the account used for consensus voting. |
| VOTE_CREDITS | NUMBER | Number of vote credits earned by this validator during the epoch. Vote credits are earned for successful votes on blocks and determine reward distribution. |
| RELEASE_VERSION | TEXT | The Solana software version the validator is running. SFDP may require validators to run recent versions to remain eligible for foundation stake. |
| SFDP_VERSION | TEXT | The SFDP program version the validator is participating in. Different versions may have different rules and stake allocation mechanics. |
| DISPLAY_COMMISSION | NUMBER | The commission rate displayed to users, which may be formatted differently from the raw commission value. Used for user-facing presentations. |
| DC_COUNTRY_ISO | TEXT | ISO country code for the data center where the validator is hosted. SFDP tracks geographic distribution to promote network decentralization. |
| DC_CONCENTRATION | NUMBER | Data center concentration metric indicating what percentage of network stake is hosted in the same data center. Higher values indicate centralization risk. |
| DC_ASN | NUMBER | Autonomous System Number (ASN) of the data center hosting the validator. Used to track infrastructure diversity and prevent over-concentration on single providers. |
| DC_ASO | TEXT | Autonomous System Organization name for the data center. Identifies the hosting provider or network operator running the validator’s infrastructure. |
| TESTNET_PERFORMANCE_SCORE | NUMBER | Performance score based on the validator’s activity in the last 10 testnet epochs. Validators may need to demonstrate testnet participation for SFDP eligibility. |
| VOTE_COST_COVERAGE_PERCENT | NUMBER | Percentage of vote transaction costs covered by the validator’s earnings. Indicates the validator’s economic sustainability and ability to cover operational costs. |
| ISSUES_LIST | TEXT | Comma-separated list of issues or flags identified for this validator by SFDP. Issues may affect eligibility or require remediation for continued program participation. |
| FACT_VALIDATORS_SFDP_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. |
