mirror of
https://github.com/FlipsideCrypto/near-models.git
synced 2026-02-06 11:26:52 +00:00
table docs updates
This commit is contained in:
parent
7de621a334
commit
096ac0a121
@ -1,83 +0,0 @@
|
||||
---
|
||||
description: Cursor Rules Location
|
||||
globs:
|
||||
alwaysApply: false
|
||||
---
|
||||
---
|
||||
description: Cursor Rules Location
|
||||
globs: *.mdc
|
||||
---
|
||||
# Cursor Rules Location
|
||||
|
||||
Rules for placing and organizing Cursor rule files in the repository.
|
||||
|
||||
<rule>
|
||||
name: cursor_rules_location
|
||||
description: Standards for placing Cursor rule files in the correct directory
|
||||
filters:
|
||||
# Match any .mdc files
|
||||
- type: file_extension
|
||||
pattern: "\\.mdc$"
|
||||
# Match files that look like Cursor rules
|
||||
- type: content
|
||||
pattern: "(?s)<rule>.*?</rule>"
|
||||
# Match file creation events
|
||||
- type: event
|
||||
pattern: "file_create"
|
||||
|
||||
actions:
|
||||
- type: reject
|
||||
conditions:
|
||||
- pattern: "^(?!\\.\\/\\.cursor\\/rules\\/.*\\.mdc$)"
|
||||
message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
|
||||
|
||||
- type: suggest
|
||||
message: |
|
||||
When creating Cursor rules:
|
||||
|
||||
1. Always place rule files in PROJECT_ROOT/.cursor/rules/:
|
||||
```
|
||||
.cursor/rules/
|
||||
├── general-coding-standards.mdc
|
||||
├── dbt-model-standards.mdc
|
||||
├── project-context.mdc
|
||||
└── cursor-rules-location.mdc
|
||||
```
|
||||
|
||||
2. Follow the naming convention:
|
||||
- Use kebab-case for filenames
|
||||
- Always use .mdc extension
|
||||
- Make names descriptive of the rule's purpose
|
||||
|
||||
3. Directory structure:
|
||||
```
|
||||
PROJECT_ROOT/
|
||||
├── .cursor/
|
||||
│ └── rules/
|
||||
│ ├── general-coding-standards.mdc
|
||||
│ ├── dbt-model-standards.mdc
|
||||
│ ├── project-context.mdc
|
||||
│ └── cursor-rules-location.mdc
|
||||
└── ...
|
||||
```
|
||||
|
||||
4. Never place rule files:
|
||||
- In the project root
|
||||
- In subdirectories outside .cursor/rules
|
||||
- In any other location
|
||||
|
||||
examples:
|
||||
- input: |
|
||||
# Bad: Rule file in wrong location
|
||||
rules/my-rule.mdc
|
||||
my-rule.mdc
|
||||
.rules/my-rule.mdc
|
||||
|
||||
# Good: Rule file in correct location
|
||||
.cursor/rules/my-rule.mdc
|
||||
output: "Correctly placed Cursor rule file"
|
||||
|
||||
metadata:
|
||||
priority: high
|
||||
version: 1.0
|
||||
</rule>
|
||||
@ -11,7 +11,7 @@ The file `models/descriptions/__overview__.md` is the entry point to the model d
|
||||
The file MUST START AND END WITH DBT JINJA DOCS TAGS `{% docs __overview__ %}` and `{% ENDDOCS %}`
|
||||
|
||||
## Quick Links Section Requirements
|
||||
The `__overview__.md` file MUST contain a "Quick Links to Table Documentation" section that provides direct navigation to all gold model documentation. This section must include a simple list, organized by gold schema, with the models and a hyperlink to the model documentation.
|
||||
The `__overview__.md` file MUST contain a "Quick Links to Table Documentation" section that provides direct navigation to all gold model documentation. This section must include a simple list, organized by gold schema, with the models and a hyperlink to the model documentation. If there is an existing section like "using dbt docs" that instructs the user on how to navigate dbt docs or a list of links to flipside and dbt, remove it! These are outdated.
|
||||
|
||||
### Required Elements:
|
||||
**Hyperlinks to Gold Model Documentation** - A comprehensive list of all gold models organized by schema. The schema can be inferred from the model name as the slug before the double underscore. For example, `core__fact_blocks` is a model named `fact_blocks` in the schema `core`.
|
||||
|
||||
@ -1,69 +0,0 @@
|
||||
---
|
||||
description:
|
||||
globs:
|
||||
alwaysApply: true
|
||||
---
|
||||
# Project Context
|
||||
|
||||
This is a dbt project for analyzing NEAR Protocol blockchain data using Snowflake as the data warehouse.
|
||||
The models follow dimensional modeling principles with a focus on blockchain-specific patterns.
|
||||
|
||||
## Domain Knowledge
|
||||
|
||||
### NEAR Protocol
|
||||
- Account structure: implicit accounts vs named accounts
|
||||
- Transaction anatomy: signatures, actions, receipts, outcomes
|
||||
- Smart contract interactions: function calls, cross-contract calls
|
||||
- Gas mechanics: attached deposits, gas pricing, refunds
|
||||
- RPC methods: tx_status, block, receipt, access_key_changes
|
||||
- Sharding architecture: chunks, receipts across shards
|
||||
- Token standards: FT (NEP-141), NFT (NEP-171)
|
||||
|
||||
### Data Structures
|
||||
- Blocks: height, timestamp, hash, author, chunks
|
||||
- Transactions: hash, signer_id, receiver_id, actions
|
||||
- Receipts: predecessor_id, receiver_id, action_kind
|
||||
- Execution Outcomes: status, gas_burnt, tokens_burnt
|
||||
- State Changes: account updates, code deployments, token transfers
|
||||
|
||||
## Modeling Standards
|
||||
- Use snake_case for all objects
|
||||
- Implement incremental processing for core tables
|
||||
- Follow source/staging/core/mart layering
|
||||
- Handle chain reorganizations properly
|
||||
- Document chain-specific assumptions
|
||||
|
||||
## Testing Requirements
|
||||
- Validate transaction integrity across receipt chains
|
||||
- Ensure proper token decimal handling
|
||||
- Test cross-shard transaction completeness
|
||||
- Verify action parsing accuracy
|
||||
- Monitor for chain reorganizations
|
||||
|
||||
## Performance Guidelines
|
||||
- Optimize for NEAR's high TPS
|
||||
- Handle large state change volumes efficiently
|
||||
- Index frequently queried dimensions
|
||||
- Consider partition pruning strategies
|
||||
- Implement appropriate clustering keys
|
||||
|
||||
## Documentation
|
||||
- Document RPC data sources
|
||||
- Explain transaction flow assumptions
|
||||
- Note sharding implications
|
||||
- Map entity relationships
|
||||
- Track known data anomalies
|
||||
|
||||
## Metrics Focus
|
||||
- Transaction volumes and success rates
|
||||
- Active accounts and contract usage
|
||||
- Token transfers and balances
|
||||
- Gas consumption patterns
|
||||
- Protocol economics indicators
|
||||
|
||||
## Error Handling
|
||||
- Handle invalid UTF-8 in contract data
|
||||
- Manage receipt execution failures
|
||||
- Track missing block segments
|
||||
- Monitor for RPC inconsistencies
|
||||
- Log unexpected action types
|
||||
@ -103,20 +103,6 @@ The gold layer is organized into domain-specific schemas:
|
||||
- **Stats**: Aggregated metrics and KPIs
|
||||
- **Atlas**: Supply and economic indicators
|
||||
|
||||
## Using dbt docs
|
||||
|
||||
To explore the complete data lineage and documentation:
|
||||
|
||||
1. Run `dbt docs generate` to create the documentation
|
||||
2. Run `dbt docs serve` to start the documentation server
|
||||
3. Navigate to the generated documentation in your browser
|
||||
|
||||
The documentation includes:
|
||||
- Table and column descriptions
|
||||
- Data lineage graphs
|
||||
- Test results and data quality metrics
|
||||
- Model dependencies and relationships
|
||||
|
||||
<llm>
|
||||
<blockchain>NEAR Protocol</blockchain>
|
||||
<aliases>NEAR, NEAR Protocol</aliases>
|
||||
|
||||
32
models/descriptions/atlas__ez_supply.md
Normal file
32
models/descriptions/atlas__ez_supply.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs atlas__ez_supply %}
|
||||
|
||||
## Description
|
||||
This table provides comprehensive daily supply metrics for the NEAR Protocol blockchain, capturing the distribution and categorization of NEAR tokens across different supply categories. The data includes total supply, staked supply, circulating supply, locked supply, and various percentage breakdowns, enabling detailed analysis of token distribution, staking participation, and economic indicators. This easy view provides ready-to-use data for supply analysis, economic modeling, and tokenomics assessment across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Token supply analysis and distribution tracking
|
||||
- Staking participation analysis and yield assessment
|
||||
- Economic modeling and tokenomics analysis
|
||||
- Supply impact analysis of protocol changes
|
||||
- Cross-day supply trend analysis and pattern identification
|
||||
- Lockup and vesting schedule impact assessment
|
||||
- Economic indicator analysis and market health monitoring
|
||||
|
||||
## Important Relationships
|
||||
- Provides supply data for economic analysis and tokenomics modeling
|
||||
- Supports `core.ez_native_daily_balances` with supply context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for supply metrics
|
||||
- Powers economic analysis and market health assessment
|
||||
- Supports governance analytics and staking participation analysis
|
||||
- Provides foundation for all supply-related analytics and reporting
|
||||
|
||||
## Commonly-used Fields
|
||||
- `utc_date`: Essential for time-series analysis and trend detection
|
||||
- `total_supply`: Critical for overall supply analysis and tokenomics assessment
|
||||
- `total_staked_supply` and `total_nonstaked_supply`: Important for staking participation analysis
|
||||
- `circulating_supply`: Essential for market liquidity and economic analysis
|
||||
- `total_locked_supply`: Important for vesting and lockup impact assessment
|
||||
- `perc_locked_supply` and `perc_circulating_supply`: Critical for supply distribution analysis
|
||||
- `perc_staked_locked` and `perc_staked_circulating`: Useful for staking pattern analysis
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/core__dim_address_labels.md
Normal file
31
models/descriptions/core__dim_address_labels.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs core__dim_address_labels %}
|
||||
|
||||
## Description
|
||||
This table contains comprehensive address labeling and categorization data for the NEAR Protocol blockchain, providing human-readable names, project associations, and classification information for accounts and contracts. The data includes both manual and automated labeling from multiple sources, enabling enhanced analytics by providing context about wallet ownership, contract purposes, and project affiliations. This dimension table supports all other gold models by providing enriched address information for improved data interpretation and user experience.
|
||||
|
||||
## Key Use Cases
|
||||
- Enhanced transaction analysis with human-readable address names
|
||||
- Project-specific activity tracking and protocol analysis
|
||||
- Whale and institutional wallet identification and monitoring
|
||||
- Contract categorization and smart contract ecosystem analysis
|
||||
- Compliance and regulatory reporting with entity identification
|
||||
- User experience improvement in analytics dashboards and reports
|
||||
- Cross-protocol address correlation and analysis
|
||||
|
||||
## Important Relationships
|
||||
- Enriches all fact tables by providing address context and labels
|
||||
- Supports `core.ez_token_transfers` with sender and receiver labeling
|
||||
- Enhances `defi.ez_dex_swaps` with protocol and user identification
|
||||
- Improves `defi.ez_bridge_activity` with bridge protocol labeling
|
||||
- Enables better analysis in `nft.ez_nft_sales` with marketplace identification
|
||||
- Powers `stats.ez_core_metrics_hourly` with labeled activity metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `address`: Essential for joining with transaction and transfer data
|
||||
- `address_name`: Critical for human-readable analytics and reporting
|
||||
- `project_name`: Important for protocol-specific analysis and categorization
|
||||
- `label_type` and `label_subtype`: Essential for address categorization and filtering
|
||||
- `l1_label` and `l2_label`: Important for hierarchical classification analysis
|
||||
- `creator`: Useful for understanding label source and reliability
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/core__dim_ft_contract_metadata.md
Normal file
31
models/descriptions/core__dim_ft_contract_metadata.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs core__dim_ft_contract_metadata %}
|
||||
|
||||
## Description
|
||||
This table contains comprehensive metadata for fungible token contracts on the NEAR Protocol blockchain, including token names, symbols, decimal precision, and cross-chain mapping information. The data covers both native NEAR tokens and cross-chain bridged assets, providing essential context for token identification, pricing, and value calculations. This dimension table supports all token-related analytics by providing standardized token information and enabling proper decimal adjustment for accurate value analysis.
|
||||
|
||||
## Key Use Cases
|
||||
- Token identification and metadata enrichment for transfer analysis
|
||||
- Cross-chain token correlation and bridge activity analysis
|
||||
- Token pricing and market data integration
|
||||
- Decimal adjustment for accurate value calculations
|
||||
- Token supply and economics analysis
|
||||
- Multi-chain portfolio tracking and analysis
|
||||
- Token standard compliance and verification
|
||||
|
||||
## Important Relationships
|
||||
- Enriches `core.fact_token_transfers` with token metadata and decimal information
|
||||
- Supports `core.ez_token_transfers` with enhanced token context
|
||||
- Enables `defi.ez_dex_swaps` with token pair identification and pricing
|
||||
- Powers `defi.ez_bridge_activity` with cross-chain token mapping
|
||||
- Supports `price.ez_prices_hourly` with token metadata for price analysis
|
||||
- Enables accurate USD value calculations across all token-related models
|
||||
|
||||
## Commonly-used Fields
|
||||
- `contract_address`: Essential for joining with transfer and swap data
|
||||
- `name` and `symbol`: Critical for human-readable token identification
|
||||
- `decimals`: Important for accurate value calculations and decimal adjustment
|
||||
- `source_chain`: Essential for cross-chain analysis and bridge tracking
|
||||
- `crosschain_token_contract`: Important for multi-chain token correlation
|
||||
- `asset_identifier`: Useful for unique token identification across systems
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__ez_actions.md
Normal file
32
models/descriptions/core__ez_actions.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__ez_actions %}
|
||||
|
||||
## Description
|
||||
This table provides a comprehensive, action-level view of all blockchain activities on NEAR Protocol, combining transaction and receipt data to create detailed action records. Each record represents a specific action within a transaction, including function calls, token transfers, account creation, and other blockchain operations. The table normalizes complex receipt structures into standardized action records, enabling granular analysis of smart contract interactions, user behaviors, and protocol activities across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Detailed smart contract interaction analysis and function call tracking
|
||||
- Action-level user behavior analysis and pattern recognition
|
||||
- Gas consumption analysis at the action level for optimization
|
||||
- Cross-contract call tracking and dependency analysis
|
||||
- Protocol-specific action monitoring and analytics
|
||||
- DeFi protocol interaction analysis and volume tracking
|
||||
- Account creation and management pattern analysis
|
||||
|
||||
## Important Relationships
|
||||
- Combines data from `core.fact_transactions` and `core.fact_receipts` for comprehensive action analysis
|
||||
- Provides detailed context for `core.fact_token_transfers` and `core.ez_token_transfers`
|
||||
- Supports `defi.ez_dex_swaps` with detailed swap action analysis
|
||||
- Enables `defi.ez_bridge_activity` with cross-chain action tracking
|
||||
- Powers `defi.ez_intents` with intent-based action analysis
|
||||
- Supports `stats.ez_core_metrics_hourly` with action-level metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `action_name`: Essential for categorizing and filtering specific action types
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `tx_hash` and `receipt_id`: Critical for linking to transaction and receipt context
|
||||
- `action_data`: Important for detailed action parameter analysis
|
||||
- `receipt_signer_id` and `receipt_receiver_id`: Essential for user and contract analysis
|
||||
- `receipt_gas_burnt`: Important for gas consumption analysis and optimization
|
||||
- `action_index`: Critical for action ordering within transactions
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__ez_native_daily_balances.md
Normal file
32
models/descriptions/core__ez_native_daily_balances.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__ez_native_daily_balances %}
|
||||
|
||||
## Description
|
||||
This table provides daily balance snapshots for all accounts on the NEAR Protocol blockchain, capturing liquid balances, staking positions, lockup accounts, and storage usage. The data includes both regular accounts and lockup accounts (used for vesting schedules and staking), providing comprehensive balance tracking across different account types and balance categories. This table enables historical balance analysis, staking behavior tracking, and economic analysis of the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Historical balance analysis and account growth tracking
|
||||
- Staking behavior analysis and validator participation monitoring
|
||||
- Lockup account analysis and vesting schedule tracking
|
||||
- Storage usage analysis and network resource consumption
|
||||
- Economic analysis of liquid vs staked token distribution
|
||||
- Account activity correlation with balance changes
|
||||
- Compliance and audit trail analysis for account balances
|
||||
|
||||
## Important Relationships
|
||||
- Provides balance context for `core.fact_token_transfers` and `core.ez_token_transfers`
|
||||
- Supports `gov.ez_staking_actions` with balance impact analysis
|
||||
- Enables `gov.ez_lockup_actions` with lockup balance tracking
|
||||
- Powers `stats.ez_core_metrics_hourly` with balance aggregation metrics
|
||||
- Supports `atlas.ez_supply` with supply distribution analysis
|
||||
- Provides foundation for account-level analytics and reporting
|
||||
|
||||
## Commonly-used Fields
|
||||
- `account_id`: Essential for account-specific analysis and balance tracking
|
||||
- `epoch_date`: Primary field for time-series analysis and balance history
|
||||
- `liquid`: Critical for available balance analysis and spending patterns
|
||||
- `staked`: Important for staking participation and validator analysis
|
||||
- `lockup_liquid` and `lockup_staked`: Essential for lockup account analysis
|
||||
- `storage_usage`: Useful for network resource consumption analysis
|
||||
- `reward`: Important for staking reward analysis and economic incentives
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__ez_token_transfers.md
Normal file
32
models/descriptions/core__ez_token_transfers.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__ez_token_transfers %}
|
||||
|
||||
## Description
|
||||
This table provides an enhanced view of all token transfers on the NEAR Protocol blockchain, combining raw transfer data with token metadata, pricing information, and decimal adjustments. The table includes both raw and adjusted amounts, USD values, and comprehensive token context, making it the primary table for token flow analysis and economic calculations. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for analytics, reporting, and business intelligence workflows.
|
||||
|
||||
## Key Use Cases
|
||||
- Token flow analysis with accurate decimal-adjusted amounts and USD values
|
||||
- DeFi protocol volume analysis and liquidity monitoring
|
||||
- Token economics analysis and market impact assessment
|
||||
- Cross-token comparison and portfolio analysis
|
||||
- Whale movement tracking with value context
|
||||
- Token distribution analysis and holder behavior tracking
|
||||
- Economic impact analysis of token transfers and market movements
|
||||
|
||||
## Important Relationships
|
||||
- Enhances `core.fact_token_transfers` with pricing and metadata from `price.ez_prices_hourly`
|
||||
- Combines token metadata from `core.dim_ft_contract_metadata` for complete token context
|
||||
- Supports `defi.ez_dex_swaps` with accurate token pricing and amounts
|
||||
- Enables `defi.ez_bridge_activity` with cross-chain value analysis
|
||||
- Powers `stats.ez_core_metrics_hourly` with aggregated transfer values
|
||||
- Provides foundation for all token-related analytics and reporting
|
||||
|
||||
## Commonly-used Fields
|
||||
- `amount_raw` and `amount_precise`: Essential for accurate token amount analysis
|
||||
- `amount_usd`: Critical for economic analysis and value calculations
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `from_address` and `to_address`: Important for flow analysis and network mapping
|
||||
- `contract_address`: Essential for token-specific analysis and filtering
|
||||
- `symbol` and `decimals`: Important for token identification and decimal handling
|
||||
- `token_price`: Useful for price trend analysis and market impact assessment
|
||||
|
||||
{% enddocs %}
|
||||
1
models/descriptions/core__fact_blocks.md
Normal file
1
models/descriptions/core__fact_blocks.md
Normal file
@ -0,0 +1 @@
|
||||
|
||||
30
models/descriptions/core__fact_developer_activity.md
Normal file
30
models/descriptions/core__fact_developer_activity.md
Normal file
@ -0,0 +1,30 @@
|
||||
{% docs core__fact_developer_activity %}
|
||||
|
||||
## Description
|
||||
This table contains developer activity data sourced from GitHub repositories related to the NEAR Protocol ecosystem, capturing code commits, repository statistics, and development metrics. The data includes information about NEAR-related projects, developer contributions, and ecosystem growth indicators. This table provides insights into the developer community activity, project development velocity, and overall ecosystem health through external development metrics.
|
||||
|
||||
## Key Use Cases
|
||||
- Developer ecosystem analysis and community growth tracking
|
||||
- Project development velocity and activity monitoring
|
||||
- Code contribution analysis and developer engagement metrics
|
||||
- Repository health and maintenance activity tracking
|
||||
- Ecosystem project discovery and categorization
|
||||
- Developer retention and activity pattern analysis
|
||||
- Cross-project collaboration and dependency analysis
|
||||
|
||||
## Important Relationships
|
||||
- Provides external context for blockchain activity analysis
|
||||
- Supports ecosystem health metrics in `stats.ez_core_metrics_hourly`
|
||||
- Enables correlation between developer activity and protocol usage
|
||||
- Provides foundation for developer-focused analytics and reporting
|
||||
- Supports project categorization and ecosystem mapping
|
||||
|
||||
## Commonly-used Fields
|
||||
- `repo_owner` and `repo_name`: Essential for project identification and categorization
|
||||
- `endpoint_name`: Important for understanding the type of GitHub data captured
|
||||
- `data`: Critical for detailed developer activity analysis and metrics
|
||||
- `provider`: Useful for data source identification and reliability assessment
|
||||
- `snapshot_timestamp`: Primary field for time-series analysis of developer activity
|
||||
- `endpoint_github`: Important for linking to specific GitHub API endpoints
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__fact_logs.md
Normal file
32
models/descriptions/core__fact_logs.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__fact_logs %}
|
||||
|
||||
## Description
|
||||
This table contains all event logs emitted by smart contracts on the NEAR Protocol blockchain, capturing structured event data including token transfers, contract interactions, and custom application events. Logs represent the standardized way that smart contracts communicate state changes and events to external systems, following NEAR's event logging standards. This table provides the foundation for understanding contract behavior, token movements, and application-specific events across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Token transfer tracking and balance analysis
|
||||
- Smart contract event monitoring and analytics
|
||||
- DeFi protocol activity analysis and volume tracking
|
||||
- NFT minting and transfer event analysis
|
||||
- Cross-contract communication tracking
|
||||
- Application-specific event analysis and user behavior tracking
|
||||
- Compliance and audit trail analysis
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_receipts` through receipt_id for execution context
|
||||
- Provides event data for `core.fact_token_transfers` and `core.ez_token_transfers`
|
||||
- Supports `defi.ez_dex_swaps` and `defi.ez_bridge_activity` through event parsing
|
||||
- Enables analysis in `nft.ez_nft_sales` through NFT-related events
|
||||
- Powers `stats.ez_core_metrics_hourly` for aggregated event metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `log_index`: Essential for event ordering within transactions and receipts
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `receiver_id` and `predecessor_id`: Critical for contract interaction analysis
|
||||
- `clean_log`: Important for event parsing and structured data analysis
|
||||
- `event_standard`: Essential for identifying standardized event types
|
||||
- `receipt_succeeded`: Important for filtering successful events only
|
||||
- `gas_burnt`: Useful for gas consumption analysis and cost optimization
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__fact_receipts.md
Normal file
32
models/descriptions/core__fact_receipts.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__fact_receipts %}
|
||||
|
||||
## Description
|
||||
This table contains all receipt execution outcomes on the NEAR Protocol blockchain, capturing the results of transaction processing including gas consumption, execution status, logs, and cross-contract communication details. Receipts represent the execution units in NEAR's sharding architecture and contain the actual state changes, function calls, and event emissions that occur during transaction processing. This table provides the foundation for understanding smart contract execution, cross-shard communication, and the complete transaction lifecycle from submission to final state changes.
|
||||
|
||||
## Key Use Cases
|
||||
- Smart contract execution analysis and performance monitoring
|
||||
- Cross-contract call tracking and dependency analysis
|
||||
- Gas consumption analysis and optimization studies
|
||||
- Execution failure investigation and error pattern analysis
|
||||
- Cross-shard transaction flow analysis and sharding efficiency
|
||||
- Event log analysis and contract interaction patterns
|
||||
- State change tracking and account balance analysis
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides execution context for `core.fact_logs` and `core.fact_token_transfers`
|
||||
- Supports `core.ez_actions` for detailed action-level analysis
|
||||
- Enables analysis in `defi.ez_dex_swaps` and `defi.ez_bridge_activity` through receipt outcomes
|
||||
- Powers `stats.ez_core_metrics_hourly` for aggregated execution metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `receipt_id`: Essential for unique receipt identification and execution tracking
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `receiver_id` and `predecessor_id`: Critical for cross-contract call analysis and flow tracking
|
||||
- `gas_burnt`: Important for gas consumption analysis and cost optimization
|
||||
- `receipt_succeeded`: Essential for success rate analysis and failure investigation
|
||||
- `logs`: Critical for event analysis and contract interaction patterns
|
||||
- `outcome`: Important for detailed execution analysis and state change tracking
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__fact_token_transfers.md
Normal file
32
models/descriptions/core__fact_token_transfers.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__fact_token_transfers %}
|
||||
|
||||
## Description
|
||||
This table contains all token transfers on the NEAR Protocol blockchain, capturing movements of native NEAR tokens, fungible tokens (NEP-141), and other token types across accounts and contracts. The data includes both direct transfers and complex token operations like minting, deposits, and liquidity operations. This table provides the foundation for understanding token economics, user behavior, and DeFi activity across the NEAR ecosystem, supporting comprehensive token flow analysis and balance tracking.
|
||||
|
||||
## Key Use Cases
|
||||
- Token flow analysis and whale movement tracking
|
||||
- DeFi protocol volume analysis and liquidity monitoring
|
||||
- Token distribution analysis and holder behavior tracking
|
||||
- Cross-contract token movement analysis
|
||||
- Economic analysis of token transfers and value flows
|
||||
- Compliance and audit trail analysis for token movements
|
||||
- Token minting and burning pattern analysis
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides transfer data for `core.ez_token_transfers` with enhanced metadata
|
||||
- Supports `defi.ez_dex_swaps` and `defi.ez_bridge_activity` through transfer events
|
||||
- Enables analysis in `nft.ez_nft_sales` through token payment flows
|
||||
- Powers `stats.ez_core_metrics_hourly` for aggregated transfer metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `from_address` and `to_address`: Critical for flow analysis and network mapping
|
||||
- `contract_address`: Important for token-specific analysis and contract tracking
|
||||
- `amount_unadj`: Essential for value calculations and economic analysis
|
||||
- `transfer_type`: Important for categorizing different token standards
|
||||
- `transfer_action`: Critical for understanding the specific operation type
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/core__fact_transactions.md
Normal file
32
models/descriptions/core__fact_transactions.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs core__fact_transactions %}
|
||||
|
||||
## Description
|
||||
This table contains all transactions processed on the NEAR Protocol blockchain, providing comprehensive transaction metadata including signer and receiver information, gas consumption, fees, and execution status. The data captures the complete transaction lifecycle from submission to finalization, including cryptographic signatures, nonce values, and gas mechanics. This table serves as the primary fact table for transaction-level analytics and provides the foundation for understanding user activity, contract interactions, and network utilization patterns.
|
||||
|
||||
## Key Use Cases
|
||||
- Transaction volume analysis and network activity monitoring
|
||||
- User behavior analysis and wallet activity tracking
|
||||
- Gas consumption analysis and fee optimization studies
|
||||
- Contract interaction analysis and smart contract usage patterns
|
||||
- Transaction success rate analysis and failure investigation
|
||||
- Cross-account transaction flow analysis and network mapping
|
||||
- Economic analysis of transaction fees and gas pricing
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_blocks` through block_id for temporal and block context
|
||||
- Connects to `core.fact_receipts` through tx_hash for execution outcome details
|
||||
- Provides transaction context for `core.fact_logs` and `core.fact_token_transfers`
|
||||
- Supports `core.ez_actions` for detailed action-level analysis
|
||||
- Enables analysis in `defi.ez_dex_swaps` and `defi.ez_bridge_activity` through transaction context
|
||||
- Powers `stats.ez_core_metrics_hourly` for aggregated transaction metrics
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for unique transaction identification and blockchain verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `tx_signer` and `tx_receiver`: Critical for user activity analysis and network mapping
|
||||
- `gas_used` and `transaction_fee`: Important for economic analysis and cost optimization
|
||||
- `tx_succeeded`: Essential for success rate analysis and failure investigation
|
||||
- `attached_gas`: Important for understanding gas mechanics and transaction planning
|
||||
- `nonce`: Critical for transaction ordering and replay protection analysis
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/defi__ez_bridge_activity.md
Normal file
31
models/descriptions/defi__ez_bridge_activity.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs defi__ez_bridge_activity %}
|
||||
|
||||
## Description
|
||||
This table provides an enhanced view of all cross-chain bridge transactions on the NEAR Protocol blockchain, combining raw bridge data with token metadata, pricing information, and cross-chain mapping details. The table includes both raw and adjusted amounts, USD values, and comprehensive token context across multiple bridge protocols including Rainbow Bridge, Wormhole, Multichain, Allbridge, and Omni. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for cross-chain analytics and bridge analysis.
|
||||
|
||||
## Key Use Cases
|
||||
- Cross-chain bridge volume analysis with accurate decimal-adjusted amounts and USD values
|
||||
- Bridge protocol comparison and performance benchmarking with value context
|
||||
- Cross-chain token flow analysis and liquidity tracking
|
||||
- Bridge security analysis and risk assessment with economic impact
|
||||
- Multi-chain portfolio tracking and analysis
|
||||
- Bridge protocol adoption and user behavior analysis
|
||||
- Cross-chain arbitrage opportunity detection with value calculations
|
||||
|
||||
## Important Relationships
|
||||
- Enhances `defi.fact_bridge_activity` with pricing and metadata from `price.ez_prices_hourly`
|
||||
- Combines token metadata from `core.dim_ft_contract_metadata` for complete token context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for bridge metrics
|
||||
- Provides foundation for all cross-chain analytics and reporting
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `amount` and `amount_usd`: Essential for accurate bridge volume analysis
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `source_chain` and `destination_chain`: Critical for cross-chain flow analysis
|
||||
- `platform`: Important for bridge protocol comparison and analysis
|
||||
- `direction`: Critical for understanding bridge flow direction (inbound/outbound)
|
||||
- `symbol`: Important for token identification and cross-chain mapping
|
||||
- `token_address`: Essential for token-specific bridge activity analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__ez_dex_swaps.md
Normal file
32
models/descriptions/defi__ez_dex_swaps.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__ez_dex_swaps %}
|
||||
|
||||
## Description
|
||||
This table provides an enhanced view of all decentralized exchange (DEX) swap transactions on the NEAR Protocol blockchain, combining raw swap data with token metadata, pricing information, and decimal adjustments. The table includes both raw and adjusted amounts, USD values, and comprehensive token context, making it the primary table for DEX analytics and trading analysis. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for DeFi analytics, reporting, and business intelligence workflows.
|
||||
|
||||
## Key Use Cases
|
||||
- DEX trading volume analysis with accurate decimal-adjusted amounts and USD values
|
||||
- Token pair liquidity analysis and trading pattern identification
|
||||
- Price impact analysis and slippage calculation with USD context
|
||||
- DEX protocol comparison and performance benchmarking
|
||||
- Arbitrage opportunity detection and analysis
|
||||
- Trading bot activity monitoring and pattern recognition
|
||||
- DeFi protocol integration analysis and cross-protocol flows
|
||||
|
||||
## Important Relationships
|
||||
- Enhances `defi.fact_dex_swaps` with pricing and metadata from `price.ez_prices_hourly`
|
||||
- Combines token metadata from `core.dim_ft_contract_metadata` for complete token context
|
||||
- Supports `defi.ez_intents` with swap execution analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for DeFi metrics
|
||||
- Provides foundation for all DEX-related analytics and reporting
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `amount_in` and `amount_out`: Essential for accurate swap amount analysis
|
||||
- `amount_in_usd` and `amount_out_usd`: Critical for economic analysis and value calculations
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `trader`: Important for user behavior analysis and trading patterns
|
||||
- `platform`: Essential for DEX protocol analysis and comparison
|
||||
- `symbol_in` and `symbol_out`: Important for token pair identification and analysis
|
||||
- `pool_id`: Useful for liquidity pool analysis and performance tracking
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/defi__ez_intents.md
Normal file
31
models/descriptions/defi__ez_intents.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs defi__ez_intents %}
|
||||
|
||||
## Description
|
||||
This table provides an enhanced view of all intent-based transactions on the NEAR Protocol blockchain, combining raw intent data with token metadata, pricing information, and cross-chain mapping details. The table includes both NEP-245 and DIP-4 standard intents with decimal adjustments, USD values, and comprehensive token context. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for intent-based trading analysis and MEV protection mechanism evaluation.
|
||||
|
||||
## Key Use Cases
|
||||
- Intent-based trading analysis with accurate decimal-adjusted amounts and USD values
|
||||
- MEV protection mechanism effectiveness analysis with economic impact
|
||||
- User behavior analysis in intent-driven protocols with value context
|
||||
- Cross-protocol intent execution tracking and performance comparison
|
||||
- Intent fulfillment rate analysis and optimization with value calculations
|
||||
- Referral program analysis and user acquisition tracking
|
||||
- Intent-based DeFi protocol performance monitoring and benchmarking
|
||||
|
||||
## Important Relationships
|
||||
- Enhances `defi.fact_intents` with pricing and metadata from `price.ez_prices_hourly`
|
||||
- Combines token metadata from `core.dim_ft_contract_metadata` for complete token context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for intent metrics
|
||||
- Provides foundation for all intent-based analytics and reporting
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `amount` and `amount_usd`: Essential for accurate intent value analysis
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `log_event`: Critical for intent type classification and analysis
|
||||
- `owner_id`: Important for user behavior analysis and intent tracking
|
||||
- `token_id` and `symbol`: Essential for token-specific intent analysis
|
||||
- `referral`: Important for referral program analysis and user acquisition
|
||||
- `receipt_succeeded`: Critical for intent fulfillment rate analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__ez_lending.md
Normal file
32
models/descriptions/defi__ez_lending.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__ez_lending %}
|
||||
|
||||
## Description
|
||||
This table provides an enhanced view of all lending protocol transactions on the NEAR Protocol blockchain, primarily capturing activities on the Burrow lending protocol with token metadata, pricing information, and decimal adjustments. The table includes both raw and adjusted amounts, USD values, and comprehensive token context, making it the primary table for lending analytics and risk assessment. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for DeFi lending analysis and reporting.
|
||||
|
||||
## Key Use Cases
|
||||
- Lending protocol volume analysis with accurate decimal-adjusted amounts and USD values
|
||||
- Borrowing and lending pattern analysis and risk assessment with economic context
|
||||
- Collateral utilization analysis and liquidation monitoring with value calculations
|
||||
- Interest rate impact analysis and yield optimization
|
||||
- Protocol health monitoring and risk metrics calculation
|
||||
- User behavior analysis in lending protocols with value context
|
||||
- Cross-protocol lending comparison and performance benchmarking
|
||||
|
||||
## Important Relationships
|
||||
- Enhances `defi.fact_lending` with pricing and metadata from `price.ez_prices_hourly`
|
||||
- Combines token metadata from `core.dim_ft_contract_metadata` for complete token context
|
||||
- Supports `defi.ez_intents` with lending intent analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for lending metrics
|
||||
- Provides foundation for all lending-related analytics and reporting
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `amount` and `amount_usd`: Essential for accurate lending volume analysis
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `actions`: Critical for lending action classification and analysis
|
||||
- `sender_id`: Important for user behavior analysis and lending patterns
|
||||
- `platform`: Critical for protocol-specific analysis and comparison
|
||||
- `symbol`: Important for token identification and lending analysis
|
||||
- `token_address`: Essential for token-specific lending activity analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__fact_bridge_activity.md
Normal file
32
models/descriptions/defi__fact_bridge_activity.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__fact_bridge_activity %}
|
||||
|
||||
## Description
|
||||
This table contains all cross-chain bridge transactions on the NEAR Protocol blockchain, capturing token movements between NEAR and other blockchains through various bridge protocols including Rainbow Bridge, Wormhole, Multichain, Allbridge, and Omni. The data includes bridge-specific details such as source/destination chains, token addresses, amounts, and bridge protocol metadata. This table provides the foundation for cross-chain analytics, bridge volume analysis, and multi-chain ecosystem monitoring.
|
||||
|
||||
## Key Use Cases
|
||||
- Cross-chain bridge volume analysis and flow monitoring
|
||||
- Bridge protocol comparison and performance benchmarking
|
||||
- Cross-chain token flow analysis and liquidity tracking
|
||||
- Bridge security analysis and risk assessment
|
||||
- Multi-chain portfolio tracking and analysis
|
||||
- Bridge protocol adoption and user behavior analysis
|
||||
- Cross-chain arbitrage opportunity detection
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides bridge data for `defi.ez_bridge_activity` with enhanced metadata
|
||||
- Supports `defi.ez_intents` with cross-chain intent analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for bridge metrics
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `source_chain` and `destination_chain`: Critical for cross-chain flow analysis
|
||||
- `token_address`: Important for token-specific bridge activity analysis
|
||||
- `amount_raw` and `amount_adj`: Essential for bridge volume calculations
|
||||
- `platform`: Important for bridge protocol comparison and analysis
|
||||
- `direction`: Critical for understanding bridge flow direction (inbound/outbound)
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__fact_dex_swaps.md
Normal file
32
models/descriptions/defi__fact_dex_swaps.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__fact_dex_swaps %}
|
||||
|
||||
## Description
|
||||
This table contains all decentralized exchange (DEX) swap transactions on the NEAR Protocol blockchain, capturing token swaps across various DEX protocols including Ref Finance, Orderly Network, and other automated market makers. The data includes swap details such as input/output tokens, amounts, prices, and protocol-specific metadata. This table provides the foundation for DeFi analytics, trading volume analysis, and liquidity pool performance tracking across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- DEX trading volume analysis and market activity monitoring
|
||||
- Token pair liquidity analysis and trading pattern identification
|
||||
- Price impact analysis and slippage calculation
|
||||
- DEX protocol comparison and performance benchmarking
|
||||
- Arbitrage opportunity detection and analysis
|
||||
- Trading bot activity monitoring and pattern recognition
|
||||
- DeFi protocol integration analysis and cross-protocol flows
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides swap data for `defi.ez_dex_swaps` with enhanced metadata and pricing
|
||||
- Supports `defi.ez_intents` with swap execution analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for DeFi metrics
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `token_in` and `token_out`: Critical for token pair analysis and trading patterns
|
||||
- `amount_in_raw` and `amount_out_raw`: Important for swap size analysis and volume calculations
|
||||
- `receiver_id` and `signer_id`: Essential for user behavior analysis and trader identification
|
||||
- `swap_index`: Important for multi-swap transaction analysis
|
||||
- `swap_input_data`: Useful for detailed swap parameter analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__fact_intents.md
Normal file
32
models/descriptions/defi__fact_intents.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__fact_intents %}
|
||||
|
||||
## Description
|
||||
This table contains all intent-based transactions on the NEAR Protocol blockchain, capturing user intents for token transfers, swaps, and other DeFi operations through the intents.near protocol. The data includes both NEP-245 and DIP-4 standard intents, providing comprehensive tracking of intent creation, execution, and fulfillment. This table enables analysis of intent-based trading patterns, MEV protection mechanisms, and user behavior in intent-driven DeFi protocols.
|
||||
|
||||
## Key Use Cases
|
||||
- Intent-based trading analysis and pattern recognition
|
||||
- MEV protection mechanism effectiveness analysis
|
||||
- User behavior analysis in intent-driven protocols
|
||||
- Cross-protocol intent execution tracking
|
||||
- Intent fulfillment rate analysis and optimization
|
||||
- Referral program analysis and user acquisition tracking
|
||||
- Intent-based DeFi protocol performance monitoring
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides intent data for `defi.ez_intents` with enhanced metadata
|
||||
- Supports `defi.ez_dex_swaps` with intent execution analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for intent metrics
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `log_event`: Critical for intent type classification and analysis
|
||||
- `owner_id`: Important for user behavior analysis and intent tracking
|
||||
- `amount_raw` and `token_id`: Essential for intent value analysis
|
||||
- `referral`: Important for referral program analysis and user acquisition
|
||||
- `receipt_succeeded`: Critical for intent fulfillment rate analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/defi__fact_lending.md
Normal file
32
models/descriptions/defi__fact_lending.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs defi__fact_lending %}
|
||||
|
||||
## Description
|
||||
This table contains all lending protocol transactions on the NEAR Protocol blockchain, primarily capturing activities on the Burrow lending protocol. The data includes lending actions such as deposits, withdrawals, borrows, and repayments, along with associated token amounts and protocol metadata. This table provides the foundation for lending analytics, protocol risk assessment, and DeFi lending market analysis across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Lending protocol volume analysis and market activity monitoring
|
||||
- Borrowing and lending pattern analysis and risk assessment
|
||||
- Collateral utilization analysis and liquidation monitoring
|
||||
- Interest rate impact analysis and yield optimization
|
||||
- Protocol health monitoring and risk metrics calculation
|
||||
- User behavior analysis in lending protocols
|
||||
- Cross-protocol lending comparison and performance benchmarking
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides lending data for `defi.ez_lending` with enhanced metadata
|
||||
- Supports `defi.ez_intents` with lending intent analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for lending metrics
|
||||
- Powers cross-protocol analysis with other DeFi activities
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `actions`: Critical for lending action classification and analysis
|
||||
- `token_address`: Important for token-specific lending analysis
|
||||
- `amount_raw` and `amount_adj`: Essential for lending volume calculations
|
||||
- `sender_id`: Important for user behavior analysis and lending patterns
|
||||
- `platform`: Critical for protocol-specific analysis and comparison
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/gov__dim_staking_pools.md
Normal file
32
models/descriptions/gov__dim_staking_pools.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs gov__dim_staking_pools %}
|
||||
|
||||
## Description
|
||||
This table contains comprehensive metadata for staking pools on the NEAR Protocol blockchain, including pool addresses, owners, reward fee structures, and pool creation details. The data covers all staking pools that participate in NEAR's proof-of-stake consensus mechanism, providing essential context for staking analysis, validator performance tracking, and governance participation. This dimension table supports all staking-related analytics by providing standardized pool information and enabling proper staking pool categorization and analysis.
|
||||
|
||||
## Key Use Cases
|
||||
- Staking pool identification and metadata enrichment
|
||||
- Validator performance analysis and pool comparison
|
||||
- Staking pool fee structure analysis and optimization
|
||||
- Pool creation and lifecycle tracking
|
||||
- Cross-pool performance benchmarking
|
||||
- Staking pool discovery and participation analysis
|
||||
- Governance participation tracking and analysis
|
||||
|
||||
## Important Relationships
|
||||
- Enriches `gov.fact_staking_actions` with pool metadata and context
|
||||
- Supports `gov.fact_staking_pool_balances` with pool identification
|
||||
- Provides metadata for `gov.ez_staking_actions` with enhanced pool context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for staking metrics
|
||||
- Supports cross-pool analysis and validator performance comparison
|
||||
- Powers governance analytics and staking participation analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `address`: Essential for joining with staking action and balance data
|
||||
- `owner`: Critical for validator identification and ownership analysis
|
||||
- `reward_fee_fraction`: Important for fee structure analysis and optimization
|
||||
- `tx_hash`: Essential for pool creation transaction linking and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and pool lifecycle tracking
|
||||
- `tx_type`: Important for pool operation classification and analysis
|
||||
- `inserted_timestamp`: Useful for pool discovery timeline analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/gov__fact_lockup_actions.md
Normal file
32
models/descriptions/gov__fact_lockup_actions.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs gov__fact_lockup_actions %}
|
||||
|
||||
## Description
|
||||
This table contains all lockup account transactions on the NEAR Protocol blockchain, capturing lockup creation, vesting schedules, and release mechanisms. The data includes lockup amounts, duration periods, vesting schedules, and associated metadata, providing comprehensive tracking of token lockups and vesting arrangements. This table provides the foundation for lockup analytics, vesting schedule analysis, and token release tracking across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Lockup account analysis and vesting schedule tracking
|
||||
- Token release analysis and unlock pattern identification
|
||||
- Vesting schedule compliance monitoring and analysis
|
||||
- Lockup duration analysis and trend identification
|
||||
- Cross-account lockup comparison and performance analysis
|
||||
- Token distribution analysis and supply impact assessment
|
||||
- Governance token lockup analysis and voting power tracking
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides lockup data for governance analytics and vesting analysis
|
||||
- Supports `core.ez_native_daily_balances` with lockup balance tracking
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for lockup metrics
|
||||
- Powers supply analysis and token distribution studies
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `lockup_account_id` and `owner_account_id`: Critical for account identification and ownership tracking
|
||||
- `deposit`: Important for lockup amount analysis and value tracking
|
||||
- `lockup_duration` and `release_duration`: Essential for vesting schedule analysis
|
||||
- `lockup_timestamp` and `lockup_timestamp_ntz`: Important for timeline analysis and unlock tracking
|
||||
- `vesting_schedule`: Critical for vesting pattern analysis and compliance monitoring
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/gov__fact_staking_actions.md
Normal file
32
models/descriptions/gov__fact_staking_actions.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs gov__fact_staking_actions %}
|
||||
|
||||
## Description
|
||||
This table contains all staking-related transactions on the NEAR Protocol blockchain, capturing staking actions such as deposits, withdrawals, and reward distributions. The data includes staking amounts, action types, and associated metadata, providing comprehensive tracking of staking participation and validator interactions. This table provides the foundation for staking analytics, validator performance analysis, and governance participation tracking across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Staking participation analysis and user behavior tracking
|
||||
- Validator performance analysis and staking pool comparison
|
||||
- Staking reward analysis and yield optimization
|
||||
- Staking pattern analysis and trend identification
|
||||
- Cross-pool staking comparison and performance benchmarking
|
||||
- Staking pool health monitoring and risk assessment
|
||||
- Governance participation analysis and voting power tracking
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides staking data for `gov.ez_staking_actions` with enhanced metadata
|
||||
- Supports `gov.fact_staking_pool_balances` with action impact analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for staking metrics
|
||||
- Powers cross-pool analysis and validator performance comparison
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `action`: Critical for staking action classification and analysis
|
||||
- `amount`: Important for staking volume analysis and participation tracking
|
||||
- `address`: Essential for staking pool identification and analysis
|
||||
- `signer_id`: Important for user behavior analysis and staking patterns
|
||||
- `predecessor_id`: Useful for action flow tracking and context analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/gov__fact_staking_pool_balances.md
Normal file
32
models/descriptions/gov__fact_staking_pool_balances.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs gov__fact_staking_pool_balances %}
|
||||
|
||||
## Description
|
||||
This table contains all staking pool balance changes on the NEAR Protocol blockchain, capturing the dynamic balance updates of staking pools as tokens are deposited, withdrawn, or rewards are distributed. The data includes balance amounts, pool addresses, and associated metadata, providing comprehensive tracking of staking pool liquidity and performance. This table provides the foundation for staking pool analytics, validator performance analysis, and pool health monitoring across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Staking pool balance analysis and liquidity monitoring
|
||||
- Validator performance tracking and pool comparison
|
||||
- Staking pool health assessment and risk analysis
|
||||
- Balance change pattern analysis and trend identification
|
||||
- Cross-pool balance comparison and performance benchmarking
|
||||
- Staking pool growth analysis and adoption tracking
|
||||
- Governance participation analysis and voting power distribution
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides balance data for `gov.fact_staking_pool_daily_balances` with aggregated metrics
|
||||
- Supports `gov.fact_staking_actions` with balance impact analysis
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for staking metrics
|
||||
- Powers cross-pool analysis and validator performance comparison
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `balance`: Critical for pool balance analysis and liquidity assessment
|
||||
- `address`: Essential for staking pool identification and analysis
|
||||
- `receipt_object_id`: Important for action-level analysis and receipt context
|
||||
- `block_id`: Useful for temporal ordering and block-level analysis
|
||||
- `inserted_timestamp`: Important for data freshness and update tracking
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/gov__fact_staking_pool_daily_balances.md
Normal file
31
models/descriptions/gov__fact_staking_pool_daily_balances.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs gov__fact_staking_pool_daily_balances %}
|
||||
|
||||
## Description
|
||||
This table contains daily balance snapshots for all staking pools on the NEAR Protocol blockchain, providing aggregated daily balance data for staking pool analysis and performance tracking. The data includes daily balance amounts, pool addresses, and associated metadata, enabling historical analysis of staking pool growth, performance trends, and liquidity patterns. This table provides the foundation for staking pool analytics, validator performance analysis, and long-term trend identification across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Staking pool growth analysis and historical performance tracking
|
||||
- Daily balance trend analysis and pattern identification
|
||||
- Cross-pool performance comparison and benchmarking
|
||||
- Staking pool health monitoring and risk assessment
|
||||
- Long-term validator performance analysis and trend identification
|
||||
- Staking adoption analysis and participation tracking
|
||||
- Governance participation analysis and voting power distribution over time
|
||||
|
||||
## Important Relationships
|
||||
- Aggregates data from `gov.fact_staking_pool_balances` for daily analysis
|
||||
- Provides daily balance data for staking pool analytics and reporting
|
||||
- Supports `gov.fact_staking_actions` with historical balance context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for staking metrics
|
||||
- Powers cross-pool analysis and long-term validator performance comparison
|
||||
- Supports governance analytics and staking participation trend analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `date`: Essential for time-series analysis and trend detection
|
||||
- `balance`: Critical for daily balance analysis and performance assessment
|
||||
- `address`: Essential for staking pool identification and analysis
|
||||
- `fact_staking_pool_daily_balances_id`: Important for unique record identification
|
||||
- `inserted_timestamp`: Useful for data freshness and update tracking
|
||||
- `modified_timestamp`: Important for data quality and update monitoring
|
||||
|
||||
{% enddocs %}
|
||||
30
models/descriptions/nft__dim_nft_contract_metadata.md
Normal file
30
models/descriptions/nft__dim_nft_contract_metadata.md
Normal file
@ -0,0 +1,30 @@
|
||||
{% docs nft__dim_nft_contract_metadata %}
|
||||
|
||||
## Description
|
||||
This table contains comprehensive metadata for NFT contracts on the NEAR Protocol blockchain, including contract names, symbols, base URIs, and token counts. The data covers NFT collections and individual NFT contracts, providing essential context for NFT identification, collection analysis, and metadata enrichment. This dimension table supports all NFT-related analytics by providing standardized contract information and enabling proper NFT categorization and analysis.
|
||||
|
||||
## Key Use Cases
|
||||
- NFT collection identification and categorization
|
||||
- NFT contract analysis and collection metadata enrichment
|
||||
- NFT marketplace integration and collection discovery
|
||||
- NFT collection performance tracking and analysis
|
||||
- Cross-collection comparison and benchmarking
|
||||
- NFT ecosystem mapping and collection discovery
|
||||
- NFT metadata standardization and quality assessment
|
||||
|
||||
## Important Relationships
|
||||
- Enriches `nft.fact_nft_mints` with collection metadata and contract information
|
||||
- Supports `nft.fact_nft_transfers` with contract context and collection details
|
||||
- Provides metadata for `nft.ez_nft_sales` with enhanced collection information
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for NFT metrics
|
||||
- Supports cross-collection analysis and ecosystem mapping
|
||||
|
||||
## Commonly-used Fields
|
||||
- `contract_address`: Essential for joining with NFT transaction and transfer data
|
||||
- `name` and `symbol`: Critical for human-readable collection identification
|
||||
- `base_uri`: Important for NFT metadata access and collection exploration
|
||||
- `tokens`: Useful for collection size analysis and token count tracking
|
||||
- `icon`: Important for collection branding and visual identification
|
||||
- `inserted_timestamp`: Useful for collection discovery timeline analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/nft__ez_nft_sales.md
Normal file
32
models/descriptions/nft__ez_nft_sales.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs nft__ez_nft_sales %}
|
||||
|
||||
## Description
|
||||
This table provides a comprehensive view of all NFT sales on the NEAR Protocol blockchain, combining minting and transfer data with marketplace information, pricing details, and fee structures. The table includes both raw and USD prices, platform fees, royalties, and affiliate information, making it the primary table for NFT marketplace analytics and sales analysis. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for NFT analytics, reporting, and business intelligence workflows.
|
||||
|
||||
## Key Use Cases
|
||||
- NFT marketplace volume analysis and sales performance tracking
|
||||
- NFT pricing analysis and market trend identification
|
||||
- Platform fee analysis and marketplace economics assessment
|
||||
- Royalty tracking and creator revenue analysis
|
||||
- Affiliate program analysis and user acquisition tracking
|
||||
- Cross-platform NFT sales comparison and performance benchmarking
|
||||
- NFT collection performance analysis and market health monitoring
|
||||
|
||||
## Important Relationships
|
||||
- Combines data from `nft.fact_nft_mints` and `nft.fact_nft_transfers` for comprehensive sales analysis
|
||||
- Provides sales data for marketplace analytics and platform comparison
|
||||
- Supports `nft.dim_nft_contract_metadata` with collection context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for NFT metrics
|
||||
- Provides foundation for all NFT marketplace analytics and reporting
|
||||
- Powers cross-collection analysis and ecosystem mapping
|
||||
|
||||
## Commonly-used Fields
|
||||
- `price` and `price_usd`: Essential for sales value analysis and market trends
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `seller_address` and `buyer_address`: Critical for user behavior analysis and flow tracking
|
||||
- `platform_name`: Important for marketplace comparison and platform analysis
|
||||
- `token_id` and `nft_address`: Essential for NFT identification and collection analysis
|
||||
- `platform_fee` and `royalties`: Important for marketplace economics analysis
|
||||
- `affiliate_id`: Useful for affiliate program analysis and user acquisition tracking
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/nft__fact_nft_mints.md
Normal file
32
models/descriptions/nft__fact_nft_mints.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs nft__fact_nft_mints %}
|
||||
|
||||
## Description
|
||||
This table contains all NFT minting transactions on the NEAR Protocol blockchain, capturing the creation of new NFTs across various collections and standards. The data includes minting details such as token IDs, minting methods, arguments, deposits, and associated metadata. This table provides the foundation for NFT analytics, collection growth tracking, and minting pattern analysis across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- NFT collection growth analysis and minting velocity tracking
|
||||
- NFT minting pattern analysis and user behavior monitoring
|
||||
- Collection launch analysis and initial distribution tracking
|
||||
- NFT minting cost analysis and gas optimization
|
||||
- Cross-collection minting comparison and performance benchmarking
|
||||
- NFT creator analysis and minting strategy evaluation
|
||||
- NFT ecosystem health monitoring and collection discovery
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides minting data for `nft.ez_nft_sales` with enhanced metadata
|
||||
- Supports `nft.fact_nft_transfers` with minting context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for NFT metrics
|
||||
- Powers cross-collection analysis and ecosystem mapping
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `token_id`: Critical for unique NFT identification and tracking
|
||||
- `owner_id`: Important for creator analysis and ownership tracking
|
||||
- `method_name`: Essential for minting method classification and analysis
|
||||
- `deposit` and `implied_price`: Important for minting cost analysis
|
||||
- `tx_receiver`: Critical for collection identification and contract analysis
|
||||
|
||||
{% enddocs %}
|
||||
32
models/descriptions/nft__fact_nft_transfers.md
Normal file
32
models/descriptions/nft__fact_nft_transfers.md
Normal file
@ -0,0 +1,32 @@
|
||||
{% docs nft__fact_nft_transfers %}
|
||||
|
||||
## Description
|
||||
This table contains all NFT transfer transactions on the NEAR Protocol blockchain, capturing the movement of NFTs between accounts and contracts. The data includes transfer details such as sender and receiver addresses, token IDs, contract addresses, and associated metadata. This table provides the foundation for NFT ownership tracking, transfer pattern analysis, and marketplace activity monitoring across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- NFT ownership tracking and transfer history analysis
|
||||
- NFT marketplace activity monitoring and volume analysis
|
||||
- NFT transfer pattern analysis and user behavior tracking
|
||||
- Cross-collection transfer comparison and performance analysis
|
||||
- NFT liquidity analysis and trading pattern identification
|
||||
- NFT holder analysis and distribution tracking
|
||||
- NFT ecosystem health monitoring and activity assessment
|
||||
|
||||
## Important Relationships
|
||||
- Links to `core.fact_transactions` through tx_hash for transaction context
|
||||
- Connects to `core.fact_blocks` through block_id for temporal context
|
||||
- Provides transfer data for `nft.ez_nft_sales` with enhanced metadata
|
||||
- Supports `nft.fact_nft_mints` with transfer context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for NFT metrics
|
||||
- Powers cross-collection analysis and ecosystem mapping
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`: Essential for linking to transaction details and verification
|
||||
- `block_timestamp`: Primary field for time-series analysis and trend detection
|
||||
- `token_id`: Critical for unique NFT identification and tracking
|
||||
- `from_address` and `to_address`: Important for ownership analysis and flow tracking
|
||||
- `contract_address`: Essential for collection identification and contract analysis
|
||||
- `action_id`: Important for action-level analysis and receipt context
|
||||
- `block_id`: Useful for temporal ordering and block-level analysis
|
||||
|
||||
{% enddocs %}
|
||||
30
models/descriptions/price__dim_asset_metadata.md
Normal file
30
models/descriptions/price__dim_asset_metadata.md
Normal file
@ -0,0 +1,30 @@
|
||||
{% docs price__dim_asset_metadata %}
|
||||
|
||||
## Description
|
||||
This table contains comprehensive metadata for all assets tracked for pricing on the NEAR Protocol blockchain, including token addresses, symbols, names, and blockchain platform information. The data covers both native NEAR tokens and cross-chain bridged assets, providing essential context for price identification, asset categorization, and multi-chain price correlation. This dimension table supports all price-related analytics by providing standardized asset information and enabling proper price data organization and analysis.
|
||||
|
||||
## Key Use Cases
|
||||
- Asset identification and price data correlation
|
||||
- Cross-chain asset mapping and price comparison
|
||||
- Multi-provider price data integration and validation
|
||||
- Asset categorization and platform-specific analysis
|
||||
- Price data quality assessment and metadata validation
|
||||
- Cross-asset price correlation and market analysis
|
||||
- Asset discovery and price coverage analysis
|
||||
|
||||
## Important Relationships
|
||||
- Enriches `price.fact_prices_ohlc_hourly` with asset metadata and identification
|
||||
- Supports `price.ez_prices_hourly` with enhanced asset context
|
||||
- Provides metadata for `price.ez_asset_metadata` with comprehensive asset information
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for price metrics
|
||||
- Supports cross-asset analysis and multi-chain price correlation
|
||||
|
||||
## Commonly-used Fields
|
||||
- `token_address`: Essential for joining with price data and asset identification
|
||||
- `symbol` and `name`: Critical for human-readable asset identification
|
||||
- `platform` and `platform_id`: Important for blockchain-specific analysis
|
||||
- `provider`: Useful for price data source identification and reliability assessment
|
||||
- `asset_id`: Important for unique asset identification across systems
|
||||
- `inserted_timestamp`: Useful for asset discovery timeline analysis
|
||||
|
||||
{% enddocs %}
|
||||
33
models/descriptions/price__ez_asset_metadata.md
Normal file
33
models/descriptions/price__ez_asset_metadata.md
Normal file
@ -0,0 +1,33 @@
|
||||
{% docs price__ez_asset_metadata %}
|
||||
|
||||
## Description
|
||||
This table provides a comprehensive view of asset metadata for all tracked assets on the NEAR Protocol blockchain, combining both native NEAR token metadata and cross-chain bridged asset metadata. The table includes token addresses, symbols, names, decimal precision, and blockchain platform information, making it the primary table for asset identification and categorization. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for asset analysis and metadata enrichment across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Asset identification and metadata enrichment for analytics
|
||||
- Cross-chain asset mapping and correlation analysis
|
||||
- Token categorization and platform-specific analysis
|
||||
- Asset discovery and coverage analysis
|
||||
- Multi-provider metadata validation and quality assessment
|
||||
- Cross-asset comparison and ecosystem mapping
|
||||
- Asset standardization and metadata quality improvement
|
||||
|
||||
## Important Relationships
|
||||
- Combines data from `price.dim_asset_metadata` with enhanced categorization
|
||||
- Provides metadata for `price.ez_prices_hourly` with comprehensive asset context
|
||||
- Supports `core.ez_token_transfers` with enhanced token identification
|
||||
- Enables `defi.ez_dex_swaps` with token pair analysis
|
||||
- Powers `defi.ez_bridge_activity` with cross-chain asset mapping
|
||||
- Supports `stats.ez_core_metrics_hourly` with asset-based metrics
|
||||
- Provides foundation for all asset-related analytics and reporting
|
||||
|
||||
## Commonly-used Fields
|
||||
- `token_address`: Essential for joining with transaction and price data
|
||||
- `symbol` and `name`: Critical for human-readable asset identification
|
||||
- `blockchain`: Important for cross-chain analysis and platform comparison
|
||||
- `is_native`: Essential for distinguishing native vs bridged assets
|
||||
- `decimals`: Important for accurate value calculations and decimal adjustment
|
||||
- `asset_id`: Useful for unique asset identification across systems
|
||||
- `is_deprecated`: Important for data quality assessment and asset lifecycle tracking
|
||||
|
||||
{% enddocs %}
|
||||
33
models/descriptions/price__ez_prices_hourly.md
Normal file
33
models/descriptions/price__ez_prices_hourly.md
Normal file
@ -0,0 +1,33 @@
|
||||
{% docs price__ez_prices_hourly %}
|
||||
|
||||
## Description
|
||||
This table provides a comprehensive view of hourly price data for all assets on the NEAR Protocol blockchain, combining both native NEAR token prices and cross-chain bridged asset prices. The table includes token metadata, decimal precision, and price information, making it the primary table for price analytics and value calculations. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for price analysis, market monitoring, and economic calculations across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Asset price monitoring and market trend analysis
|
||||
- Token value calculations and USD conversion
|
||||
- Cross-asset price comparison and correlation analysis
|
||||
- Market volatility assessment and risk analysis
|
||||
- Portfolio value tracking and performance calculation
|
||||
- DeFi protocol value analysis and economic impact assessment
|
||||
- Cross-chain asset price correlation and arbitrage analysis
|
||||
|
||||
## Important Relationships
|
||||
- Combines data from `price.fact_prices_ohlc_hourly` with enhanced metadata
|
||||
- Provides price data for all token-related models requiring USD values
|
||||
- Supports `core.ez_token_transfers` with accurate price information
|
||||
- Enables `defi.ez_dex_swaps` with swap value calculations
|
||||
- Powers `defi.ez_bridge_activity` with cross-chain value analysis
|
||||
- Supports `stats.ez_core_metrics_hourly` with price-based metrics
|
||||
- Provides foundation for all economic analysis and value calculations
|
||||
|
||||
## Commonly-used Fields
|
||||
- `hour`: Essential for time-series analysis and trend detection
|
||||
- `price`: Critical for value calculations and economic analysis
|
||||
- `token_address` and `symbol`: Important for asset identification and filtering
|
||||
- `blockchain`: Useful for cross-chain price analysis and comparison
|
||||
- `is_native`: Important for distinguishing native vs bridged assets
|
||||
- `decimals`: Essential for accurate value calculations and decimal adjustment
|
||||
- `is_deprecated` and `is_imputed`: Useful for data quality assessment
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/price__fact_prices_ohlc_hourly.md
Normal file
31
models/descriptions/price__fact_prices_ohlc_hourly.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs price__fact_prices_ohlc_hourly %}
|
||||
|
||||
## Description
|
||||
This table contains hourly OHLC (Open, High, Low, Close) price data for all tracked assets on the NEAR Protocol blockchain, capturing price movements and volatility patterns across different time periods. The data includes comprehensive price information from multiple providers, enabling detailed market analysis, volatility assessment, and price trend identification. This table provides the foundation for price analytics, market analysis, and economic calculations across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Asset price trend analysis and market movement tracking
|
||||
- Volatility analysis and risk assessment
|
||||
- Price correlation analysis across different assets
|
||||
- Market timing analysis and trading pattern identification
|
||||
- Cross-provider price validation and data quality assessment
|
||||
- Economic impact analysis of price movements
|
||||
- Portfolio performance tracking and value calculations
|
||||
|
||||
## Important Relationships
|
||||
- Links to `price.dim_asset_metadata` through asset_id for asset identification
|
||||
- Provides price data for `price.ez_prices_hourly` with enhanced metadata
|
||||
- Supports `price.ez_asset_metadata` with comprehensive price context
|
||||
- Enables analysis in `stats.ez_core_metrics_hourly` for price metrics
|
||||
- Powers value calculations across all token-related models
|
||||
- Supports cross-asset analysis and market correlation studies
|
||||
|
||||
## Commonly-used Fields
|
||||
- `hour`: Essential for time-series analysis and trend detection
|
||||
- `open`, `high`, `low`, `close`: Critical for price movement analysis and volatility calculation
|
||||
- `asset_id`: Important for asset-specific price analysis and correlation
|
||||
- `provider`: Useful for price data source identification and reliability assessment
|
||||
- `inserted_timestamp`: Important for data freshness and update tracking
|
||||
- `fact_prices_ohlc_hourly_id`: Essential for unique price record identification
|
||||
|
||||
{% enddocs %}
|
||||
31
models/descriptions/stats__ez_core_metrics_hourly.md
Normal file
31
models/descriptions/stats__ez_core_metrics_hourly.md
Normal file
@ -0,0 +1,31 @@
|
||||
{% docs stats__ez_core_metrics_hourly %}
|
||||
|
||||
## Description
|
||||
This table provides comprehensive hourly metrics for the NEAR Protocol blockchain, combining block production, transaction activity, and economic data with USD pricing information. The table includes block counts, transaction volumes, success rates, unique user counts, and fee calculations in both native NEAR and USD terms. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for network health monitoring, performance analysis, and economic assessment across the NEAR ecosystem.
|
||||
|
||||
## Key Use Cases
|
||||
- Network health monitoring and performance analysis
|
||||
- Transaction volume analysis and success rate tracking
|
||||
- Economic analysis with USD value calculations
|
||||
- User activity analysis and adoption tracking
|
||||
- Network fee analysis and economic impact assessment
|
||||
- Cross-hour performance comparison and trend identification
|
||||
- Network capacity analysis and scaling assessment
|
||||
|
||||
## Important Relationships
|
||||
- Combines data from `stats.core_metrics_block_hourly` and `stats.core_metrics_hourly` for comprehensive metrics
|
||||
- Enhances metrics with pricing data from `price.ez_prices_hourly` for USD calculations
|
||||
- Provides aggregated metrics for network health monitoring and reporting
|
||||
- Supports all other gold models with network-level context and metrics
|
||||
- Powers dashboard analytics and network performance reporting
|
||||
- Enables cross-protocol comparison and benchmarking
|
||||
|
||||
## Commonly-used Fields
|
||||
- `block_timestamp_hour`: Essential for time-series analysis and trend detection
|
||||
- `transaction_count` and `transaction_count_success`: Critical for network activity analysis
|
||||
- `total_fees_native` and `total_fees_usd`: Important for economic analysis and fee impact assessment
|
||||
- `unique_from_count` and `unique_to_count`: Essential for user activity analysis and adoption tracking
|
||||
- `block_count`: Important for network throughput and capacity analysis
|
||||
- `block_number_min` and `block_number_max`: Useful for block range analysis and completeness verification
|
||||
|
||||
{% enddocs %}
|
||||
Loading…
Reference in New Issue
Block a user