Fact Gov Actions

Schema: solana.gov Table: fact_gov_actions Type: Base Table

​

Description

This table tracks all governance actions across Saber and Marinade governance platforms. It captures various governance activities such as voting, proposal creation, and administrative actions, providing a comprehensive view of decentralized governance participation and decision-making processes on Solana.

​

Key Use Cases

• Analyze governance participation patterns across different protocols
• Track voting behavior and decision-making processes
• Monitor governance action types and their frequency
• Study protocol governance evolution and participation trends
• Support governance analytics and reporting for DAOs and protocols

​

Important Relationships

• Links to gov.fact_proposal_votes through governance context for comprehensive voting analysis
• Connects to gov.fact_proposal_creation for proposal lifecycle tracking
• References core.fact_blocks and core.fact_transactions for blockchain context
• Provides governance context for protocol-specific analytics

​

Commonly-used Fields

• block_timestamp: Timestamp when the governance action was processed
• tx_id: Unique transaction identifier for the governance action
• signer: Address of the account that performed the governance action
• program_name: Name of the governance program (e.g., ‘saber’, ‘marinade’)
• action: Type of governance action performed
• amount: Amount associated with the governance action
• locker_account: Account with locked tokens for governance participation
• locker_nft: NFT used for governance participation (Marinade)
• mint: Token mint address associated with the governance action

​

Columns

Column Name	Data Type	Description
PROGRAM_NAME	TEXT	The name of the Solana program that processed the governance action or transaction. This field identifies which specific governance protocol or program handled the action, enabling cross-program analysis and protocol-specific filtering.

Data type: STRING (program identifier) Business context: Used to identify governance programs and analyze cross-protocol governance patterns and adoption. Analytics use cases: Program usage analysis, cross-protocol governance comparison, and governance tool adoption tracking. Example: ‘marinade’, ‘saber’, ‘realms’ | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The timestamp (UTC) at which the block was produced on the Solana blockchain. This field is recorded as a TIMESTAMP data type and represents the precise moment the block was finalized and added to the chain. It is essential for time-series analysis, block production monitoring, and aligning transaction and event data to specific points in time. Used extensively for analytics involving block intervals, network activity trends, and historical lookups. Format: YYYY-MM-DD HH:MI:SS (UTC). | | BLOCK_ID | NUMBER | A unique identifier for the block in which this transaction was included on the Solana blockchain. Typically a sequential integer or hash, depending on the data source. Used to group transactions by block and analyze block-level activity. Example:

• 123456789

Business Context:

• Supports block-level analytics, such as block production rate and transaction throughput.
• Useful for tracing transaction inclusion and block explorer integrations.

Relationships:

• All transactions with the same ‘block_id’ share the same ‘block_timestamp’. | | TX_ID | TEXT | The unique transaction signature (hash) for each transaction on the Solana blockchain. This field is a base58-encoded string, typically 88 characters in length, and serves as the primary identifier for transactions across all Solana data models. Used to join transaction data with related tables (blocks, events, transfers, logs, decoded instructions) and to trace the full lifecycle and effects of a transaction. Essential for transaction-level analytics, debugging, and cross-referencing with block explorers or Solana APIs.

Example:

• 5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw5Nf6Q2k6v1Qw2k3v4Qw

Business Context:

• Enables precise tracking, auditing, and attribution of on-chain activity
• Used for linking transactions to events, logs, and protocol actions
• Critical for compliance, monitoring, and analytics workflows | | SUCCEEDED | BOOLEAN | Boolean flag indicating whether the transaction was successfully executed and confirmed on the Solana blockchain. A value of TRUE means the transaction was processed without errors; FALSE indicates failure due to program errors, insufficient funds, or other issues.

Example:

• true
• false

Business Context:

• Used to filter for successful transactions in analytics and reporting.
• Important for error analysis, user experience, and program debugging. | | SIGNER | TEXT | Address initiating the action | | LOCKER_ACCOUNT | TEXT | Account holding tokens for governance | | LOCKER_NFT | TEXT | NFT representing tokens for governance. This is only available for certain types of governance. | | MINT | TEXT | Mint being locked or exited | | ACTION | TEXT | NFT mint associated with the action | | AMOUNT | FLOAT | Amount being locked or exited | | FACT_GOV_ACTIONS_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. |