diff --git a/models/descriptions/columns/account_sol.md b/models/descriptions/columns/account_sol.md new file mode 100644 index 00000000..8ac3b7a1 --- /dev/null +++ b/models/descriptions/columns/account_sol.md @@ -0,0 +1,10 @@ +{% docs account_sol %} + +The SOL assigned to this vote account. This field tracks the amount of SOL held by the vote account, enabling balance analysis and validator stake assessment. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track vote account balances, analyze validator stake distribution, and assess account funding. +**Analytics use cases:** Balance tracking, stake distribution analysis, and funding assessment. +**Example:** 100.0, 1000.0, 5000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/activation_epoch.md b/models/descriptions/columns/activation_epoch.md new file mode 100644 index 00000000..9424c310 --- /dev/null +++ b/models/descriptions/columns/activation_epoch.md @@ -0,0 +1,10 @@ +{% docs activation_epoch %} + +The epoch when the stake was activated. This field tracks when the stake delegation became active and started earning rewards, enabling activation analysis and timeline tracking. + +**Data type:** INTEGER (epoch number) +**Business context:** Used to track stake activation timing, analyze delegation patterns, and measure stake lifecycle. +**Analytics use cases:** Activation timing tracking, delegation pattern analysis, and lifecycle measurement. +**Example:** 123, 456, 789 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/active_stake.md b/models/descriptions/columns/active_stake.md new file mode 100644 index 00000000..55f54956 --- /dev/null +++ b/models/descriptions/columns/active_stake.md @@ -0,0 +1,10 @@ +{% docs active_stake %} + +The active stake in SOL delegated to the validator. This field represents the total amount of SOL currently staked and actively participating in consensus for the validator. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to analyze validator stake distribution, delegation patterns, and network security assessment. +**Analytics use cases:** Validator stake distribution analysis, delegation patterns, and network security assessment. +**Example:** 1000000.0, 500000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/admin_warning.md b/models/descriptions/columns/admin_warning.md new file mode 100644 index 00000000..1ebe10b2 --- /dev/null +++ b/models/descriptions/columns/admin_warning.md @@ -0,0 +1,10 @@ +{% docs admin_warning %} + +Admin warning for the validator. This field contains any administrative warnings or alerts associated with the validator, enabling validator health monitoring and issue tracking. + +**Data type:** STRING (warning message) +**Business context:** Used to track validator issues, monitor validator health, and identify problematic validators. +**Analytics use cases:** Issue tracking, health monitoring, and problematic validator identification. +**Example:** 'High commission rate', 'Frequent delinquent periods', 'Low uptime' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/authorized_staker.md b/models/descriptions/columns/authorized_staker.md new file mode 100644 index 00000000..e5a8f819 --- /dev/null +++ b/models/descriptions/columns/authorized_staker.md @@ -0,0 +1,10 @@ +{% docs authorized_staker %} + +The account responsible for signing stake delegations and deactivations transactions. This field identifies who has control over the stake account's delegation decisions. + +**Data type:** STRING (Solana address) +**Business context:** Used to track stake authorities, analyze delegation control, and assess staking security. +**Analytics use cases:** Stake authority tracking, delegation control analysis, and staking security assessment. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/authorized_voter.md b/models/descriptions/columns/authorized_voter.md new file mode 100644 index 00000000..c8eb546a --- /dev/null +++ b/models/descriptions/columns/authorized_voter.md @@ -0,0 +1,10 @@ +{% docs authorized_voter %} + +The account responsible for signing vote transactions. This field identifies who has authority to cast votes on behalf of the vote account in network consensus. + +**Data type:** STRING (Solana address) +**Business context:** Used to track vote authorities, analyze validator voting patterns, and monitor consensus participation. +**Analytics use cases:** Vote authority tracking, validator voting analysis, and consensus participation monitoring. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/authorized_withdrawer.md b/models/descriptions/columns/authorized_withdrawer.md new file mode 100644 index 00000000..4c9db659 --- /dev/null +++ b/models/descriptions/columns/authorized_withdrawer.md @@ -0,0 +1,10 @@ +{% docs authorized_withdrawer %} + +The account responsible for signing stake withdrawal transactions. This field identifies who has authority to withdraw stake from the vote account. + +**Data type:** STRING (Solana address) +**Business context:** Used to track withdrawal authorities, analyze vote account security, and monitor withdrawal patterns. +**Analytics use cases:** Withdrawal authority tracking, vote account security analysis, and withdrawal pattern monitoring. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/avatar_url.md b/models/descriptions/columns/avatar_url.md new file mode 100644 index 00000000..a6b6815b --- /dev/null +++ b/models/descriptions/columns/avatar_url.md @@ -0,0 +1,10 @@ +{% docs avatar_url %} + +URL of the validator's avatar image. This field provides a link to the validator's profile image, enabling visual identification and branding analysis. + +**Data type:** STRING (URL) +**Business context:** Used for validator branding, visual identification, and user interface display. +**Analytics use cases:** Branding analysis, visual identification, and UI display support. +**Example:** 'https://example.com/avatar.png', 'https://keybase.io/avatar.jpg' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/claim_amount.md b/models/descriptions/columns/claim_amount.md new file mode 100644 index 00000000..fe2a4ebd --- /dev/null +++ b/models/descriptions/columns/claim_amount.md @@ -0,0 +1,10 @@ +{% docs claim_amount %} + +The amount of SOL claimed from the liquid staking protocol. This field tracks the quantity of SOL withdrawn when users claim their staking rewards or unstake, enabling claim analysis and reward tracking. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track claim amounts, analyze reward distributions, and measure unstaking activity. +**Analytics use cases:** Claim tracking, reward analysis, and unstaking measurement. +**Example:** 10.5, 105.0, 1050.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/claim_amount_usd.md b/models/descriptions/columns/claim_amount_usd.md new file mode 100644 index 00000000..936e7e37 --- /dev/null +++ b/models/descriptions/columns/claim_amount_usd.md @@ -0,0 +1,10 @@ +{% docs claim_amount_usd %} + +The amount of SOL claimed in USD value. This field provides the USD equivalent of the claimed SOL, enabling financial analysis and value-based metrics. + +**Data type:** DECIMAL (USD amount) +**Business context:** Used to track claim values, analyze financial metrics, and measure reward distributions. +**Analytics use cases:** Value tracking, financial analysis, and reward measurement. +**Example:** 105.0, 1050.0, 10500.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/commission.md b/models/descriptions/columns/commission.md new file mode 100644 index 00000000..97d3cdb3 --- /dev/null +++ b/models/descriptions/columns/commission.md @@ -0,0 +1,10 @@ +{% docs commission %} + +The percentage of rewards payout to the vote account. This field represents the fee rate that the validator charges on staking rewards, expressed as a decimal percentage. + +**Data type:** DECIMAL (percentage as decimal) +**Business context:** Used to analyze validator fee structures, model reward distributions, and study validator economics. +**Analytics use cases:** Validator fee analysis, reward distribution modeling, and validator economics studies. +**Example:** 0.05, 0.10, 0.00 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/created_at.md b/models/descriptions/columns/created_at.md new file mode 100644 index 00000000..2ce443d2 --- /dev/null +++ b/models/descriptions/columns/created_at.md @@ -0,0 +1,10 @@ +{% docs created_at %} + +The date when the validator was created. This field tracks when the validator first joined the network, enabling validator lifecycle analysis and network growth tracking. + +**Data type:** TIMESTAMP (UTC) +**Business context:** Used to track validator lifecycle, analyze network growth patterns, and assess validator experience. +**Analytics use cases:** Lifecycle tracking, growth pattern analysis, and experience assessment. +**Example:** '2023-01-15 10:30:00', '2022-06-20 14:45:30' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/credits_observed.md b/models/descriptions/columns/credits_observed.md new file mode 100644 index 00000000..cbdcc7f1 --- /dev/null +++ b/models/descriptions/columns/credits_observed.md @@ -0,0 +1,10 @@ +{% docs credits_observed %} + +Credits observed for the validator associated with this stake account. This field tracks the voting credits earned by the validator that this stake is delegated to, enabling performance analysis and reward tracking. + +**Data type:** INTEGER (credit count) +**Business context:** Used to track validator performance, analyze credit accumulation, and measure stake delegation effectiveness. +**Analytics use cases:** Performance tracking, credit accumulation analysis, and delegation effectiveness measurement. +**Example:** 1000, 5000, 10000 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/data_center_host.md b/models/descriptions/columns/data_center_host.md new file mode 100644 index 00000000..0a573e06 --- /dev/null +++ b/models/descriptions/columns/data_center_host.md @@ -0,0 +1,10 @@ +{% docs data_center_host %} + +Host information for the data center where the validator is hosted. This field provides details about the hosting infrastructure, enabling infrastructure analysis and performance monitoring. + +**Data type:** STRING (host information) +**Business context:** Used to track hosting infrastructure, analyze performance patterns, and monitor data center health. +**Analytics use cases:** Infrastructure tracking, performance analysis, and health monitoring. +**Example:** 'aws.amazon.com', 'google.com', 'microsoft.com' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/data_center_key.md b/models/descriptions/columns/data_center_key.md new file mode 100644 index 00000000..7de2b12f --- /dev/null +++ b/models/descriptions/columns/data_center_key.md @@ -0,0 +1,10 @@ +{% docs data_center_key %} + +Identifier for the data center where the validator is hosted. This field tracks the specific data center location, enabling geographic analysis and infrastructure monitoring. + +**Data type:** STRING (data center identifier) +**Business context:** Used to track validator infrastructure, analyze geographic distribution, and monitor data center performance. +**Analytics use cases:** Infrastructure tracking, geographic analysis, and performance monitoring. +**Example:** 'DC1', 'AWS_US_EAST_1', 'GCP_US_CENTRAL_1' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/deactivation_epoch.md b/models/descriptions/columns/deactivation_epoch.md new file mode 100644 index 00000000..8c0c20a6 --- /dev/null +++ b/models/descriptions/columns/deactivation_epoch.md @@ -0,0 +1,10 @@ +{% docs deactivation_epoch %} + +The epoch when the stake will be deactivated. This field tracks when the stake delegation will become inactive and stop earning rewards, enabling deactivation planning and timeline analysis. + +**Data type:** INTEGER (epoch number) +**Business context:** Used to track stake deactivation timing, analyze delegation patterns, and plan for stake lifecycle changes. +**Analytics use cases:** Deactivation timing tracking, delegation pattern analysis, and lifecycle planning. +**Example:** 123, 456, 789 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/delinquent.md b/models/descriptions/columns/delinquent.md new file mode 100644 index 00000000..0ce9848f --- /dev/null +++ b/models/descriptions/columns/delinquent.md @@ -0,0 +1,10 @@ +{% docs delinquent %} + +A boolean flag indicating whether the validator is offline or delinquent. This field tracks the operational status of validators, enabling network health monitoring and reliability analysis. + +**Data type:** BOOLEAN (TRUE/FALSE) +**Business context:** Used to monitor network health, analyze validator reliability, and track uptime performance. +**Analytics use cases:** Network health monitoring, validator reliability analysis, and uptime tracking. +**Example:** TRUE, FALSE + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/deposit_amount.md b/models/descriptions/columns/deposit_amount.md new file mode 100644 index 00000000..c00c9661 --- /dev/null +++ b/models/descriptions/columns/deposit_amount.md @@ -0,0 +1,10 @@ +{% docs deposit_amount %} + +The amount of SOL deposited into the liquid staking protocol. This field tracks the quantity of SOL being staked through Marinade Finance, enabling deposit analysis and staking volume measurement. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track staking deposits, analyze staking volume patterns, and measure protocol usage. +**Analytics use cases:** Deposit tracking, volume pattern analysis, and usage measurement. +**Example:** 10.0, 100.0, 1000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/deposit_amount_usd.md b/models/descriptions/columns/deposit_amount_usd.md new file mode 100644 index 00000000..1ef4a3bf --- /dev/null +++ b/models/descriptions/columns/deposit_amount_usd.md @@ -0,0 +1,10 @@ +{% docs deposit_amount_usd %} + +The amount of SOL deposited in USD value. This field provides the USD equivalent of the deposited SOL, enabling financial analysis and value-based metrics. + +**Data type:** DECIMAL (USD amount) +**Business context:** Used to track deposit values, analyze financial metrics, and measure protocol TVL impact. +**Analytics use cases:** Value tracking, financial analysis, and TVL impact measurement. +**Example:** 100.0, 1000.0, 10000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/details.md b/models/descriptions/columns/details.md new file mode 100644 index 00000000..8af9cae9 --- /dev/null +++ b/models/descriptions/columns/details.md @@ -0,0 +1,10 @@ +{% docs details %} + +Additional details for the validator. This field contains supplementary information about the validator, enabling comprehensive validator analysis and metadata tracking. + +**Data type:** STRING (details text) +**Business context:** Used to store additional validator information, track metadata, and provide comprehensive validator context. +**Analytics use cases:** Metadata tracking, comprehensive analysis, and context provision. +**Example:** 'Professional validator with 99.9% uptime', 'Community validator focused on decentralization' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/dex_platform.md b/models/descriptions/columns/dex_platform.md new file mode 100644 index 00000000..82b42ea2 --- /dev/null +++ b/models/descriptions/columns/dex_platform.md @@ -0,0 +1,10 @@ +{% docs dex_platform %} + +Name of the decentralized exchange used to perform the swap. This field identifies the specific DEX or aggregator platform that facilitated the swap, enabling cross-platform analysis and platform-specific comparisons. + +**Data type:** STRING (platform name) +**Business context:** Used to categorize swaps by platform, analyze cross-platform trading patterns, and compare platform performance. +**Analytics use cases:** Platform categorization, cross-platform analysis, and performance comparison. +**Example:** 'Jupiter', 'Raydium', 'Orca', 'Meteora' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/end_slot.md b/models/descriptions/columns/end_slot.md new file mode 100644 index 00000000..01eba351 --- /dev/null +++ b/models/descriptions/columns/end_slot.md @@ -0,0 +1,10 @@ +{% docs end_slot %} + +The final slot of the epoch. This field identifies the ending slot number for the epoch, enabling epoch boundary tracking and time-based analysis. + +**Data type:** INTEGER (slot number) +**Business context:** Used to track epoch boundaries, analyze time-based patterns, and provide epoch context for block production data. +**Analytics use cases:** Epoch boundary tracking, time-based analysis, and epoch context provision. +**Example:** 123456789, 123456800 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/epoch_active.md b/models/descriptions/columns/epoch_active.md new file mode 100644 index 00000000..d9b341ea --- /dev/null +++ b/models/descriptions/columns/epoch_active.md @@ -0,0 +1,10 @@ +{% docs epoch_active %} + +The last epoch when the vote account was active. This field tracks the most recent epoch in which the validator's vote account participated in consensus voting, enabling activity analysis and validator health assessment. + +**Data type:** INTEGER (epoch number) +**Business context:** Used to track validator activity, analyze participation patterns, and assess validator health and reliability. +**Analytics use cases:** Activity tracking, participation analysis, and health assessment. +**Example:** 123, 456, 789 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/epoch_credits.md b/models/descriptions/columns/epoch_credits.md new file mode 100644 index 00000000..62340ee3 --- /dev/null +++ b/models/descriptions/columns/epoch_credits.md @@ -0,0 +1,10 @@ +{% docs epoch_credits %} + +Credits earned by the end of epochs, containing epoch/credits/previous credits. This field tracks the cumulative voting credits earned by the vote account across epochs, enabling validator performance analysis and reward calculation. + +**Data type:** STRING (credits data) +**Business context:** Used to track validator voting performance, analyze credit accumulation patterns, and calculate voting rewards. +**Analytics use cases:** Validator performance analysis, credit accumulation tracking, and voting reward calculation. +**Example:** "123/1000/500", "456/1500/1000" + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/governance_platform.md b/models/descriptions/columns/governance_platform.md new file mode 100644 index 00000000..9ebe4b9e --- /dev/null +++ b/models/descriptions/columns/governance_platform.md @@ -0,0 +1,10 @@ +{% docs governance_platform %} + +The platform used for governance space and voting mechanisms. This field identifies which governance platform hosted the voting activity, enabling cross-platform analysis and platform adoption tracking. + +**Data type:** STRING (platform identifier) +**Business context:** Used to identify governance platforms and analyze cross-platform governance patterns and tool adoption. +**Analytics use cases:** Platform adoption analysis, cross-platform governance comparison, and governance tool effectiveness studies. +**Example:** 'realms', 'tribeca' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/is_mnde_pool.md b/models/descriptions/columns/is_mnde_pool.md new file mode 100644 index 00000000..f6cb76e5 --- /dev/null +++ b/models/descriptions/columns/is_mnde_pool.md @@ -0,0 +1,10 @@ +{% docs is_mnde_pool %} + +Whether the pool has MNDE as one of the tokens. This field indicates if the liquidity pool contains Marinade Finance governance token (MNDE) as a trading pair, enabling MNDE-specific pool filtering and analysis. + +**Data type:** BOOLEAN (true/false) +**Business context:** Used to filter MNDE-related pools, analyze MNDE liquidity distribution, and track MNDE trading opportunities. +**Analytics use cases:** MNDE pool filtering, liquidity distribution analysis, and trading opportunity tracking. +**Example:** true, false + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/is_msol_pool.md b/models/descriptions/columns/is_msol_pool.md new file mode 100644 index 00000000..891cd629 --- /dev/null +++ b/models/descriptions/columns/is_msol_pool.md @@ -0,0 +1,10 @@ +{% docs is_msol_pool %} + +Whether the pool has MSOL as one of the tokens. This field indicates if the liquidity pool contains Marinade Staked SOL (MSOL) as a trading pair, enabling MSOL-specific pool filtering and analysis. + +**Data type:** BOOLEAN (true/false) +**Business context:** Used to filter MSOL-related pools, analyze MSOL liquidity distribution, and track MSOL trading opportunities. +**Analytics use cases:** MSOL pool filtering, liquidity distribution analysis, and trading opportunity tracking. +**Example:** true, false + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/is_using_marinade_native_staking.md b/models/descriptions/columns/is_using_marinade_native_staking.md new file mode 100644 index 00000000..7a4edae6 --- /dev/null +++ b/models/descriptions/columns/is_using_marinade_native_staking.md @@ -0,0 +1,10 @@ +{% docs is_using_marinade_native_staking %} + +Whether the staking action is using Marinade Native Staking. This field indicates if the staking activity is routed through Marinade's native staking proxy service, enabling proxy service usage analysis. + +**Data type:** BOOLEAN (true/false) +**Business context:** Used to track Marinade proxy service usage, analyze proxy adoption patterns, and measure service utilization. +**Analytics use cases:** Usage tracking, adoption analysis, and utilization measurement. +**Example:** true, false + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/keybase_id.md b/models/descriptions/columns/keybase_id.md new file mode 100644 index 00000000..b778d190 --- /dev/null +++ b/models/descriptions/columns/keybase_id.md @@ -0,0 +1,10 @@ +{% docs keybase_id %} + +Keybase ID for the validator. This field provides the validator's Keybase identity, enabling social verification and community engagement analysis. + +**Data type:** STRING (Keybase username) +**Business context:** Used for social verification, community engagement tracking, and validator identity verification. +**Analytics use cases:** Social verification, engagement tracking, and identity verification. +**Example:** 'validator_name', 'solana_validator', 'community_node' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/last_epoch_active.md b/models/descriptions/columns/last_epoch_active.md new file mode 100644 index 00000000..b044053e --- /dev/null +++ b/models/descriptions/columns/last_epoch_active.md @@ -0,0 +1,10 @@ +{% docs last_epoch_active %} + +The last epoch when the vote account was active. This field tracks the most recent epoch in which the vote account participated in consensus voting, enabling activity analysis and validator health assessment. + +**Data type:** INTEGER (epoch number) +**Business context:** Used to track vote account activity, analyze validator participation patterns, and assess validator health and reliability. +**Analytics use cases:** Vote account activity tracking, validator participation analysis, and health assessment. +**Example:** 123, 456, 789 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/last_timestamp.md b/models/descriptions/columns/last_timestamp.md new file mode 100644 index 00000000..df5a5cc3 --- /dev/null +++ b/models/descriptions/columns/last_timestamp.md @@ -0,0 +1,10 @@ +{% docs last_timestamp %} + +The timestamp when the last slot was voted on. This field captures the exact time when the vote account last participated in consensus voting, enabling temporal analysis and activity tracking. + +**Data type:** TIMESTAMP (UTC) +**Business context:** Used to track vote account activity timing, analyze voting frequency patterns, and assess validator reliability over time. +**Analytics use cases:** Activity timing analysis, voting frequency tracking, and reliability assessment. +**Example:** '2024-01-15 10:30:00', '2024-01-15 14:45:30' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/last_timestamp_slot.md b/models/descriptions/columns/last_timestamp_slot.md new file mode 100644 index 00000000..6405c155 --- /dev/null +++ b/models/descriptions/columns/last_timestamp_slot.md @@ -0,0 +1,10 @@ +{% docs last_timestamp_slot %} + +The last slot voted on by the vote account. This field tracks the most recent slot number where the vote account participated in consensus voting, enabling activity tracking and performance analysis. + +**Data type:** INTEGER (slot number) +**Business context:** Used to track vote account activity, analyze voting patterns, and assess validator participation in consensus. +**Analytics use cases:** Vote account activity tracking, voting pattern analysis, and consensus participation assessment. +**Example:** 123456789, 123456800 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/latitude.md b/models/descriptions/columns/latitude.md new file mode 100644 index 00000000..be4c96a8 --- /dev/null +++ b/models/descriptions/columns/latitude.md @@ -0,0 +1,10 @@ +{% docs latitude %} + +Latitude coordinates of the data center where the validator is hosted. This field provides geographic location data, enabling geographic analysis and infrastructure distribution studies. + +**Data type:** DECIMAL (latitude degrees) +**Business context:** Used to track geographic distribution, analyze infrastructure patterns, and study validator clustering. +**Analytics use cases:** Geographic analysis, infrastructure pattern study, and clustering analysis. +**Example:** 40.7128, 34.0522, 51.5074 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/lockup.md b/models/descriptions/columns/lockup.md new file mode 100644 index 00000000..4af551f7 --- /dev/null +++ b/models/descriptions/columns/lockup.md @@ -0,0 +1,10 @@ +{% docs lockup %} + +Lockup information specifying when tokens can be withdrawn from the stake account. This field contains the lockup conditions including epoch, timestamp, and custodian restrictions, enabling withdrawal analysis and lockup tracking. + +**Data type:** OBJECT (lockup data) +**Business context:** Used to track withdrawal restrictions, analyze lockup conditions, and monitor stake account liquidity. +**Analytics use cases:** Withdrawal restriction tracking, lockup condition analysis, and liquidity monitoring. +**Example:** {'epoch': 123, 'unix_timestamp': 1642233600, 'custodian': 'CustodianAddress'} + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/longitude.md b/models/descriptions/columns/longitude.md new file mode 100644 index 00000000..ea9fc0ae --- /dev/null +++ b/models/descriptions/columns/longitude.md @@ -0,0 +1,10 @@ +{% docs longitude %} + +Longitude coordinates of the data center where the validator is hosted. This field provides geographic location data, enabling geographic analysis and infrastructure distribution studies. + +**Data type:** DECIMAL (longitude degrees) +**Business context:** Used to track geographic distribution, analyze infrastructure patterns, and study validator clustering. +**Analytics use cases:** Geographic analysis, infrastructure pattern study, and clustering analysis. +**Example:** -74.0060, -118.2437, -0.1278 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/move_amount.md b/models/descriptions/columns/move_amount.md new file mode 100644 index 00000000..263c5e8b --- /dev/null +++ b/models/descriptions/columns/move_amount.md @@ -0,0 +1,10 @@ +{% docs move_amount %} + +The amount of SOL being moved from the stake account. This field captures the quantity of SOL involved in the staking action, enabling transaction value analysis and movement tracking. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track SOL movements, analyze transaction values, and measure staking activity volume. +**Analytics use cases:** Transaction value analysis, movement tracking, and staking activity volume measurement. +**Example:** 50.0, 100.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/move_destination.md b/models/descriptions/columns/move_destination.md new file mode 100644 index 00000000..68ee3916 --- /dev/null +++ b/models/descriptions/columns/move_destination.md @@ -0,0 +1,10 @@ +{% docs move_destination %} + +The destination wallet address of the moved SOL. This field identifies where the SOL was transferred to during the staking action, enabling movement tracking and destination analysis. + +**Data type:** STRING (Solana address) +**Business context:** Used to track SOL movement destinations, analyze transfer patterns, and identify stake recipients. +**Analytics use cases:** Movement destination tracking, transfer pattern analysis, and stake recipient identification. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/msol_burned.md b/models/descriptions/columns/msol_burned.md new file mode 100644 index 00000000..25772722 --- /dev/null +++ b/models/descriptions/columns/msol_burned.md @@ -0,0 +1,10 @@ +{% docs msol_burned %} + +The amount of MSOL (Marinade Staked SOL) burned. This field tracks the quantity of MSOL tokens destroyed when users unstake or claim rewards, enabling MSOL supply analysis. + +**Data type:** DECIMAL (MSOL amount) +**Business context:** Used to track MSOL burning, analyze supply reduction, and measure unstaking activity. +**Analytics use cases:** Burning tracking, supply analysis, and unstaking activity measurement. +**Example:** 9.95, 99.5, 995.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/msol_minted.md b/models/descriptions/columns/msol_minted.md new file mode 100644 index 00000000..426b851b --- /dev/null +++ b/models/descriptions/columns/msol_minted.md @@ -0,0 +1,10 @@ +{% docs msol_minted %} + +The amount of MSOL (Marinade Staked SOL) minted. This field tracks the quantity of MSOL tokens created when SOL is deposited into the liquid staking protocol, enabling MSOL supply analysis. + +**Data type:** DECIMAL (MSOL amount) +**Business context:** Used to track MSOL minting, analyze supply growth, and measure staking efficiency. +**Analytics use cases:** Minting tracking, supply analysis, and efficiency measurement. +**Example:** 9.95, 99.5, 995.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/native_staking_platform.md b/models/descriptions/columns/native_staking_platform.md new file mode 100644 index 00000000..574755ab --- /dev/null +++ b/models/descriptions/columns/native_staking_platform.md @@ -0,0 +1,10 @@ +{% docs native_staking_platform %} + +The platform of the staking account, either native or marinade native proxy. This field identifies whether the staking action is using direct native staking or Marinade's native staking proxy service, enabling platform-specific analysis. + +**Data type:** STRING (platform type) +**Business context:** Used to categorize staking methods, analyze platform usage patterns, and compare native vs proxy staking. +**Analytics use cases:** Platform categorization, usage pattern analysis, and method comparison. +**Example:** 'native', 'marinade native proxy' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/node_pubkey.md b/models/descriptions/columns/node_pubkey.md new file mode 100644 index 00000000..a0d42abc --- /dev/null +++ b/models/descriptions/columns/node_pubkey.md @@ -0,0 +1,10 @@ +{% docs node_pubkey %} + +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' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/num_blocks_produced.md b/models/descriptions/columns/num_blocks_produced.md new file mode 100644 index 00000000..be17040d --- /dev/null +++ b/models/descriptions/columns/num_blocks_produced.md @@ -0,0 +1,10 @@ +{% docs num_blocks_produced %} + +The number of blocks the validator produced in the epoch. This field tracks the actual blocks created by the validator when it was the slot leader, enabling block production analysis and validator efficiency measurement. + +**Data type:** INTEGER (block count) +**Business context:** Used to analyze validator block production efficiency, track network performance, and measure validator reliability. +**Analytics use cases:** Block production analysis, network performance tracking, and validator efficiency measurement. +**Example:** 8, 45, 95 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/num_leader_slots.md b/models/descriptions/columns/num_leader_slots.md new file mode 100644 index 00000000..af07e0d1 --- /dev/null +++ b/models/descriptions/columns/num_leader_slots.md @@ -0,0 +1,10 @@ +{% docs num_leader_slots %} + +The number of slots the validator was the leader for in the epoch. This field tracks how many times the validator was selected as the slot leader, enabling validator performance analysis and network participation measurement. + +**Data type:** INTEGER (slot count) +**Business context:** Used to analyze validator performance, track network participation, and measure validator reliability. +**Analytics use cases:** Validator performance analysis, network participation tracking, and reliability measurement. +**Example:** 10, 50, 100 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/num_votes.md b/models/descriptions/columns/num_votes.md new file mode 100644 index 00000000..4c063437 --- /dev/null +++ b/models/descriptions/columns/num_votes.md @@ -0,0 +1,10 @@ +{% docs num_votes %} + +The number of vote events that occurred within the block. This field tracks the count of voting transactions processed in a specific block, enabling consensus participation analysis and block-level voting activity measurement. + +**Data type:** INTEGER (vote count) +**Business context:** Used to analyze consensus participation patterns, track voting activity by block, and measure network consensus health. +**Analytics use cases:** Consensus participation analysis, voting activity tracking, and network consensus health measurement. +**Example:** 5, 10, 20 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/platform.md b/models/descriptions/columns/platform.md new file mode 100644 index 00000000..84ad8369 --- /dev/null +++ b/models/descriptions/columns/platform.md @@ -0,0 +1,10 @@ +{% docs platform %} + +Name of the liquidity pool protocol or platform. This field identifies the DeFi protocol that hosts the liquidity pool, enabling cross-protocol analysis and platform-specific comparisons. + +**Data type:** STRING (platform name) +**Business context:** Used to categorize pools by protocol, analyze cross-platform liquidity distribution, and compare platform performance. +**Analytics use cases:** Platform categorization, cross-protocol analysis, and performance comparison. +**Example:** 'raydium', 'orca', 'meteora' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/pool_name.md b/models/descriptions/columns/pool_name.md new file mode 100644 index 00000000..fc4cb270 --- /dev/null +++ b/models/descriptions/columns/pool_name.md @@ -0,0 +1,10 @@ +{% docs pool_name %} + +The name of the liquidity pool, typically formatted as a token pair (e.g., "MSOL-USDC"). This field provides a human-readable identifier for the pool, enabling easy identification and analysis of specific liquidity pools. + +**Data type:** STRING (pool name) +**Business context:** Used to identify liquidity pools, analyze pool naming patterns, and provide user-friendly pool references. +**Analytics use cases:** Pool identification, naming pattern analysis, and user interface display. +**Example:** 'MSOL-USDC', 'MNDE-SOL', 'MSOL-RAY' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/post_balances.md b/models/descriptions/columns/post_balances.md index 16de801a..2b4e1107 100644 --- a/models/descriptions/columns/post_balances.md +++ b/models/descriptions/columns/post_balances.md @@ -1,3 +1,10 @@ {% docs post_balances %} -An array of lamport balances for each account in 'account_keys' after the transaction is executed. The order matches the 'account_keys' array. Used to track balance changes and verify transaction effects. Value is in lamports (1 SOL = 1,000,000,000 lamports). + +List of post-transaction balances for different accounts. This field captures the SOL balances of all accounts involved in the transaction after execution, enabling balance change analysis and transaction impact measurement. + +**Data type:** ARRAY (SOL amounts) +**Business context:** Used to track balance changes, analyze transaction impact, and measure SOL movement between accounts. +**Analytics use cases:** Balance change analysis, transaction impact measurement, and SOL movement tracking. +**Example:** [95.0, 55.0, 25.0] + {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/post_token_balances.md b/models/descriptions/columns/post_token_balances.md index 195cf07b..ab2df821 100644 --- a/models/descriptions/columns/post_token_balances.md +++ b/models/descriptions/columns/post_token_balances.md @@ -1,3 +1,10 @@ {% docs post_token_balances %} -An array of SPL token balances for each token account involved in the transaction, after execution. Each entry includes the token account address, mint, and raw amount. Used to track token transfers and verify effects. See: https://spl.solana.com/token + +List of post-transaction token balances for different token accounts. This field captures the token balances of all token accounts involved in the transaction after execution, enabling token balance change analysis. + +**Data type:** ARRAY (token balance objects) +**Business context:** Used to track token balance changes, analyze token movements, and measure token transaction impact. +**Analytics use cases:** Token balance change analysis, token movement tracking, and token transaction impact measurement. +**Example:** [{'mint': 'TokenMintAddress', 'amount': 900}, {'mint': 'AnotherToken', 'amount': 600}] + {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/post_tx_staked_balance.md b/models/descriptions/columns/post_tx_staked_balance.md new file mode 100644 index 00000000..6dcddef4 --- /dev/null +++ b/models/descriptions/columns/post_tx_staked_balance.md @@ -0,0 +1,10 @@ +{% docs post_tx_staked_balance %} + +The amount of Solana belonging to the stake account after the transaction. This field captures the stake balance following the staking action, enabling balance change analysis and transaction impact measurement. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track stake balance changes, analyze transaction impact, and measure staking activity. +**Analytics use cases:** Balance change analysis, transaction impact measurement, and staking activity tracking. +**Example:** 100.0, 1000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/post_tx_staked_balance_usd.md b/models/descriptions/columns/post_tx_staked_balance_usd.md new file mode 100644 index 00000000..e807e698 --- /dev/null +++ b/models/descriptions/columns/post_tx_staked_balance_usd.md @@ -0,0 +1,10 @@ +{% docs post_tx_staked_balance_usd %} + +The amount of SOL belonging to the stake account after the transaction in USD value. This field provides the USD equivalent of the post-transaction stake balance, enabling financial analysis and value-based metrics. + +**Data type:** DECIMAL (USD amount) +**Business context:** Used to track post-transaction values, analyze financial metrics, and measure balance changes in USD terms. +**Analytics use cases:** Value tracking, financial analysis, and USD-based balance measurement. +**Example:** 95.0, 1050.0, 10050.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/pre_balances.md b/models/descriptions/columns/pre_balances.md index e3f392bd..fcb6a306 100644 --- a/models/descriptions/columns/pre_balances.md +++ b/models/descriptions/columns/pre_balances.md @@ -1,3 +1,10 @@ {% docs pre_balances %} -An array of lamport balances for each account in 'account_keys' before the transaction is executed. The order matches the 'account_keys' array. Used to track balance changes and verify transaction effects. Value is in lamports (1 SOL = 1,000,000,000 lamports). + +List of pre-transaction balances for different accounts. This field captures the SOL balances of all accounts involved in the transaction before execution, enabling balance change analysis and transaction impact measurement. + +**Data type:** ARRAY (SOL amounts) +**Business context:** Used to track balance changes, analyze transaction impact, and measure SOL movement between accounts. +**Analytics use cases:** Balance change analysis, transaction impact measurement, and SOL movement tracking. +**Example:** [100.0, 50.0, 25.0] + {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/pre_token_balances.md b/models/descriptions/columns/pre_token_balances.md index a00efa90..f6f3a45e 100644 --- a/models/descriptions/columns/pre_token_balances.md +++ b/models/descriptions/columns/pre_token_balances.md @@ -1,3 +1,10 @@ {% docs pre_token_balances %} -An array of SPL token balances for each token account involved in the transaction, before execution. Each entry includes the token account address, mint, and raw amount. Used to track token transfers and verify effects. See: https://spl.solana.com/token + +List of pre-transaction token balances for different token accounts. This field captures the token balances of all token accounts involved in the transaction before execution, enabling token balance change analysis. + +**Data type:** ARRAY (token balance objects) +**Business context:** Used to track token balance changes, analyze token movements, and measure token transaction impact. +**Analytics use cases:** Token balance change analysis, token movement tracking, and token transaction impact measurement. +**Example:** [{'mint': 'TokenMintAddress', 'amount': 1000}, {'mint': 'AnotherToken', 'amount': 500}] + {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/pre_tx_staked_balance.md b/models/descriptions/columns/pre_tx_staked_balance.md new file mode 100644 index 00000000..0bef443e --- /dev/null +++ b/models/descriptions/columns/pre_tx_staked_balance.md @@ -0,0 +1,10 @@ +{% docs pre_tx_staked_balance %} + +The amount of Solana belonging to the stake account before the transaction. This field captures the stake balance prior to the staking action, enabling balance change analysis and transaction impact measurement. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track stake balance changes, analyze transaction impact, and measure staking activity. +**Analytics use cases:** Balance change analysis, transaction impact measurement, and staking activity tracking. +**Example:** 100.0, 1000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/pre_tx_staked_balance_usd.md b/models/descriptions/columns/pre_tx_staked_balance_usd.md new file mode 100644 index 00000000..f17f4690 --- /dev/null +++ b/models/descriptions/columns/pre_tx_staked_balance_usd.md @@ -0,0 +1,10 @@ +{% docs pre_tx_staked_balance_usd %} + +The amount of SOL belonging to the stake account before the transaction in USD value. This field provides the USD equivalent of the pre-transaction stake balance, enabling financial analysis and value-based metrics. + +**Data type:** DECIMAL (USD amount) +**Business context:** Used to track pre-transaction values, analyze financial metrics, and measure balance changes in USD terms. +**Analytics use cases:** Value tracking, financial analysis, and USD-based balance measurement. +**Example:** 100.0, 1000.0, 10000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/prior_voters.md b/models/descriptions/columns/prior_voters.md new file mode 100644 index 00000000..fe73561a --- /dev/null +++ b/models/descriptions/columns/prior_voters.md @@ -0,0 +1,10 @@ +{% docs prior_voters %} + +Prior voters for the vote account. This field tracks the historical list of voters that have been associated with this vote account, enabling voter history analysis and account ownership tracking. + +**Data type:** ARRAY (voter addresses) +**Business context:** Used to track vote account ownership history, analyze voter transitions, and understand account control changes. +**Analytics use cases:** Ownership history tracking, voter transition analysis, and account control change monitoring. +**Example:** ['PreviousVoter1', 'PreviousVoter2'], ['OldVoterAddress'] + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/program.md b/models/descriptions/columns/program.md new file mode 100644 index 00000000..2af0a85c --- /dev/null +++ b/models/descriptions/columns/program.md @@ -0,0 +1,10 @@ +{% docs program %} + +The type of account program that owns this stake account. This field identifies the Solana program that has authority over the stake account, enabling ownership analysis and program relationship tracking. + +**Data type:** STRING (program address) +**Business context:** Used to track stake account ownership, analyze program relationships, and understand account control structures. +**Analytics use cases:** Ownership tracking, program relationship analysis, and control structure understanding. +**Example:** 'Stake111111111111111111111111111111111111111111' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/program_name.md b/models/descriptions/columns/program_name.md new file mode 100644 index 00000000..6d2e8f9d --- /dev/null +++ b/models/descriptions/columns/program_name.md @@ -0,0 +1,10 @@ +{% docs program_name %} + +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' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/proposal.md b/models/descriptions/columns/proposal.md new file mode 100644 index 00000000..418f5eda --- /dev/null +++ b/models/descriptions/columns/proposal.md @@ -0,0 +1,10 @@ +{% docs proposal %} + +Address representing the proposal being voted on. This field identifies the specific proposal within the governance system, enabling proposal tracking and governance activity analysis. + +**Data type:** STRING (proposal address) +**Business context:** Used to track individual proposals, analyze proposal lifecycle, and monitor governance activity. +**Analytics use cases:** Proposal tracking, lifecycle analysis, and governance activity monitoring. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/proposal_name.md b/models/descriptions/columns/proposal_name.md new file mode 100644 index 00000000..0f562397 --- /dev/null +++ b/models/descriptions/columns/proposal_name.md @@ -0,0 +1,10 @@ +{% docs proposal_name %} + +The name of the proposal that is being submitted. This field contains the human-readable title or name of the governance proposal, enabling proposal identification and content analysis. + +**Data type:** STRING (proposal name) +**Business context:** Used to identify proposals, analyze proposal content themes, and categorize governance topics. +**Analytics use cases:** Proposal identification, content theme analysis, and topic categorization. +**Example:** 'Increase Treasury Allocation', 'Update Protocol Parameters', 'Community Grant Proposal' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/proposal_writer.md b/models/descriptions/columns/proposal_writer.md new file mode 100644 index 00000000..2f32bdd3 --- /dev/null +++ b/models/descriptions/columns/proposal_writer.md @@ -0,0 +1,10 @@ +{% docs proposal_writer %} + +Address of the user who is submitting the proposal for voting. This field identifies the creator of the governance proposal, enabling creator analysis and proposal attribution tracking. + +**Data type:** STRING (user address) +**Business context:** Used to track proposal creators, analyze creator patterns, and attribute governance activity to specific users. +**Analytics use cases:** Creator tracking, pattern analysis, and activity attribution. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/realms_id.md b/models/descriptions/columns/realms_id.md new file mode 100644 index 00000000..31d6daab --- /dev/null +++ b/models/descriptions/columns/realms_id.md @@ -0,0 +1,10 @@ +{% docs realms_id %} + +An address that is unique to the space or voting group on Realms. This field identifies the specific governance space within the Realms platform where the proposal is being created, enabling governance space analysis and proposal categorization. + +**Data type:** STRING (Realms address) +**Business context:** Used to track governance spaces, analyze proposal distribution across spaces, and categorize governance activity. +**Analytics use cases:** Governance space tracking, proposal distribution analysis, and activity categorization. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/rent_epoch.md b/models/descriptions/columns/rent_epoch.md new file mode 100644 index 00000000..577857e4 --- /dev/null +++ b/models/descriptions/columns/rent_epoch.md @@ -0,0 +1,10 @@ +{% docs rent_epoch %} + +The epoch at which this account will next owe rent. This field tracks when the vote account will be charged rent for storage, enabling rent management analysis and account maintenance planning. + +**Data type:** INTEGER (epoch number) +**Business context:** Used to track rent obligations, analyze account maintenance costs, and plan for rent payments. +**Analytics use cases:** Rent obligation tracking, maintenance cost analysis, and payment planning. +**Example:** 123, 456, 789 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/rent_exempt_reserve.md b/models/descriptions/columns/rent_exempt_reserve.md new file mode 100644 index 00000000..d79ebee8 --- /dev/null +++ b/models/descriptions/columns/rent_exempt_reserve.md @@ -0,0 +1,10 @@ +{% docs rent_exempt_reserve %} + +The minimum SOL balance that must be maintained for this account to remain rent exempt. This field tracks the required SOL amount to avoid rent charges, enabling cost analysis and account maintenance planning. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track rent exemption requirements, analyze account maintenance costs, and plan for rent payments. +**Analytics use cases:** Rent exemption tracking, maintenance cost analysis, and payment planning. +**Example:** 0.00203928, 0.00144768 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/reward_recipient_pubkey.md b/models/descriptions/columns/reward_recipient_pubkey.md new file mode 100644 index 00000000..54691d0c --- /dev/null +++ b/models/descriptions/columns/reward_recipient_pubkey.md @@ -0,0 +1,10 @@ +{% docs reward_recipient_pubkey %} + +The address receiving the fee rewards. This field identifies the account that received the fee reward, enabling reward distribution analysis and recipient tracking. + +**Data type:** STRING (Solana address) +**Business context:** Used to track reward recipients, analyze reward distribution patterns, and identify fee reward beneficiaries. +**Analytics use cases:** Reward distribution analysis, recipient tracking, and fee reward beneficiary identification. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/root_slot.md b/models/descriptions/columns/root_slot.md new file mode 100644 index 00000000..69256936 --- /dev/null +++ b/models/descriptions/columns/root_slot.md @@ -0,0 +1,10 @@ +{% docs root_slot %} + +The latest slot confirmed by the vote account. This field tracks the most recent slot that the vote account has confirmed as part of the consensus process, enabling confirmation analysis and network health assessment. + +**Data type:** INTEGER (slot number) +**Business context:** Used to track vote account confirmation activity, analyze consensus participation, and assess network health. +**Analytics use cases:** Confirmation activity tracking, consensus participation analysis, and network health assessment. +**Example:** 123456789, 123456800 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/signers.md b/models/descriptions/columns/signers.md index 20c145b9..0329329d 100644 --- a/models/descriptions/columns/signers.md +++ b/models/descriptions/columns/signers.md @@ -1,14 +1,10 @@ {% docs signers %} -An array of account addresses that have signed the transaction, authorizing its execution on the Solana blockchain. Each signer is a base58-encoded public key. Signers are required for transaction validity and may include the fee payer and other accounts with write permissions. The order of signers matches their appearance in the transaction's account_keys array. For more details, see: https://docs.solana.com/developing/programming-model/accounts#signers -**Example:** -- ["3N5k...", "7G8h..."] +List of accounts that signed the transaction. This field captures all wallet addresses that provided signatures for the transaction, enabling multi-signature analysis and transaction authority tracking. -**Business Context:** -- Used to verify transaction authorization and trace which accounts initiated or approved actions. -- Important for analytics on user activity, multisig wallets, and program interactions. +**Data type:** ARRAY (list of Solana addresses) +**Business context:** Used to track transaction signers, analyze multi-signature patterns, and identify transaction authorities. +**Analytics use cases:** Multi-signature analysis, transaction authority tracking, and signer pattern studies. +**Example:** ['9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM', 'AnotherAddress...'] -**Relationships:** -- Subset of the 'account_keys' array. -- The first signer is typically the fee payer. {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/software_version.md b/models/descriptions/columns/software_version.md new file mode 100644 index 00000000..e52b9bd0 --- /dev/null +++ b/models/descriptions/columns/software_version.md @@ -0,0 +1,10 @@ +{% docs software_version %} + +The Solana mainnet version running on the validator. This field tracks which software version the validator is operating, enabling network upgrade monitoring and compatibility analysis. + +**Data type:** STRING (version number) +**Business context:** Used to track network upgrades, analyze version adoption patterns, and monitor compatibility across the network. +**Analytics use cases:** Network upgrade tracking, version adoption analysis, and compatibility monitoring. +**Example:** '1.17.0', '1.16.0' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_account.md b/models/descriptions/columns/stake_account.md index b7071a8e..adbb918e 100644 --- a/models/descriptions/columns/stake_account.md +++ b/models/descriptions/columns/stake_account.md @@ -1,5 +1,10 @@ {% docs stake_account %} -An account address containing balances of staked SOL. +The address of the stake account. This field identifies the specific account that holds staked SOL and participates in the staking system. + +**Data type:** STRING (Solana address) +**Business context:** Used to track stake accounts, analyze delegation patterns, and measure staking participation. +**Analytics use cases:** Stake account tracking, delegation analysis, and staking participation measurement. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_account_sol.md b/models/descriptions/columns/stake_account_sol.md new file mode 100644 index 00000000..2b88ff14 --- /dev/null +++ b/models/descriptions/columns/stake_account_sol.md @@ -0,0 +1,10 @@ +{% docs stake_account_sol %} + +The SOL held in this stake account. This field tracks the total SOL balance in the stake account, enabling balance analysis and stake amount tracking. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track stake account balances, analyze stake amounts, and assess account funding. +**Analytics use cases:** Balance tracking, stake amount analysis, and funding assessment. +**Example:** 100.0, 1000.0, 5000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_active.md b/models/descriptions/columns/stake_active.md new file mode 100644 index 00000000..85fe0bb4 --- /dev/null +++ b/models/descriptions/columns/stake_active.md @@ -0,0 +1,10 @@ +{% docs stake_active %} + +Whether the stake account is active. This field indicates if the stake account is currently participating in staking and earning rewards, enabling stake status analysis and active stake tracking. + +**Data type:** BOOLEAN (true/false) +**Business context:** Used to track stake account status, analyze active stake patterns, and measure staking participation. +**Analytics use cases:** Status tracking, pattern analysis, and participation measurement. +**Example:** true, false + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_authority.md b/models/descriptions/columns/stake_authority.md index dc3de6a4..18f48829 100644 --- a/models/descriptions/columns/stake_authority.md +++ b/models/descriptions/columns/stake_authority.md @@ -1,5 +1,10 @@ {% docs stake_authority %} -The authority that can perform staking related actions on the stake account except for withdrawing. +The wallet address of the user who initialized the transaction. This field identifies the account that has authority over the stake account and initiated the staking action. + +**Data type:** STRING (Solana address) +**Business context:** Used to track stake authorities, analyze user staking behavior, and identify transaction initiators. +**Analytics use cases:** Stake authority tracking, user staking behavior analysis, and transaction initiation patterns. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_balance.md b/models/descriptions/columns/stake_balance.md new file mode 100644 index 00000000..63742729 --- /dev/null +++ b/models/descriptions/columns/stake_balance.md @@ -0,0 +1,10 @@ +{% docs stake_balance %} + +The amount staked in SOL. This field represents the total value of SOL currently staked in the account, enabling staking amount analysis and delegation value tracking. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to analyze staking amounts, track delegation values, and measure staking participation levels. +**Analytics use cases:** Staking amount analysis, delegation value tracking, and staking participation measurement. +**Example:** 100.0, 1000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/stake_type.md b/models/descriptions/columns/stake_type.md new file mode 100644 index 00000000..1c2290a9 --- /dev/null +++ b/models/descriptions/columns/stake_type.md @@ -0,0 +1,10 @@ +{% docs stake_type %} + +The status of the stake (active, inactive, activating, deactivating). This field tracks the current state of the stake in the staking lifecycle, enabling stake lifecycle analysis and behavior tracking. + +**Data type:** STRING (stake status) +**Business context:** Used to analyze stake lifecycles, track activation/deactivation patterns, and monitor staking behavior. +**Analytics use cases:** Stake lifecycle analysis, activation/deactivation patterns, and staking behavior tracking. +**Example:** 'active', 'inactive', 'activating', 'deactivating' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/start_slot.md b/models/descriptions/columns/start_slot.md new file mode 100644 index 00000000..26b70800 --- /dev/null +++ b/models/descriptions/columns/start_slot.md @@ -0,0 +1,10 @@ +{% docs start_slot %} + +The first slot of the epoch. This field identifies the beginning slot number for the epoch, enabling epoch boundary tracking and time-based analysis. + +**Data type:** INTEGER (slot number) +**Business context:** Used to track epoch boundaries, analyze time-based patterns, and provide epoch context for block production data. +**Analytics use cases:** Epoch boundary tracking, time-based analysis, and epoch context provision. +**Example:** 123456789, 123456800 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/updated_at.md b/models/descriptions/columns/updated_at.md new file mode 100644 index 00000000..8a7ccd88 --- /dev/null +++ b/models/descriptions/columns/updated_at.md @@ -0,0 +1,10 @@ +{% docs updated_at %} + +The last date when the validator information was updated. This field tracks when the validator's metadata was last refreshed, enabling data freshness analysis and update tracking. + +**Data type:** TIMESTAMP (UTC) +**Business context:** Used to track data freshness, analyze update patterns, and ensure information currency. +**Analytics use cases:** Freshness tracking, update pattern analysis, and currency assessment. +**Example:** '2024-01-15 10:30:00', '2024-01-14 14:45:30' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/validator_epoch_credits.md b/models/descriptions/columns/validator_epoch_credits.md new file mode 100644 index 00000000..c7a7455e --- /dev/null +++ b/models/descriptions/columns/validator_epoch_credits.md @@ -0,0 +1,10 @@ +{% docs validator_epoch_credits %} + +Epoch credits for the validator. This field tracks the cumulative voting credits earned by the validator across epochs, enabling performance analysis and reward calculation. + +**Data type:** STRING (credits data) +**Business context:** Used to track validator voting performance, analyze credit accumulation patterns, and calculate voting rewards. +**Analytics use cases:** Performance analysis, credit accumulation tracking, and reward calculation. +**Example:** "123/1000/500", "456/1500/1000" + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/validator_name.md b/models/descriptions/columns/validator_name.md new file mode 100644 index 00000000..8d1da503 --- /dev/null +++ b/models/descriptions/columns/validator_name.md @@ -0,0 +1,10 @@ +{% docs validator_name %} + +The name of the validator. This field provides a human-readable identifier for the validator, enabling easier identification and branding analysis. + +**Data type:** STRING (validator name) +**Business context:** Used to identify validators, analyze branding, and track user experience with different validators. +**Analytics use cases:** Validator identification, branding analysis, and user experience tracking. +**Example:** 'Solana Foundation', 'Chorus One', 'Stakefish' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/validator_rank.md b/models/descriptions/columns/validator_rank.md new file mode 100644 index 00000000..b5d72701 --- /dev/null +++ b/models/descriptions/columns/validator_rank.md @@ -0,0 +1,10 @@ +{% docs validator_rank %} + +The rank of the validator by amount of delegated SOL. This field provides the validator's position in the network based on total stake delegation, enabling validator ranking analysis and stake distribution studies. + +**Data type:** INTEGER (ranking number) +**Business context:** Used to analyze validator rankings, track stake distribution, and study validator performance by stake size. +**Analytics use cases:** Validator ranking analysis, stake distribution studies, and performance correlation analysis. +**Example:** 1, 10, 100 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_account_owner.md b/models/descriptions/columns/vote_account_owner.md new file mode 100644 index 00000000..d4017bd6 --- /dev/null +++ b/models/descriptions/columns/vote_account_owner.md @@ -0,0 +1,10 @@ +{% docs vote_account_owner %} + +The program account that owns the vote account. This field identifies the Solana program that has authority over the vote account, enabling ownership analysis and program relationship tracking. + +**Data type:** STRING (program address) +**Business context:** Used to track vote account ownership, analyze program relationships, and understand account control structures. +**Analytics use cases:** Ownership tracking, program relationship analysis, and control structure understanding. +**Example:** 'Vote111111111111111111111111111111111111111111' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_choice.md b/models/descriptions/columns/vote_choice.md new file mode 100644 index 00000000..720a9595 --- /dev/null +++ b/models/descriptions/columns/vote_choice.md @@ -0,0 +1,10 @@ +{% docs vote_choice %} + +The voting option selected by the user on a Realms proposal. This field captures the specific choice made by the voter, enabling voting preference analysis and outcome prediction. + +**Data type:** STRING (voting option) +**Business context:** Used to track voting preferences, analyze proposal outcomes, and measure governance sentiment. +**Analytics use cases:** Voting preference analysis, proposal outcome prediction, and governance sentiment analysis. +**Example:** 'yes', 'no', 'abstain' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_options.md b/models/descriptions/columns/vote_options.md new file mode 100644 index 00000000..b8e19284 --- /dev/null +++ b/models/descriptions/columns/vote_options.md @@ -0,0 +1,10 @@ +{% docs vote_options %} + +The options that will be available to users who are voting on the proposal. This field contains the available voting choices or options for the governance proposal, enabling option analysis and voting choice tracking. + +**Data type:** ARRAY (vote options) +**Business context:** Used to track voting options, analyze choice patterns, and understand proposal structure. +**Analytics use cases:** Option tracking, choice pattern analysis, and structure understanding. +**Example:** ['Yes', 'No'], ['Option A', 'Option B', 'Option C'], ['Approve', 'Reject', 'Abstain'] + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_rank.md b/models/descriptions/columns/vote_rank.md new file mode 100644 index 00000000..80d1075b --- /dev/null +++ b/models/descriptions/columns/vote_rank.md @@ -0,0 +1,10 @@ +{% docs vote_rank %} + +The order which a user ranks their choices on a ranked vote on Realms. This field captures the preference ranking in multi-choice governance votes, enabling ranked voting analysis and preference ordering studies. + +**Data type:** INTEGER (ranking number) +**Business context:** Used to analyze ranked voting patterns, preference ordering, and governance decision complexity. +**Analytics use cases:** Ranked voting analysis, preference ordering studies, and governance decision complexity measurement. +**Example:** 1, 2, 3 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_type.md b/models/descriptions/columns/vote_type.md new file mode 100644 index 00000000..752f7ee1 --- /dev/null +++ b/models/descriptions/columns/vote_type.md @@ -0,0 +1,10 @@ +{% docs vote_type %} + +The type of voting strategy that will be used for voting on the proposal. This field specifies the voting mechanism or strategy for the governance proposal, enabling voting analysis and strategy comparison. + +**Data type:** STRING (vote type) +**Business context:** Used to track voting strategies, analyze voting mechanisms, and compare different governance approaches. +**Analytics use cases:** Strategy tracking, mechanism analysis, and approach comparison. +**Example:** 'Single Choice', 'Multiple Choice', 'Quadratic Voting', 'Token Weighted' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/vote_weight.md b/models/descriptions/columns/vote_weight.md new file mode 100644 index 00000000..c358afd0 --- /dev/null +++ b/models/descriptions/columns/vote_weight.md @@ -0,0 +1,10 @@ +{% docs vote_weight %} + +The percentage of voting power put towards a voting option on Realms. This field represents the proportion of a voter's total voting power allocated to a specific choice in weighted voting systems. + +**Data type:** DECIMAL (percentage as decimal) +**Business context:** Used to analyze voting power distribution, measure governance influence, and study weighted voting outcomes. +**Analytics use cases:** Voting power distribution analysis, governance influence measurement, and weighted voting outcome studies. +**Example:** 0.75, 1.0, 0.25 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/voter.md b/models/descriptions/columns/voter.md new file mode 100644 index 00000000..8732f72d --- /dev/null +++ b/models/descriptions/columns/voter.md @@ -0,0 +1,10 @@ +{% docs voter %} + +The address of the account that cast the governance vote. This field identifies the specific wallet or account that participated in the governance decision, enabling voter analysis and participation tracking. + +**Data type:** STRING (Solana address) +**Business context:** Used to track governance participation, analyze voter behavior, and identify key governance participants. +**Analytics use cases:** Voter participation analysis, whale voting tracking, and governance participation pattern studies. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/voter_account.md b/models/descriptions/columns/voter_account.md new file mode 100644 index 00000000..5823817d --- /dev/null +++ b/models/descriptions/columns/voter_account.md @@ -0,0 +1,10 @@ +{% docs voter_account %} + +The account with locked tokens linked to the NFT that determines voting power. This field identifies the specific account that holds the governance tokens and determines the voting power for the governance action. + +**Data type:** STRING (Solana address) +**Business context:** Used to analyze voting power distribution, governance token holdings, and voter influence measurement. +**Analytics use cases:** Voting power analysis, governance token distribution studies, and voter influence measurement. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/voter_nft.md b/models/descriptions/columns/voter_nft.md new file mode 100644 index 00000000..51488a04 --- /dev/null +++ b/models/descriptions/columns/voter_nft.md @@ -0,0 +1,10 @@ +{% docs voter_nft %} + +The NFT mint used in this vote on Marinade governance. This field identifies the specific NFT that was used to participate in the governance vote, enabling NFT-based voting analysis and utility measurement. + +**Data type:** STRING (NFT mint address) +**Business context:** Used to track NFT-based governance participation and analyze the utility of governance NFTs. +**Analytics use cases:** NFT-based voting analysis, governance participation tracking, and NFT utility measurement. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/votes.md b/models/descriptions/columns/votes.md new file mode 100644 index 00000000..4b653c76 --- /dev/null +++ b/models/descriptions/columns/votes.md @@ -0,0 +1,10 @@ +{% docs votes %} + +Votes cast by the vote account during the epoch. This field tracks the voting activity of the vote account within the current epoch, enabling participation analysis and consensus contribution measurement. + +**Data type:** ARRAY (vote data) +**Business context:** Used to track vote account participation, analyze voting patterns, and measure consensus contribution. +**Analytics use cases:** Participation tracking, voting pattern analysis, and consensus contribution measurement. +**Example:** [{'slot': 123456789, 'confirmation_count': 32}, {'slot': 123456790, 'confirmation_count': 31}] + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/warmup_cooldown_rate.md b/models/descriptions/columns/warmup_cooldown_rate.md new file mode 100644 index 00000000..5a8efdd5 --- /dev/null +++ b/models/descriptions/columns/warmup_cooldown_rate.md @@ -0,0 +1,10 @@ +{% docs warmup_cooldown_rate %} + +The rate at which stake can be activated or deactivated. This field tracks the speed of stake transitions between active and inactive states, enabling activation/deactivation analysis and timeline planning. + +**Data type:** DECIMAL (rate value) +**Business context:** Used to track stake transition rates, analyze activation/deactivation patterns, and plan for stake changes. +**Analytics use cases:** Transition rate tracking, pattern analysis, and change planning. +**Example:** 0.25, 0.5, 1.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/withdraw_amount.md b/models/descriptions/columns/withdraw_amount.md new file mode 100644 index 00000000..9ecabd12 --- /dev/null +++ b/models/descriptions/columns/withdraw_amount.md @@ -0,0 +1,10 @@ +{% docs withdraw_amount %} + +The amount of SOL withdrawn from the stake account. This field tracks the quantity of SOL removed from staking during withdrawal actions, enabling withdrawal analysis and stake reduction tracking. + +**Data type:** DECIMAL (SOL amount) +**Business context:** Used to track withdrawal amounts, analyze withdrawal patterns, and measure stake reduction activity. +**Analytics use cases:** Withdrawal tracking, pattern analysis, and reduction measurement. +**Example:** 10.0, 100.0, 1000.0 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/withdraw_authority.md b/models/descriptions/columns/withdraw_authority.md index 3bfc9c78..039df1eb 100644 --- a/models/descriptions/columns/withdraw_authority.md +++ b/models/descriptions/columns/withdraw_authority.md @@ -1,5 +1,10 @@ {% docs withdraw_authority %} -The authority that can withdraw SOL from the stake account. +The account responsible for signing any stake withdrawal transactions. This field identifies who has authority to withdraw staked SOL from the account. + +**Data type:** STRING (Solana address) +**Business context:** Used to track withdrawal authorities, analyze stake security, and monitor withdrawal patterns. +**Analytics use cases:** Withdrawal authority tracking, stake security analysis, and withdrawal pattern monitoring. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' {% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/withdraw_destination.md b/models/descriptions/columns/withdraw_destination.md new file mode 100644 index 00000000..7d9dd348 --- /dev/null +++ b/models/descriptions/columns/withdraw_destination.md @@ -0,0 +1,10 @@ +{% docs withdraw_destination %} + +The destination wallet address of the withdrawn SOL. This field identifies where the SOL was transferred to during withdrawal actions, enabling movement tracking and destination analysis. + +**Data type:** STRING (Solana address) +**Business context:** Used to track SOL movement destinations, analyze withdrawal patterns, and identify withdrawal recipients. +**Analytics use cases:** Movement tracking, pattern analysis, and recipient identification. +**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/columns/www_url.md b/models/descriptions/columns/www_url.md new file mode 100644 index 00000000..1d661519 --- /dev/null +++ b/models/descriptions/columns/www_url.md @@ -0,0 +1,10 @@ +{% docs www_url %} + +URL for the validator's website. This field provides a link to the validator's official website, enabling branding analysis and community engagement tracking. + +**Data type:** STRING (URL) +**Business context:** Used for validator branding, community engagement tracking, and official information access. +**Analytics use cases:** Branding analysis, engagement tracking, and information access. +**Example:** 'https://validator.com', 'https://stake.example.com', 'https://solana-validator.org' + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/dim_epoch.md b/models/descriptions/tables/dim_epoch.md new file mode 100644 index 00000000..3335ca9f --- /dev/null +++ b/models/descriptions/tables/dim_epoch.md @@ -0,0 +1,24 @@ +{% docs dim_epoch %} + +## Description +This table contains epoch information for the Solana blockchain, including the block range for each epoch. It serves as a dimension table that provides epoch context for governance and staking analytics, enabling time-based analysis across different epochs and supporting epoch-level aggregations. + +## Key Use Cases +- Provide epoch context for governance and staking analytics +- Enable epoch-based filtering and grouping of blockchain data +- Support time-series analysis across different epochs +- Facilitate epoch-level aggregations and reporting +- Track epoch progression and block range changes + +## Important Relationships +- Links to `gov.fact_validators` via `epoch` for validator performance analysis +- Connects to `gov.fact_proposal_votes` through epoch context for governance timeline analysis +- References `gov.fact_rewards_staking` and `gov.fact_rewards_voting` for epoch-based reward tracking +- Provides epoch context for `gov.fact_stake_accounts` and `gov.fact_vote_accounts` + +## Commonly-used Fields +- `epoch`: The epoch number identifier +- `start_block`: The first block number in the epoch +- `end_block`: The last block number in the epoch + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/ez_staking_lp_actions.md b/models/descriptions/tables/ez_staking_lp_actions.md new file mode 100644 index 00000000..8c498a9a --- /dev/null +++ b/models/descriptions/tables/ez_staking_lp_actions.md @@ -0,0 +1,30 @@ +{% docs ez_staking_lp_actions %} + +## Description +This table provides a unified view of native staking actions on the Solana blockchain using the official Stake11111111111111111111111111111111111111 program. It consolidates stake delegation, activation, deactivation, and withdrawal operations and enriches them with metadata, USD pricing, and validator information, enabling comprehensive analysis of native staking participation and validator delegation patterns. + +## Key Use Cases +- Analyze native staking delegation patterns and validator selection +- Track stake account lifecycle and balance changes with USD values +- Monitor native staking participation and delegation trends +- Study validator stake distribution and concentration +- Support native staking analytics and reward distribution analysis + +## Important Relationships +- Links to `gov.fact_staking_lp_actions` for detailed native staking action data +- Connects to `price.ez_prices_hourly` for USD price conversion +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides unified native staking context for validator analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the staking action occurred +- `tx_id`: Unique transaction identifier for the staking action +- `stake_account`: Address of the stake account +- `vote_pubkey`: Vote account that the stake is delegated to +- `action`: Type of staking action (e.g., 'delegate', 'deactivate', 'withdraw') +- `amount`: Amount of SOL involved in the action +- `amount_usd`: USD value of the action +- `user`: Address of the user performing the action +- `validator_name`: Name of the validator being delegated to + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_block_production.md b/models/descriptions/tables/fact_block_production.md new file mode 100644 index 00000000..3954e95c --- /dev/null +++ b/models/descriptions/tables/fact_block_production.md @@ -0,0 +1,26 @@ +{% docs fact_block_production %} + +## Description +This table tracks block production events on the Solana blockchain, capturing which validators produced blocks and when. It provides insights into network performance, validator participation in consensus, and block production distribution across the validator set. + +## Key Use Cases +- Analyze block production distribution across validators +- Track validator participation in network consensus +- Monitor network performance and block production efficiency +- Study validator reliability and block production patterns +- Support network health analysis and validator performance metrics + +## Important Relationships +- Links to `gov.fact_validators` through `node_pubkey` for validator performance analysis +- Connects to `gov.fact_vote_accounts` for vote account analysis +- References `core.fact_blocks` for block context +- Provides block production context for validator analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the block was produced +- `block_id`: Block number that was produced +- `node_pubkey`: Address of the validator that produced the block +- `vote_pubkey`: Vote account associated with the block producer +- `epoch`: Epoch when the block was produced + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_gauges_creates.md b/models/descriptions/tables/fact_gauges_creates.md new file mode 100644 index 00000000..aa188a8b --- /dev/null +++ b/models/descriptions/tables/fact_gauges_creates.md @@ -0,0 +1,26 @@ +{% docs fact_gauges_creates %} + +## Description +This table tracks gauge creation events, particularly for Marinade Finance's gauge system. Gauge creation establishes new reward distribution mechanisms for liquidity pools or protocols, enabling decentralized control over reward allocation and liquidity incentivization strategies. + +## Key Use Cases +- Track gauge creation patterns and new reward distribution mechanisms +- Analyze gauge creation frequency and protocol adoption +- Study gauge lifecycle from creation to voting and reward distribution +- Monitor DeFi protocol reward strategies and incentivization +- Support gauge analytics and reward optimization + +## Important Relationships +- Links to `gov.fact_gauges_votes` through `gauge` address for complete gauge lifecycle +- Connects to `gov.fact_gov_actions` for governance action analysis +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides gauge context for DeFi analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the gauge was created +- `tx_id`: Unique transaction identifier for the gauge creation +- `gauge`: Address of the created gauge +- `creator`: Address of the account that created the gauge +- `program_name`: Name of the gauge program (e.g., 'marinade') + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_gauges_votes.md b/models/descriptions/tables/fact_gauges_votes.md new file mode 100644 index 00000000..0401e1fe --- /dev/null +++ b/models/descriptions/tables/fact_gauges_votes.md @@ -0,0 +1,27 @@ +{% docs fact_gauges_votes %} + +## Description +This table tracks gauge voting events, particularly for Marinade Finance's gauge system. Gauge voting allows users to allocate rewards to different liquidity pools or protocols, providing a mechanism for decentralized reward distribution and liquidity incentivization. + +## Key Use Cases +- Analyze gauge voting patterns and reward allocation preferences +- Track reward distribution across different protocols and pools +- Study liquidity incentivization strategies and effectiveness +- Monitor gauge voting participation and user behavior +- Support DeFi analytics and reward optimization + +## Important Relationships +- Links to `gov.fact_gov_actions` through governance context for comprehensive governance analysis +- Connects to `gov.fact_gauges_creates` for gauge creation lifecycle +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides gauge context for DeFi analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the gauge vote was cast +- `tx_id`: Unique transaction identifier for the gauge vote +- `voter`: Address of the account that cast the gauge vote +- `gauge`: Address of the gauge being voted on +- `vote_weight`: Weight of the vote for reward allocation +- `program_name`: Name of the gauge program (e.g., 'marinade') + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_gov_actions.md b/models/descriptions/tables/fact_gov_actions.md new file mode 100644 index 00000000..219487f2 --- /dev/null +++ b/models/descriptions/tables/fact_gov_actions.md @@ -0,0 +1,30 @@ +{% docs fact_gov_actions %} + +## 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 + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_proposal_creation.md b/models/descriptions/tables/fact_proposal_creation.md new file mode 100644 index 00000000..693215a7 --- /dev/null +++ b/models/descriptions/tables/fact_proposal_creation.md @@ -0,0 +1,28 @@ +{% docs fact_proposal_creation %} + +## Description +This table tracks governance proposal creation events across different platforms including Realms and Tribeca. It captures the initial creation of governance proposals, including proposal details, creator information, and proposal parameters, enabling comprehensive analysis of governance proposal lifecycle and creation patterns. + +## Key Use Cases +- Track governance proposal creation patterns and frequency +- Analyze proposal creation by different governance platforms +- Study proposal lifecycle from creation to voting +- Monitor governance participation and proposal diversity +- Support DAO analytics and governance reporting + +## Important Relationships +- Links to `gov.fact_proposal_votes` through `proposal` address for complete proposal lifecycle +- Connects to `gov.fact_gov_actions` for governance action analysis +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides proposal context for governance analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the proposal was created +- `tx_id`: Unique transaction identifier for the proposal creation +- `proposal`: Address representing the created proposal +- `creator`: Address of the account that created the proposal +- `governance_platform`: Platform where the proposal was created +- `program_name`: Name of the governance program +- `realms_id`: Address representing the voting group within Realms + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_proposal_votes.md b/models/descriptions/tables/fact_proposal_votes.md new file mode 100644 index 00000000..ffb5a2bb --- /dev/null +++ b/models/descriptions/tables/fact_proposal_votes.md @@ -0,0 +1,33 @@ +{% docs fact_proposal_votes %} + +## Description +This table captures all governance proposal votes across different platforms including Realms and Tribeca (Marinade). It tracks voting participation, vote choices, voting power, and governance decisions, providing comprehensive analytics on decentralized governance voting patterns and decision-making processes. + +## Key Use Cases +- Analyze voting participation and patterns across governance platforms +- Track proposal outcomes and voting power distribution +- Study governance decision-making processes and voter behavior +- Monitor governance platform adoption and usage trends +- Support DAO analytics and governance reporting + +## Important Relationships +- Links to `gov.fact_gov_actions` through governance context for comprehensive governance analysis +- Connects to `gov.fact_proposal_creation` for proposal lifecycle tracking +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides voting context for protocol-specific governance analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the vote was cast +- `tx_id`: Unique transaction identifier for the vote +- `voter`: Address of the account that cast the vote +- `voter_account`: Account with locked tokens linked to the NFT (determines voting power) +- `voter_nft`: NFT mint used in this vote on Marinade +- `proposal`: Address representing the proposal being voted on +- `governance_platform`: Platform used for governance (e.g., 'realms', 'tribeca') +- `program_name`: Name of the governance program +- `vote_choice`: The voting option selected by the user on a Realms proposal +- `vote_rank`: The order which a user ranks their choices on a ranked vote +- `vote_weight`: Percentage of voting power put towards a voting option +- `realms_id`: Address representing the voting group within Realms + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_rewards_fee.md b/models/descriptions/tables/fact_rewards_fee.md new file mode 100644 index 00000000..19894ba4 --- /dev/null +++ b/models/descriptions/tables/fact_rewards_fee.md @@ -0,0 +1,27 @@ +{% docs fact_rewards_fee %} + +## Description +This table tracks fee rewards distributed on the Solana blockchain, capturing transaction fee distribution to validators and vote accounts. It enables analysis of fee reward patterns, validator fee income, and network fee distribution across the validator set. + +## Key Use Cases +- Analyze fee reward distribution and validator income +- Track validator fee generation and reward patterns +- Study network fee distribution and validator incentives +- Monitor fee reward accumulation and validator economics +- Support validator performance and fee optimization analysis + +## Important Relationships +- Links to `gov.fact_validators` through `node_pubkey` for validator fee analysis +- Connects to `gov.fact_vote_accounts` through `vote_pubkey` for vote account fee analysis +- References `gov.dim_epoch` for epoch-based fee analysis +- Provides fee reward context for validator economics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the fee reward was distributed +- `tx_id`: Unique transaction identifier for the fee reward +- `vote_pubkey`: Vote account receiving the fee reward +- `node_pubkey`: Validator node associated with the fee reward +- `reward_amount`: Amount of SOL distributed as fee reward +- `epoch`: Epoch when the fee reward was earned + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_rewards_rent.md b/models/descriptions/tables/fact_rewards_rent.md new file mode 100644 index 00000000..1bc285c9 --- /dev/null +++ b/models/descriptions/tables/fact_rewards_rent.md @@ -0,0 +1,27 @@ +{% docs fact_rewards_rent %} + +## Description +This table contains historical rent rewards data from the Solana blockchain, capturing rent payment distribution to validators and vote accounts that occurred before Solana discontinued rent rewards. This table is no longer updated as Solana has eliminated rent rewards as part of network improvements. + +## Key Use Cases +- Analyze historical rent reward distribution and validator income patterns +- Study past rent reward accumulation and validator economics +- Research historical network rent distribution and validator incentives +- Support historical validator performance analysis +- Provide context for understanding Solana's transition away from rent rewards + +## Important Relationships +- Links to `gov.fact_validators` through `node_pubkey` for historical validator rent analysis +- Connects to `gov.fact_vote_accounts` through `vote_pubkey` for historical vote account rent analysis +- References `gov.dim_epoch` for historical epoch-based rent analysis +- Provides historical rent reward context for validator economics research + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the rent reward was distributed (historical) +- `tx_id`: Unique transaction identifier for the rent reward +- `vote_pubkey`: Vote account that received the rent reward +- `node_pubkey`: Validator node associated with the rent reward +- `reward_amount`: Amount of SOL distributed as rent reward +- `epoch`: Epoch when the rent reward was earned + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_rewards_staking.md b/models/descriptions/tables/fact_rewards_staking.md new file mode 100644 index 00000000..2ae21d7f --- /dev/null +++ b/models/descriptions/tables/fact_rewards_staking.md @@ -0,0 +1,27 @@ +{% docs fact_rewards_staking %} + +## Description +This table tracks staking rewards distributed to stake accounts on the Solana blockchain. It captures reward events, amounts, and distribution patterns, enabling comprehensive analysis of staking returns, validator performance, and reward distribution across the network. + +## Key Use Cases +- Analyze staking reward distribution and returns +- Track validator performance and reward generation +- Study staking participation and reward patterns +- Monitor stake account reward accumulation +- Support staking analytics and return optimization + +## Important Relationships +- Links to `gov.fact_stake_accounts` through stake account addresses for reward analysis +- Connects to `gov.fact_validators` through `vote_pubkey` for validator performance +- References `gov.dim_epoch` for epoch-based reward analysis +- Provides reward context for staking analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the reward was distributed +- `tx_id`: Unique transaction identifier for the reward +- `stake_account`: Address of the stake account receiving the reward +- `vote_pubkey`: Vote account associated with the reward +- `reward_amount`: Amount of SOL distributed as reward +- `epoch`: Epoch when the reward was earned + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_rewards_voting.md b/models/descriptions/tables/fact_rewards_voting.md new file mode 100644 index 00000000..d643c864 --- /dev/null +++ b/models/descriptions/tables/fact_rewards_voting.md @@ -0,0 +1,27 @@ +{% docs fact_rewards_voting %} + +## Description +This table tracks voting rewards distributed to vote accounts on the Solana blockchain. It captures reward events for validator voting participation, enabling analysis of voting reward distribution, validator voting performance, and network consensus participation incentives. + +## Key Use Cases +- Analyze voting reward distribution and validator incentives +- Track vote account voting performance and reward generation +- Study voting participation patterns and reward accumulation +- Monitor validator voting reliability and reward patterns +- Support validator performance analysis and incentive optimization + +## Important Relationships +- Links to `gov.fact_vote_accounts` through vote account addresses for reward analysis +- Connects to `gov.fact_validators` through `vote_pubkey` for validator performance +- References `gov.dim_epoch` for epoch-based reward analysis +- Provides voting reward context for validator analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the voting reward was distributed +- `tx_id`: Unique transaction identifier for the voting reward +- `vote_pubkey`: Address of the vote account receiving the reward +- `node_pubkey`: Validator node associated with the vote account +- `reward_amount`: Amount of SOL distributed as voting reward +- `epoch`: Epoch when the voting reward was earned + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_stake_accounts.md b/models/descriptions/tables/fact_stake_accounts.md new file mode 100644 index 00000000..1cb501ef --- /dev/null +++ b/models/descriptions/tables/fact_stake_accounts.md @@ -0,0 +1,30 @@ +{% docs fact_stake_accounts %} + +## Description +This table tracks stake accounts on the Solana blockchain, capturing stake delegation, activation, deactivation, and balance changes. Stake accounts represent delegated SOL that contributes to network security and validator voting power, enabling comprehensive staking analytics and delegation pattern analysis. + +## Key Use Cases +- Track stake delegation patterns and validator selection +- Analyze stake account lifecycle and balance changes +- Monitor staking participation and delegation trends +- Study validator stake distribution and concentration +- Support staking analytics and reward distribution analysis + +## Important Relationships +- Links to `gov.fact_validators` through `vote_pubkey` for validator-stake mapping +- Connects to `gov.fact_vote_accounts` for vote account analysis +- References `gov.fact_rewards_staking` for reward distribution analysis +- Provides stake context for `gov.fact_rewards_voting` + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the stake account event occurred +- `tx_id`: Unique transaction identifier for the stake account event +- `stake_account`: Address of the stake account +- `vote_pubkey`: Vote account that the stake is delegated to +- `authority`: Address with authority over the stake account +- `stake_balance`: Current stake balance of the account +- `stake_type`: Type of stake (e.g., 'active', 'inactive', 'activating', 'deactivating') +- `lockup_epoch`: Epoch when stake lockup expires +- `custodian`: Address with custody over the stake account + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_staking_lp_actions.md b/models/descriptions/tables/fact_staking_lp_actions.md new file mode 100644 index 00000000..fdcf13c2 --- /dev/null +++ b/models/descriptions/tables/fact_staking_lp_actions.md @@ -0,0 +1,28 @@ +{% docs fact_staking_lp_actions %} + +## Description +This table tracks native staking actions on the Solana blockchain using the official Stake11111111111111111111111111111111111111 program. It captures stake delegation, activation, deactivation, and withdrawal operations directly to validators, enabling comprehensive analysis of native staking participation and validator delegation patterns. + +## Key Use Cases +- Analyze native staking delegation patterns and validator selection +- Track stake account lifecycle and balance changes +- Monitor native staking participation and delegation trends +- Study validator stake distribution and concentration +- Support native staking analytics and reward distribution analysis + +## Important Relationships +- Links to `gov.fact_stake_accounts` through stake account addresses for staking analysis +- Connects to `gov.fact_validators` for validator performance context +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides native staking context for validator analytics + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the staking action occurred +- `tx_id`: Unique transaction identifier for the staking action +- `stake_account`: Address of the stake account +- `vote_pubkey`: Vote account that the stake is delegated to +- `action`: Type of staking action (e.g., 'delegate', 'deactivate', 'withdraw') +- `amount`: Amount of SOL involved in the action +- `user`: Address of the user performing the action + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_validators.md b/models/descriptions/tables/fact_validators.md new file mode 100644 index 00000000..0c26c04e --- /dev/null +++ b/models/descriptions/tables/fact_validators.md @@ -0,0 +1,32 @@ +{% docs fact_validators %} + +## Description +This table contains comprehensive validator data by epoch, sourced from the Validators.app API. It tracks validator performance, stake distribution, geographic location, and operational metrics, providing detailed insights into Solana's validator network and supporting staking analytics and network health monitoring. + +## Key Use Cases +- Analyze validator performance and stake distribution across epochs +- Track validator geographic distribution and data center locations +- Monitor validator uptime, commission rates, and operational status +- Study staking patterns and validator selection behavior +- Support network health analysis and validator ranking + +## Important Relationships +- Links to `gov.dim_epoch` via `epoch` for epoch-based validator analysis +- Connects to `gov.fact_vote_accounts` through `vote_pubkey` for vote account analysis +- References `gov.fact_stake_accounts` for stake distribution analysis +- Provides validator context for `gov.fact_rewards_staking` and `gov.fact_rewards_voting` + +## Commonly-used Fields +- `epoch`: The epoch when validator data was recorded +- `node_pubkey`: Account for the validator node +- `vote_pubkey`: Vote account for the validator +- `active_stake`: Active stake in SOL delegated to the validator +- `commission`: Percentage of rewards payout to the vote account +- `delinquent`: Status whether the validator is offline/delinquent +- `validator_name`: Name of the validator +- `data_center_key`: Identifier for the data center +- `data_center_host`: Host for the data center +- `latitude` and `longitude`: Geographic coordinates of data center +- `software_version`: Solana mainnet version + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_vote_accounts.md b/models/descriptions/tables/fact_vote_accounts.md new file mode 100644 index 00000000..bac4b9a8 --- /dev/null +++ b/models/descriptions/tables/fact_vote_accounts.md @@ -0,0 +1,30 @@ +{% docs fact_vote_accounts %} + +## Description +This table tracks vote accounts on the Solana blockchain, capturing vote account creation, updates, and operational status. Vote accounts are essential components of Solana's consensus mechanism, representing the voting power of validators and enabling stake-weighted voting on network decisions. + +## Key Use Cases +- Track vote account creation and lifecycle management +- Analyze vote account performance and voting participation +- Monitor vote account balance changes and stake distribution +- Study validator voting patterns and network consensus +- Support staking analytics and validator performance analysis + +## Important Relationships +- Links to `gov.fact_validators` through `vote_pubkey` for validator-vote account mapping +- Connects to `gov.fact_stake_accounts` for stake distribution analysis +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides vote account context for `gov.fact_rewards_voting` + +## Commonly-used Fields +- `block_timestamp`: Timestamp when the vote account event occurred +- `tx_id`: Unique transaction identifier for the vote account event +- `vote_pubkey`: Address of the vote account +- `node_pubkey`: Address of the validator node associated with the vote account +- `authorized_voter`: Address authorized to vote on behalf of the vote account +- `authorized_withdrawer`: Address authorized to withdraw from the vote account +- `commission`: Commission rate for the vote account +- `vote_balance`: Current voting balance of the account +- `vote_credits`: Vote credits earned by the account + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/fact_votes_agg_block.md b/models/descriptions/tables/fact_votes_agg_block.md new file mode 100644 index 00000000..d140d328 --- /dev/null +++ b/models/descriptions/tables/fact_votes_agg_block.md @@ -0,0 +1,25 @@ +{% docs fact_votes_agg_block %} + +## Description +This table contains aggregated vote data by block, providing a summary view of voting activity and consensus participation across the Solana network. It tracks vote account participation in block validation and consensus, enabling analysis of network consensus patterns and validator voting behavior. + +## Key Use Cases +- Analyze consensus participation patterns by block +- Track vote account voting frequency and reliability +- Monitor network consensus health and participation rates +- Study validator voting patterns and network consensus +- Support network health analysis and consensus metrics + +## Important Relationships +- Links to `gov.fact_vote_accounts` through `vote_pubkey` for vote account analysis +- Connects to `gov.fact_validators` for validator performance analysis +- References `core.fact_blocks` for block context +- Provides consensus context for network analytics + +## Commonly-used Fields +- `block_id`: Block number for the aggregated votes +- `vote_pubkey`: Address of the vote account +- `vote_balance`: Voting balance of the account +- `vote_credits`: Vote credits earned by the account + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/marinade_dim_pools.md b/models/descriptions/tables/marinade_dim_pools.md new file mode 100644 index 00000000..f4401b90 --- /dev/null +++ b/models/descriptions/tables/marinade_dim_pools.md @@ -0,0 +1,26 @@ +{% docs marinade_dim_pools %} + +## Description +This table contains information on liquidity pools that involve MNDE or MSOL tokens as one of the liquidity pairs across multiple DeFi protocols including Raydium, Orca, and Meteora. It serves as a dimensional table providing comprehensive pool metadata, token information, and platform categorization for Marinade Finance ecosystem analysis. + +## Key Use Cases +- Analyze liquidity pool distribution across different DeFi protocols +- Track MSOL and MNDE token liquidity availability and depth +- Monitor pool initialization and creation patterns +- Support cross-protocol liquidity analysis and comparison +- Enable pool performance analysis and token pair tracking + +## Important Relationships +- Links to `marinade.ez_liquidity_pool_actions` through pool addresses for action analysis +- Connects to `marinade.ez_swaps` through pool addresses for swap activity tracking +- References `price.ez_asset_metadata` for token symbol and metadata information +- Provides pool context for Marinade Finance ecosystem analytics + +## Commonly-used Fields +- `pool_address`: Essential for linking to pool actions and swaps +- `pool_name`: Key for human-readable pool identification and analysis +- `token_a_mint` and `token_b_mint`: Critical for token pair analysis and filtering +- `platform`: Important for cross-protocol comparison and platform-specific analysis +- `is_msol_pool` and `is_mnde_pool`: Key for Marinade-specific pool filtering and analysis + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/marinade_ez_liquid_staking_actions.md b/models/descriptions/tables/marinade_ez_liquid_staking_actions.md new file mode 100644 index 00000000..46b75613 --- /dev/null +++ b/models/descriptions/tables/marinade_ez_liquid_staking_actions.md @@ -0,0 +1,26 @@ +{% docs marinade_ez_liquid_staking_actions %} + +## Description +This table captures actions related to Marinade liquid staking, including deposits, unstakes, and claims. It provides a unified view of liquid staking activities with USD pricing information, enabling comprehensive analysis of Marinade Finance's liquid staking protocol usage and user behavior patterns. + +## Key Use Cases +- Analyze liquid staking deposit and withdrawal patterns +- Track MSOL minting and burning activities +- Monitor claim activities and reward distributions +- Study user behavior in liquid staking protocols +- Support liquid staking protocol performance analysis + +## Important Relationships +- Links to `silver.marinade_liquid_staking_actions` for detailed action data +- Connects to `price.ez_prices_hourly` for USD price conversion +- References `core.fact_blocks` and `core.fact_transactions` for blockchain context +- Provides liquid staking context for Marinade Finance ecosystem analytics + +## Commonly-used Fields +- `block_timestamp`: Essential for time-series analysis and trend detection +- `action_type`: Critical for categorizing different staking activities +- `provider_address`: Key for user analysis and behavior tracking +- `deposit_amount` and `deposit_amount_usd`: Important for value analysis and financial metrics +- `msol_minted` and `msol_burned`: Critical for MSOL token flow analysis + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/marinade_ez_liquidity_pool_actions.md b/models/descriptions/tables/marinade_ez_liquidity_pool_actions.md new file mode 100644 index 00000000..1116dd66 --- /dev/null +++ b/models/descriptions/tables/marinade_ez_liquidity_pool_actions.md @@ -0,0 +1,27 @@ +{% docs marinade_ez_liquidity_pool_actions %} + +## Description +This table captures actions for liquidity pools that use either MSOL or MNDE as one of the liquidity pairs, including deposit and withdrawal events. It provides a unified view of liquidity provision activities across multiple DeFi protocols with USD pricing information, enabling comprehensive analysis of liquidity pool participation and token pair dynamics specifically for Marinade Finance ecosystem. + +## Key Use Cases +- Analyze liquidity provision patterns for MSOL and MNDE pools +- Track liquidity pool deposits and withdrawals across protocols +- Monitor liquidity depth and availability for Marinade tokens +- Study liquidity provider behavior and preferences +- Support liquidity pool performance and risk analysis + +## Important Relationships +- Links to `marinade.dim_pools` for pool metadata and categorization +- Connects to various `silver.liquidity_pool_actions_*` tables for platform-specific data +- References `price.ez_prices_hourly` for USD price conversion +- Provides liquidity context for Marinade Finance ecosystem analytics + +## Commonly-used Fields +- `block_timestamp`: Essential for time-series analysis and trend detection +- `action_type`: Critical for categorizing deposit vs withdrawal activities +- `provider_address`: Key for liquidity provider analysis and behavior tracking +- `pool_address`: Important for pool-specific analysis and filtering +- `token_a_amount_usd` and `token_b_amount_usd`: Critical for value analysis and financial metrics +- `platform`: Key for cross-protocol comparison and platform-specific analysis + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/marinade_ez_native_staking_actions.md b/models/descriptions/tables/marinade_ez_native_staking_actions.md new file mode 100644 index 00000000..36f2c31f --- /dev/null +++ b/models/descriptions/tables/marinade_ez_native_staking_actions.md @@ -0,0 +1,27 @@ +{% docs marinade_ez_native_staking_actions %} + +## Description +This table tracks staking actions for accounts that have interacted with Marinade Native Staking at least once. It provides a comprehensive view of native staking activities including deposits, withdrawals, and balance changes, with USD pricing information and validator details, enabling analysis of Marinade's native staking proxy service. + +## Key Use Cases +- Analyze native staking patterns through Marinade's proxy service +- Track stake account lifecycle and balance changes +- Monitor validator delegation patterns and performance +- Study user behavior in native staking through Marinade +- Support native staking proxy service performance analysis + +## Important Relationships +- Links to `silver.staking_lp_actions_labeled_2` for detailed staking action data +- Connects to `gov.fact_stake_accounts` for stake account information +- References `price.ez_prices_hourly` for USD price conversion +- Provides native staking context for Marinade Finance ecosystem analytics + +## Commonly-used Fields +- `block_timestamp`: Essential for time-series analysis and trend detection +- `event_type`: Critical for categorizing different staking activities +- `provider_address`: Key for user analysis and behavior tracking +- `stake_account`: Important for stake account lifecycle tracking +- `pre_tx_staked_balance` and `post_tx_staked_balance`: Critical for balance change analysis +- `validator_name` and `validator_rank`: Key for validator performance analysis + +{% enddocs %} \ No newline at end of file diff --git a/models/descriptions/tables/marinade_ez_swaps.md b/models/descriptions/tables/marinade_ez_swaps.md new file mode 100644 index 00000000..6ce63f45 --- /dev/null +++ b/models/descriptions/tables/marinade_ez_swaps.md @@ -0,0 +1,27 @@ +{% docs marinade_ez_swaps %} + +## Description +This table contains swaps involving MSOL and MNDE tokens across multiple decentralized exchanges and aggregators. It provides a unified view of trading activities for Marinade Finance tokens with USD pricing information, enabling comprehensive analysis of token liquidity and trading patterns. + +## Key Use Cases +- Analyze MSOL and MNDE trading volume and patterns +- Track token liquidity across different DEX platforms +- Monitor trading activity and price impact +- Study user trading behavior and preferences +- Support token economics and market analysis + +## Important Relationships +- Links to `defi.fact_swaps_jupiter_summary` for Jupiter aggregator swaps +- Connects to `silver.marinade_swaps` for direct DEX swaps +- References `price.ez_prices_hourly` for USD price conversion +- Connects to `core.dim_labels` for platform identification +- Provides trading context for Marinade Finance ecosystem analytics + +## Commonly-used Fields +- `block_timestamp`: Essential for time-series analysis and trend detection +- `swapper`: Key for user analysis and trading behavior tracking +- `swap_from_mint` and `swap_to_mint`: Critical for token pair analysis and filtering +- `swap_from_amount_usd` and `swap_to_amount_usd`: Important for value analysis and financial metrics +- `platform`: Key for cross-platform comparison and DEX analysis + +{% enddocs %} \ No newline at end of file diff --git a/models/gold/gov/gov__dim_epoch.yml b/models/gold/gov/gov__dim_epoch.yml index 7a0b0f90..70a4cb60 100644 --- a/models/gold/gov/gov__dim_epoch.yml +++ b/models/gold/gov/gov__dim_epoch.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__dim_epoch - description: "Contains the block range for epochs" + description: "{{ doc('dim_epoch') }}" columns: - name: EPOCH description: "{{ doc('epoch') }}" diff --git a/models/gold/gov/gov__ez_staking_lp_actions.yml b/models/gold/gov/gov__ez_staking_lp_actions.yml index 3216968c..df9ea7ae 100644 --- a/models/gold/gov/gov__ez_staking_lp_actions.yml +++ b/models/gold/gov/gov__ez_staking_lp_actions.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__ez_staking_lp_actions - description: EZ table for staking & LP actions that contains additional information about the validator. + description: "{{ doc('ez_staking_lp_actions') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 @@ -38,47 +38,47 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: SIGNERS - description: List of accounts that signed the transaction + description: "{{ doc('signers') }}" tests: - dbt_expectations.expect_column_to_exist - name: STAKE_AUTHORITY - description: The wallet address of the user who initialized the transaction. + description: "{{ doc('stake_authority') }}" tests: - dbt_expectations.expect_column_to_exist - name: STAKE_ACCOUNT - description: An account address containing balances of staked SOL that belongs to the stake authority. + description: "{{ doc('stake_account') }}" tests: - dbt_expectations.expect_column_to_exist - name: PRE_TX_STAKED_BALANCE - description: The amount of Solana belonging to the stake account before the transaction. + description: "{{ doc('pre_tx_staked_balance') }}" tests: - dbt_expectations.expect_column_to_exist - name: POST_TX_STAKED_BALANCE - description: The amount of Solana belonging to the stake account after the transaction. + description: "{{ doc('post_tx_staked_balance') }}" tests: - dbt_expectations.expect_column_to_exist - name: MOVE_AMOUNT - description: The amount of SOL being moved from the stake account. + description: "{{ doc('move_amount') }}" tests: - dbt_expectations.expect_column_to_exist - name: MOVE_DESTINATION - description: The destination wallet address of the moved SOL. + description: "{{ doc('move_destination') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTE_ACCOUNT - description: A voting account belonging to the validator. + description: "{{ doc('vote_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - name: NODE_PUBKEY - description: A unique key belonging to the validator node. + description: "{{ doc('node_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - name: VALIDATOR_RANK - description: The rank of the validator by amount of delegated SOL. + description: "{{ doc('validator_rank') }}" tests: - dbt_expectations.expect_column_to_exist - name: COMMISSION - description: The percentage of staked earnings given to the validator. + description: "{{ doc('commission') }}" tests: - dbt_expectations.expect_column_to_exist - name: EZ_STAKING_LP_ACTIONS_ID diff --git a/models/gold/gov/gov__fact_block_production.yml b/models/gold/gov/gov__fact_block_production.yml index 25cfa75b..c8576d12 100644 --- a/models/gold/gov/gov__fact_block_production.yml +++ b/models/gold/gov/gov__fact_block_production.yml @@ -1,30 +1,30 @@ version: 2 models: - name: gov__fact_block_production - description: Block production values for validators by epoch + description: "{{ doc('fact_block_production') }}" columns: - name: EPOCH - description: "Epoch when data was captured" + description: "{{ doc('epoch') }}" tests: - dbt_expectations.expect_column_to_exist - name: NODE_PUBKEY - description: "Pubkey for the Solana validator node" + description: "{{ doc('node_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - name: NUM_LEADER_SLOTS - description: "Number of slots the validator was the leader for in the epoch" + description: "{{ doc('num_leader_slots') }}" tests: - dbt_expectations.expect_column_to_exist - name: NUM_BLOCKS_PRODUCED - description: "Number of blocks the validator produced in the epoch" + description: "{{ doc('num_blocks_produced') }}" tests: - dbt_expectations.expect_column_to_exist - name: START_SLOT - description: "First slot of the epoch" + description: "{{ doc('start_slot') }}" tests: - dbt_expectations.expect_column_to_exist - name: END_SLOT - description: "Final slot of the epoch" + description: "{{ doc('end_slot') }}" tests: - dbt_expectations.expect_column_to_exist - name: FACT_BLOCK_PRODUCTION_ID diff --git a/models/gold/gov/gov__fact_gauges_creates.yml b/models/gold/gov/gov__fact_gauges_creates.yml index de5d96f3..141df5c9 100644 --- a/models/gold/gov/gov__fact_gauges_creates.yml +++ b/models/gold/gov/gov__fact_gauges_creates.yml @@ -1,10 +1,10 @@ version: 2 models: - name: gov__fact_gauges_creates - description: Creation events for gauges on Marinade and Saber. Gauges allow voting escrows to allocate the rewards of a set of liquidity mining pools. + description: "{{ doc('fact_gauges_creates') }}" columns: - name: PROGRAM_NAME - description: "name of solana program" + description: "{{ doc('program_name') }}" tests: - dbt_expectations.expect_column_to_exist - name: BLOCK_TIMESTAMP diff --git a/models/gold/gov/gov__fact_gauges_votes.yml b/models/gold/gov/gov__fact_gauges_votes.yml index e56324ea..e62d0779 100644 --- a/models/gold/gov/gov__fact_gauges_votes.yml +++ b/models/gold/gov/gov__fact_gauges_votes.yml @@ -1,13 +1,13 @@ version: 2 models: - name: gov__fact_gauges_votes - description: All gauge votes on Solana for Marinade and Saber. Gauges allow voting escrows to allocate the rewards of a set of liquidity mining pools. + description: "{{ doc('fact_gauges_votes') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 columns: - name: PROGRAM_NAME - description: "name of solana program" + description: "{{ doc('program_name') }}" data_tests: - not_null: *recent_date_filter - name: BLOCK_TIMESTAMP diff --git a/models/gold/gov/gov__fact_gov_actions.yml b/models/gold/gov/gov__fact_gov_actions.yml index 634821d9..1f0d59b7 100644 --- a/models/gold/gov/gov__fact_gov_actions.yml +++ b/models/gold/gov/gov__fact_gov_actions.yml @@ -1,13 +1,13 @@ version: 2 models: - name: gov__fact_gov_actions - description: All governance votes for Realms spaces and Marinade / Saber votes hosted on Tribeca. + description: "{{ doc('fact_gov_actions') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 columns: - name: PROGRAM_NAME - description: "name of solana program" + description: "{{ doc('program_name') }}" data_tests: - not_null: *recent_date_filter - name: BLOCK_TIMESTAMP diff --git a/models/gold/gov/gov__fact_proposal_creation.yml b/models/gold/gov/gov__fact_proposal_creation.yml index e8fd2014..b03c894a 100644 --- a/models/gold/gov/gov__fact_proposal_creation.yml +++ b/models/gold/gov/gov__fact_proposal_creation.yml @@ -1,13 +1,13 @@ version: 2 models: - name: gov__fact_proposal_creation - description: An EZ view of all proposal creations. Currently, this table is limited to only proposal creations on Realms DAO governance spaces. A space serves as a voting group for an organization, dAPP, or DAO. + description: "{{ doc('fact_proposal_creation') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 columns: - name: GOVERNANCE_PLATFORM - description: "platform used for governance space" + description: "{{ doc('governance_platform') }}" data_tests: - not_null: *recent_date_filter - name: BLOCK_TIMESTAMP @@ -32,27 +32,27 @@ models: data_tests: - not_null: *recent_date_filter - name: REALMS_ID - description: An address that is unique to the space or voting group on Realms. + description: "{{ doc('realms_id') }}" data_tests: - not_null: *recent_date_filter - name: PROPOSAL - description: Address representing the proposal being voted on. + description: "{{ doc('proposal') }}" data_tests: - not_null: *recent_date_filter - name: PROPOSAL_WRITER - description: Address of the user who is submitting the proposal for voting. + description: "{{ doc('proposal_writer') }}" data_tests: - not_null: *recent_date_filter - name: PROPOSAL_NAME - description: The name of the proposal that is being submitted + description: "{{ doc('proposal_name') }}" data_tests: - not_null: *recent_date_filter - name: VOTE_TYPE - description: The type of voting strategy that will be used for voting on the proposal. + description: "{{ doc('vote_type') }}" data_tests: - not_null: *recent_date_filter - name: VOTE_OPTIONS - description: The options that will be available to users who are voting on the proposal + description: "{{ doc('vote_options') }}" data_tests: - not_null: *recent_date_filter - name: FACT_PROPOSAL_CREATION_ID diff --git a/models/gold/gov/gov__fact_proposal_votes.yml b/models/gold/gov/gov__fact_proposal_votes.yml index 33fed479..13725348 100644 --- a/models/gold/gov/gov__fact_proposal_votes.yml +++ b/models/gold/gov/gov__fact_proposal_votes.yml @@ -1,14 +1,14 @@ version: 2 models: - name: gov__fact_proposal_votes - description: All governance votes for Realms spaces and Marinade / Saber votes hosted on Tribeca. + description: "{{ doc('fact_proposal_votes') }}" columns: - name: GOVERNANCE_PLATFORM - description: "platform used for governance space" + description: "{{ doc('governance_platform') }}" tests: - dbt_expectations.expect_column_to_exist - name: PROGRAM_NAME - description: "name of solana program" + description: "{{ doc('program_name') }}" tests: - dbt_expectations.expect_column_to_exist - name: BLOCK_TIMESTAMP @@ -31,35 +31,35 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: VOTER - description: Address voting on the proposal + description: "{{ doc('voter') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTER_ACCOUNT - description: Account with locked tokens linked to the NFT (determines voting power) + description: "{{ doc('voter_account') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTER_NFT - description: NFT mint used in this vote on Marinade + description: "{{ doc('voter_nft') }}" tests: - dbt_expectations.expect_column_to_exist - name: PROPOSAL - description: Address representing the proposal being voted on + description: "{{ doc('proposal') }}" tests: - dbt_expectations.expect_column_to_exist - name: REALMS_ID - description: Address representing the voting group within Realms + description: "{{ doc('realms_id') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTE_CHOICE - description: The voting option selected by the user on a Realms proposal + description: "{{ doc('vote_choice') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTE_RANK - description: The order which a user ranks their choices on a ranked vote on Realms + description: "{{ doc('vote_rank') }}" tests: - dbt_expectations.expect_column_to_exist - name: VOTE_WEIGHT - description: Percentage of voting power put towards a voting option on Realms + description: "{{ doc('vote_weight') }}" tests: - dbt_expectations.expect_column_to_exist - name: FACT_PROPOSAL_VOTES_ID diff --git a/models/gold/gov/gov__fact_rewards_fee.yml b/models/gold/gov/gov__fact_rewards_fee.yml index fb2bbfce..35bccf40 100644 --- a/models/gold/gov/gov__fact_rewards_fee.yml +++ b/models/gold/gov/gov__fact_rewards_fee.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_rewards_fee - description: Vote and non-vote fee rewards sent to the leader of a block. The leader receives 1/2 the total fees paid in the block. + description: "{{ doc('fact_rewards_fee') }}" columns: - name: BLOCK_ID description: "{{ doc('block_id') }}" @@ -23,7 +23,7 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: PUBKEY - description: "The address receiving the fee rewards" + description: "{{ doc('reward_recipient_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - name: EPOCH_EARNED diff --git a/models/gold/gov/gov__fact_rewards_rent.yml b/models/gold/gov/gov__fact_rewards_rent.yml index d60046de..58599f60 100644 --- a/models/gold/gov/gov__fact_rewards_rent.yml +++ b/models/gold/gov/gov__fact_rewards_rent.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_rewards_rent - description: Rent rewards sent to the leader of a block. The amount can be negative when rent is paid instead. + description: "{{ doc('fact_rewards_rent') }}" columns: - name: BLOCK_ID description: "{{ doc('block_id') }}" diff --git a/models/gold/gov/gov__fact_rewards_staking.yml b/models/gold/gov/gov__fact_rewards_staking.yml index 2fe81412..e1f85e84 100644 --- a/models/gold/gov/gov__fact_rewards_staking.yml +++ b/models/gold/gov/gov__fact_rewards_staking.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_rewards_staking - description: Rewards recieved by stake accounts/delegators. These are sent once in the beginning of an epoch, for rewards earned by activity in the previous epoch. + description: "{{ doc('fact_rewards_staking') }}" columns: - name: BLOCK_ID description: "{{ doc('block_id') }}" @@ -23,7 +23,7 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: STAKE_PUBKEY - description: "Address of stake account" + description: "{{ doc('stake_account') }}" tests: - dbt_expectations.expect_column_to_exist - name: EPOCH_EARNED diff --git a/models/gold/gov/gov__fact_rewards_voting.yml b/models/gold/gov/gov__fact_rewards_voting.yml index 95ea941c..eeff3aa5 100644 --- a/models/gold/gov/gov__fact_rewards_voting.yml +++ b/models/gold/gov/gov__fact_rewards_voting.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_rewards_voting - description: Rewards recieved by vote accounts/validators. These are sent once in the beginning of an epoch, for rewards earned by activity in the previous epoch. + description: "{{ doc('fact_rewards_voting') }}" columns: - name: BLOCK_ID description: "{{ doc('block_id') }}" diff --git a/models/gold/gov/gov__fact_stake_accounts.yml b/models/gold/gov/gov__fact_stake_accounts.yml index 642f045c..c55cc96d 100644 --- a/models/gold/gov/gov__fact_stake_accounts.yml +++ b/models/gold/gov/gov__fact_stake_accounts.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_stake_accounts - description: "This table contains data for stake accounts by epoch, including the active amount staked, lockup information, and related information." + description: "{{ doc('fact_stake_accounts') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 @@ -12,70 +12,70 @@ models: id_column: 'stake_pubkey' columns: - name: epoch - description: "Epoch when data was captured" + description: "{{ doc('epoch') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: stake_pubkey - description: "Address of stake account" + description: "{{ doc('stake_account') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: vote_pubkey - description: "Vote account of the validator this stake is delegated to" + description: "{{ doc('vote_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - name: authorized_staker - description: "Account responsible for signing stake delegations/deactivativations transactions" + description: "{{ doc('authorized_staker') }}" tests: - dbt_expectations.expect_column_to_exist - name: authorized_withdrawer - description: "Account responsible for signing any stake withdrawal transactions" + description: "{{ doc('withdraw_authority') }}" tests: - dbt_expectations.expect_column_to_exist - name: lockup - description: "Lockup information when tokens can be withdrawn" + description: "{{ doc('lockup') }}" tests: - dbt_expectations.expect_column_to_exist - name: rent_exempt_reserve - description: "Minimum SOL balance that must be maintained for this account to remain rent exempt" + description: "{{ doc('rent_exempt_reserve') }}" tests: - dbt_expectations.expect_column_to_exist - name: credits_observed - description: "Credits observed for the validator" + description: "{{ doc('credits_observed') }}" tests: - dbt_expectations.expect_column_to_exist - name: activation_epoch - description: "Epoch when stake was activated" + description: "{{ doc('activation_epoch') }}" tests: - dbt_expectations.expect_column_to_exist - name: deactivation_epoch - description: "Epoch when stake will be deactivated" + description: "{{ doc('deactivation_epoch') }}" tests: - dbt_expectations.expect_column_to_exist - name: active_stake - description: "Amount staked in SOL" + description: "{{ doc('stake_balance') }}" tests: - dbt_expectations.expect_column_to_exist - name: warmup_cooldown_rate - description: "Rate at which stake can be activated/deactivated" + description: "{{ doc('warmup_cooldown_rate') }}" tests: - dbt_expectations.expect_column_to_exist - name: type_stake - description: "Status of the stake" + description: "{{ doc('stake_type') }}" tests: - dbt_expectations.expect_column_to_exist - name: program - description: "The type of account" + description: "{{ doc('program') }}" tests: - dbt_expectations.expect_column_to_exist - name: account_sol - description: "SOL held in this account" + description: "{{ doc('stake_account_sol') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: rent_epoch - description: "Epoch at which this account will next owe rent" + description: "{{ doc('rent_epoch') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter diff --git a/models/gold/gov/gov__fact_staking_lp_actions.yml b/models/gold/gov/gov__fact_staking_lp_actions.yml index 7818c7a2..b72169cb 100644 --- a/models/gold/gov/gov__fact_staking_lp_actions.yml +++ b/models/gold/gov/gov__fact_staking_lp_actions.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_staking_lp_actions - description: Staking and liquidity provider actions that take place on the Solana blockchain. + description: "{{ doc('fact_staking_lp_actions') }}" columns: - name: BLOCK_TIMESTAMP description: "{{ doc('block_timestamp') }}" @@ -36,11 +36,11 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: SIGNERS - description: List of accounts that signed the transaction + description: "{{ doc('signers') }}" tests: - dbt_expectations.expect_column_to_exist - name: ACCOUNT_KEYS - description: List of accounts that are referenced by pre/post sol/token balances objects + description: "{{ doc('account_keys') }}" tests: - dbt_expectations.expect_column_to_exist - name: INSTRUCTION @@ -52,19 +52,19 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: PRE_BALANCES - description: List of pre-transaction balances for different accounts + description: "{{ doc('pre_balances') }}" tests: - dbt_expectations.expect_column_to_exist - name: POST_BALANCES - description: List of post-transaction balances for different accounts + description: "{{ doc('post_balances') }}" tests: - dbt_expectations.expect_column_to_exist - name: PRE_TOKEN_BALANCES - description: List of pre-transaction token balances for different token accounts + description: "{{ doc('pre_token_balances') }}" tests: - dbt_expectations.expect_column_to_exist - name: POST_TOKEN_BALANCES - description: List of post-transaction token balances for different token accounts + description: "{{ doc('post_token_balances') }}" tests: - dbt_expectations.expect_column_to_exist - name: FACT_STAKING_LP_ACTIONS_ID diff --git a/models/gold/gov/gov__fact_validators.yml b/models/gold/gov/gov__fact_validators.yml index 16ce3aee..878f1c4f 100644 --- a/models/gold/gov/gov__fact_validators.yml +++ b/models/gold/gov/gov__fact_validators.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_validators - description: "This table contains validator data by epoch, sourced from the Validators.app API" + description: "{{ doc('fact_validators') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 @@ -16,104 +16,104 @@ models: id_column: 'node_pubkey' columns: - name: epoch - description: "The epoch when data was recorded" + description: "{{ doc('epoch') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: node_pubkey - description: "Account for the validator node" + description: "{{ doc('node_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: vote_pubkey - description: "vote account for the validator" + description: "{{ doc('vote_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: active_stake - description: "Active stake in SOL delegated to the validator" + description: "{{ doc('active_stake') }}" tests: - dbt_expectations.expect_column_to_exist - null_threshold: threshold_percent: 0.99 # api returns null for some validators where: modified_timestamp >= current_date - 7 - name: admin_warning - description: "Admin warning for the validator" + description: "{{ doc('admin_warning') }}" tests: - dbt_expectations.expect_column_to_exist - name: avatar_url - description: "URL of avatar image" + description: "{{ doc('avatar_url') }}" tests: - dbt_expectations.expect_column_to_exist - name: commission - description: "% of rewards payout to the vote account" + description: "{{ doc('commission') }}" tests: - dbt_expectations.expect_column_to_exist - null_threshold: threshold_percent: 0.99 # api returns null for some validators where: modified_timestamp >= current_date - 7 - name: created_at - description: "date when validator was created" + description: "{{ doc('created_at') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: data_center_key - description: "identifier for the data center" + description: "{{ doc('data_center_key') }}" tests: - dbt_expectations.expect_column_to_exist - name: data_center_host - description: "host for the data center" + description: "{{ doc('data_center_host') }}" tests: - dbt_expectations.expect_column_to_exist - name: delinquent - description: "Status whether the validator is offline/delinquent" + description: "{{ doc('delinquent') }}" tests: - dbt_expectations.expect_column_to_exist - null_threshold: threshold_percent: 0.99 # api returns null for some validators where: modified_timestamp >= current_date - 7 - name: details - description: "Details for the validator" + description: "{{ doc('details') }}" tests: - dbt_expectations.expect_column_to_exist - name: epoch_active - description: "last epoch when vote account was active" + description: "{{ doc('epoch_active') }}" tests: - dbt_expectations.expect_column_to_exist - name: epoch_credits - description: "Epoch credits for the validator" + description: "{{ doc('validator_epoch_credits') }}" tests: - dbt_expectations.expect_column_to_exist - name: keybase_id - description: "Keybase ID for the validator" + description: "{{ doc('keybase_id') }}" tests: - dbt_expectations.expect_column_to_exist - name: latitude - description: "Latitude coordinates of data center" + description: "{{ doc('latitude') }}" tests: - dbt_expectations.expect_column_to_exist - name: longitude - description: "Longitude coordinates of data center" + description: "{{ doc('longitude') }}" tests: - dbt_expectations.expect_column_to_exist - name: validator_name - description: "Name of the validator" + description: "{{ doc('validator_name') }}" tests: - dbt_expectations.expect_column_to_exist - name: software_version - description: "Solana mainnet version" + description: "{{ doc('software_version') }}" tests: - dbt_expectations.expect_column_to_exist - null_threshold: threshold_percent: 0.99 # api returns null for some validators where: modified_timestamp >= current_date - 7 - name: updated_at - description: "Last date validator was updated" + description: "{{ doc('updated_at') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: www_url - description: "url for the validator" + description: "{{ doc('www_url') }}" tests: - dbt_expectations.expect_column_to_exist - name: FACT_VALIDATORS_ID diff --git a/models/gold/gov/gov__fact_vote_accounts.yml b/models/gold/gov/gov__fact_vote_accounts.yml index cc2f55ce..c3a20c8c 100644 --- a/models/gold/gov/gov__fact_vote_accounts.yml +++ b/models/gold/gov/gov__fact_vote_accounts.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_vote_accounts - description: "This table contains data for each vote account by epoch, including the validator's public key, voting weight, commission rate, and related information." + description: "{{ doc('fact_vote_accounts') }}" recent_date_filter: &recent_date_filter config: where: modified_timestamp >= current_date - 7 @@ -12,80 +12,80 @@ models: id_column: 'vote_pubkey' columns: - name: epoch - description: "Epoch when data was captured" + description: "{{ doc('epoch') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: authorized_voter - description: "Account responsible for signing vote transactions" + description: "{{ doc('authorized_voter') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: where: (modified_timestamp >= current_date - 7) and authorized_withdrawer <> '11111111111111111111111111111111' - name: last_epoch_active - description: "last epoch when vote account was active" + description: "{{ doc('last_epoch_active') }}" tests: - dbt_expectations.expect_column_to_exist - name: authorized_withdrawer - description: "Account responsible for signing stake withdrawal transactions" + description: "{{ doc('authorized_withdrawer') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: commission - description: "% of rewards payout to the vote account" + description: "{{ doc('commission') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: epoch_credits - description: "Credits earned by the end of epochs, containing epoch/credits/previous credits" + description: "{{ doc('epoch_credits') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: last_timestamp_slot - description: "Last slot voted on" + description: "{{ doc('last_timestamp_slot') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: last_timestamp - description: "The timestamp when last slot was voted on" + description: "{{ doc('last_timestamp') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: node_pubkey - description: "pubkey for the Solana validator node" + description: "{{ doc('node_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: prior_voters - description: "Prior voters for the vote account" + description: "{{ doc('prior_voters') }}" tests: - dbt_expectations.expect_column_to_exist - name: root_slot - description: "latest slot confirmed" + description: "{{ doc('root_slot') }}" tests: - dbt_expectations.expect_column_to_exist - name: votes - description: "Votes during epoch" + description: "{{ doc('votes') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: account_sol - description: "SOL assigned to this account" + description: "{{ doc('account_sol') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: owner - description: "Program account that owns the vote account" + description: "{{ doc('vote_account_owner') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: rent_epoch - description: "Epoch at which this account will next owe rent" + description: "{{ doc('rent_epoch') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: vote_pubkey - description: "Public key for the vote account" + description: "{{ doc('vote_pubkey') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter diff --git a/models/gold/gov/gov__fact_votes_agg_block.yml b/models/gold/gov/gov__fact_votes_agg_block.yml index a9124363..31bf4ea3 100644 --- a/models/gold/gov/gov__fact_votes_agg_block.yml +++ b/models/gold/gov/gov__fact_votes_agg_block.yml @@ -1,7 +1,7 @@ version: 2 models: - name: gov__fact_votes_agg_block - description: An aggregate table containing the number of automatic validator voting transactions that occurred during a block. + description: "{{ doc('fact_votes_agg_block') }}" columns: - name: BLOCK_TIMESTAMP description: "{{ doc('block_timestamp') }}" @@ -15,7 +15,7 @@ models: tests: - dbt_expectations.expect_column_to_exist - name: NUM_VOTES - description: The number of vote events that occurred within the block + description: "{{ doc('num_votes') }}" tests: - dbt_expectations.expect_column_to_exist - name: FACT_VOTES_AGG_BLOCK_ID diff --git a/models/gold/marinade/marinade__dim_pools.yml b/models/gold/marinade/marinade__dim_pools.yml index db6f4090..f9275904 100644 --- a/models/gold/marinade/marinade__dim_pools.yml +++ b/models/gold/marinade/marinade__dim_pools.yml @@ -1,7 +1,7 @@ version: 2 models: - name: marinade__dim_pools - description: Dimensional table containing information on liquidity pools that involve MNDE or MSOL tokens as one of the liquidity pairs. + description: "{{ doc('marinade_dim_pools') }}" columns: - name: POOL_ADDRESS description: "{{ doc('liquidity_pool_address') }}" @@ -9,8 +9,7 @@ models: - not_null - unique - name: POOL_NAME - description: > - Name of the liquidity pool + description: "{{ doc('pool_name') }}" data_tests: - not_null: config: @@ -58,13 +57,11 @@ models: - name: INITIALIZED_AT_INNER_INDEX description: "{{ doc('inner_index') }}" - name: IS_MSOL_POOL - description: > - Whether the pool has MSOL as one of the tokens + description: "{{ doc('is_msol_pool') }}" data_tests: - not_null - name: IS_MNDE_POOL - description: > - Whether the pool has MNDE as one of the tokens + description: "{{ doc('is_mnde_pool') }}" data_tests: - not_null - name: PROGRAM_ID @@ -72,8 +69,7 @@ models: data_tests: - not_null - name: PLATFORM - description: > - Name of the liquidity pool protocol + description: "{{ doc('platform') }}" data_tests: - not_null - name: DIM_POOLS_ID diff --git a/models/gold/marinade/marinade__ez_liquid_staking_actions.yml b/models/gold/marinade/marinade__ez_liquid_staking_actions.yml index 039541b6..86e1b758 100644 --- a/models/gold/marinade/marinade__ez_liquid_staking_actions.yml +++ b/models/gold/marinade/marinade__ez_liquid_staking_actions.yml @@ -1,7 +1,7 @@ version: 2 models: - name: marinade__ez_liquid_staking_actions - description: Convenience table capturing actions related to Marinade liquid staking, including deposits, unstakes, and claims. + description: "{{ doc('marinade_ez_liquid_staking_actions') }}" tests: - dbt_utils.unique_combination_of_columns: combination_of_columns: @@ -51,35 +51,35 @@ models: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: DEPOSIT_AMOUNT - description: "The amount of SOL deposited" + description: "{{ doc('deposit_amount') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: where: action_type = 'deposit' AND block_timestamp >= current_date - 7 - name: DEPOSIT_AMOUNT_USD - description: "The amount of SOL deposited in USD" + description: "{{ doc('deposit_amount_usd') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: where: action_type = 'deposit' AND block_timestamp >= current_date - 7 - name: MSOL_MINTED - description: "The amount of mSOL minted" + description: "{{ doc('msol_minted') }}" tests: - dbt_expectations.expect_column_to_exist - name: MSOL_BURNED - description: "The amount of mSOL burned" + description: "{{ doc('msol_burned') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: where: action_type = 'orderUnstake' AND block_timestamp >= current_date - 7 - name: CLAIM_AMOUNT - description: "The amount of SOL claimed" + description: "{{ doc('claim_amount') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: where: action_type = 'claim' AND block_timestamp >= current_date - 7 - name: CLAIM_AMOUNT_USD - description: "The amount of SOL claimed in USD" + description: "{{ doc('claim_amount_usd') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: diff --git a/models/gold/marinade/marinade__ez_liquidity_pool_actions.yml b/models/gold/marinade/marinade__ez_liquidity_pool_actions.yml index 9462e5d3..3c480db8 100644 --- a/models/gold/marinade/marinade__ez_liquidity_pool_actions.yml +++ b/models/gold/marinade/marinade__ez_liquidity_pool_actions.yml @@ -1,7 +1,7 @@ version: 2 models: - name: marinade__ez_liquidity_pool_actions - description: Convenience table capturing actions for liquidity pools that use either MSOL or MNDE as one of the liquidity pairs. This includes deposit and withdrawal events. + description: "{{ doc('marinade_ez_liquidity_pool_actions') }}" recent_date_filter: &recent_date_filter config: where: > @@ -53,8 +53,7 @@ models: data_tests: - not_null: *recent_date_filter - name: TOKEN_A_AMOUNT_USD - description: > - The amount of token A in USD. + description: "{{ doc('token_a_amount_usd') }}" - name: TOKEN_B_MINT description: "{{ doc('token_b_mint') }}" - name: TOKEN_B_SYMBOL @@ -62,23 +61,19 @@ models: - name: TOKEN_B_AMOUNT description: "{{ doc('token_b_amount') }}" - name: TOKEN_B_AMOUNT_USD - description: > - The amount of token B in USD. + description: "{{ doc('token_b_amount_usd') }}" - name: POOL_ADDRESS description: "{{ doc('liquidity_pool_address') }}" data_tests: - not_null: *recent_date_filter - name: POOL_NAME - description: > - Name of the liquidity pool + description: "{{ doc('pool_name') }}" - name: IS_MSOL_POOL - description: > - Whether the pool has MSOL as one of the tokens + description: "{{ doc('is_msol_pool') }}" data_tests: - not_null - name: IS_MNDE_POOL - description: > - Whether the pool has MNDE as one of the tokens + description: "{{ doc('is_mnde_pool') }}" data_tests: - not_null - name: PROGRAM_ID @@ -86,8 +81,7 @@ models: data_tests: - not_null: *recent_date_filter - name: PLATFORM - description: > - Name of the liquidity pool protocol + description: "{{ doc('platform') }}" data_tests: - not_null - name: EZ_LIQUIDITY_POOL_ACTIONS_ID diff --git a/models/gold/marinade/marinade__ez_native_staking_actions.yml b/models/gold/marinade/marinade__ez_native_staking_actions.yml index 25a8596c..91d70d84 100644 --- a/models/gold/marinade/marinade__ez_native_staking_actions.yml +++ b/models/gold/marinade/marinade__ez_native_staking_actions.yml @@ -1,7 +1,7 @@ version: 2 models: - name: marinade__ez_native_staking_actions - description: Table for staking actions for any account that has interacted with Marinade Native Staking at least once + description: "{{ doc('marinade_ez_native_staking_actions') }}" recent_date_filter: &recent_date_filter config: where: _inserted_timestamp >= current_date - 7 @@ -59,39 +59,39 @@ models: data_tests: - not_null: *recent_date_filter - name: STAKE_ACTIVE - description: Whether the stake account is active. + description: "{{ doc('stake_active') }}" - name: WITHDRAW_DESTINATION - description: The destination wallet address of the withdrawn SOL. + description: "{{ doc('withdraw_destination') }}" - name: WITHDRAW_AMOUNT - description: The amount of SOL withdrawn from the stake account. + description: "{{ doc('withdraw_amount') }}" - name: PRE_TX_STAKED_BALANCE - description: The amount of Solana belonging to the stake account before the transaction. + description: "{{ doc('pre_tx_staked_balance') }}" - name: PRE_TX_STAKED_BALANCE_USD - description: The amount of Solana belonging to the stake account before the transaction in USD. + description: "{{ doc('pre_tx_staked_balance_usd') }}" - name: POST_TX_STAKED_BALANCE - description: The amount of Solana belonging to the stake account after the transaction. + description: "{{ doc('post_tx_staked_balance') }}" - name: POST_TX_STAKED_BALANCE_USD - description: The amount of Solana belonging to the stake account after the transaction in USD. + description: "{{ doc('post_tx_staked_balance_usd') }}" - name: VOTE_ACCOUNT - description: A voting account belonging to the validator. + description: "{{ doc('vote_pubkey') }}" - name: NODE_PUBKEY - description: A unique key belonging to the validator node. + description: "{{ doc('node_pubkey') }}" - name: VALIDATOR_RANK - description: The rank of the validator by amount of delegated SOL. + description: "{{ doc('validator_rank') }}" - name: COMMISSION - description: The percentage of staked earnings given to the validator. + description: "{{ doc('commission') }}" - name: VALIDATOR_NAME - description: The name of the validator. + description: "{{ doc('validator_name') }}" - name: PROGRAM_ID - description: The program id of the native stake program + description: "{{ doc('program_id') }}" data_tests: - not_null: *recent_date_filter - name: PLATFORM - description: The platform of the staking account either native or marinate native proxy + description: "{{ doc('native_staking_platform') }}" data_tests: - not_null: *recent_date_filter - name: IS_USING_MARINADE_NATIVE_STAKING - description: Whether the staking action is using Marinade Native Staking + description: "{{ doc('is_using_marinade_native_staking') }}" data_tests: - not_null: *recent_date_filter - name: _INSERTED_TIMESTAMP diff --git a/models/gold/marinade/marinade__ez_swaps.yml b/models/gold/marinade/marinade__ez_swaps.yml index f4a7bea4..8103ef1a 100644 --- a/models/gold/marinade/marinade__ez_swaps.yml +++ b/models/gold/marinade/marinade__ez_swaps.yml @@ -1,7 +1,7 @@ version: 2 models: - name: marinade__ez_swaps - description: A convenience table containing swaps involving mSOL and MNDE tokens. + description: "{{ doc('marinade_ez_swaps') }}" recent_date_filter: &recent_date_filter config: where: block_timestamp >= current_date - 7 @@ -25,44 +25,44 @@ models: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAPPER - description: Address that initiated the swap + description: "{{ doc('swaps_swapper') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAP_FROM_AMOUNT - description: Total amount of the token sent in to initiate the swap + description: "{{ doc('swaps_from_amt') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAP_FROM_MINT - description: Token being sent or swapped from + description: "{{ doc('swaps_from_mint') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAP_FROM_AMOUNT_USD - description: The amount of tokens put into the swap converted to USD using the price of the token + description: "{{ doc('swap_from_amount_usd') }}" tests: - dbt_expectations.expect_column_to_exist - name: SWAP_FROM_SYMBOL - description: The symbol of the token being swapped from + description: "{{ doc('swap_from_symbol') }}" tests: - dbt_expectations.expect_column_to_exist - name: SWAP_TO_AMOUNT - description: Total amount of the token received in the swap + description: "{{ doc('swaps_to_amt') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAP_TO_MINT - description: Token being received or swapped for + description: "{{ doc('swaps_to_mint') }}" tests: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: SWAP_TO_AMOUNT_USD - description: The amount of tokens taken out of or received from the swap converted to USD using the price of the token + description: "{{ doc('swap_to_amount_usd') }}" tests: - dbt_expectations.expect_column_to_exist - name: SWAP_TO_SYMBOL - description: The symbol of the token being swapped to + description: "{{ doc('swap_to_symbol') }}" tests: - dbt_expectations.expect_column_to_exist - name: PROGRAM_ID @@ -71,7 +71,7 @@ models: - dbt_expectations.expect_column_to_exist - not_null: *recent_date_filter - name: PLATFORM - description: name of decentralized exchange used to perform the swap + description: "{{ doc('dex_platform') }}" tests: - not_null: *recent_date_filter - name: MARINADE_EZ_SWAPS_ID