mirror of
https://github.com/FlipsideCrypto/aptos-models.git
synced 2026-02-06 13:56:45 +00:00
update defi and nft desc
This commit is contained in:
parent
c81c9d66cf
commit
9bcf890d79
14
models/descriptions/bridge/bridge_address.md
Normal file
14
models/descriptions/bridge/bridge_address.md
Normal file
@ -0,0 +1,14 @@
|
||||
{% docs bridge_address %}
|
||||
|
||||
The address of the contract responsible for handling the bridge deposit or transfer. This contract mediates the transfer and ensures that assets are sent and received appropriately.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying bridge contracts and their deployment locations.
|
||||
- Enables contract-level analytics, security analysis, and bridge protocol tracking.
|
||||
- Supports bridge ecosystem monitoring and contract verification.
|
||||
|
||||
{% enddocs %}
|
||||
16
models/descriptions/bridge/bridge_platform.md
Normal file
16
models/descriptions/bridge/bridge_platform.md
Normal file
@ -0,0 +1,16 @@
|
||||
{% docs bridge_platform %}
|
||||
|
||||
The platform or protocol from which the bridge transaction or event originates.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- LayerZero
|
||||
- Wormhole
|
||||
- Stargate
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying and analyzing bridge protocol usage.
|
||||
- Enables platform-level analytics, volume tracking, and protocol comparisons.
|
||||
- Supports bridge ecosystem analysis and user behavior insights.
|
||||
|
||||
{% enddocs %}
|
||||
14
models/descriptions/bridge/bridge_receiver.md
Normal file
14
models/descriptions/bridge/bridge_receiver.md
Normal file
@ -0,0 +1,14 @@
|
||||
{% docs bridge_receiver %}
|
||||
|
||||
The designated address set to receive the bridged tokens on the target chain after the completion of the bridge transaction. For non-evm chains, the hex address is decoded/encoded to match the data format of the destination chain, where possible.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking bridge recipients and cross-chain asset flows.
|
||||
- Enables user-level analytics, bridge destination patterns, and receiver behavior analysis.
|
||||
- Supports linking to address labels and user profiles across chains.
|
||||
|
||||
{% enddocs %}
|
||||
14
models/descriptions/bridge/bridge_sender.md
Normal file
14
models/descriptions/bridge/bridge_sender.md
Normal file
@ -0,0 +1,14 @@
|
||||
{% docs bridge_sender %}
|
||||
|
||||
The address that initiated the bridge deposit or transfer. This address is the sender of the tokens/assets being bridged to the destination chain.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking bridge users and their cross-chain activity.
|
||||
- Enables user-level analytics, bridge usage patterns, and sender behavior analysis.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
14
models/descriptions/bridge/bridge_token_address.md
Normal file
14
models/descriptions/bridge/bridge_token_address.md
Normal file
@ -0,0 +1,14 @@
|
||||
{% docs bridge_token_address %}
|
||||
|
||||
The address associated with the token that is being bridged. It provides a unique identifier for the token within its origin blockchain.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying bridged tokens and their cross-chain flows.
|
||||
- Enables token-level analytics, volume tracking, and cross-chain token analysis.
|
||||
- Supports bridge ecosystem monitoring and token flow visualization.
|
||||
|
||||
{% enddocs %}
|
||||
17
models/descriptions/bridge/destination_chain.md
Normal file
17
models/descriptions/bridge/destination_chain.md
Normal file
@ -0,0 +1,17 @@
|
||||
{% docs destination_chain %}
|
||||
|
||||
The name of the blockchain network to which the assets are being bridged.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- Ethereum
|
||||
- Polygon
|
||||
- Arbitrum
|
||||
- Optimism
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing cross-chain asset flows and destination preferences.
|
||||
- Enables chain-level analytics, volume tracking, and cross-chain comparisons.
|
||||
- Supports bridge ecosystem analysis and user behavior insights.
|
||||
|
||||
{% enddocs %}
|
||||
16
models/descriptions/bridge/destination_chain_id.md
Normal file
16
models/descriptions/bridge/destination_chain_id.md
Normal file
@ -0,0 +1,16 @@
|
||||
{% docs destination_chain_id %}
|
||||
|
||||
The numeric identifier associated with the destination blockchain network. This is specific to the chain and helps in uniquely identifying it.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 1 (Ethereum Mainnet)
|
||||
- 137 (Polygon)
|
||||
- 42161 (Arbitrum One)
|
||||
|
||||
**Business Context:**
|
||||
- Used for programmatic chain identification and filtering.
|
||||
- Enables automated chain-level analytics and cross-chain data processing.
|
||||
- Supports bridge protocol integration and chain-specific logic.
|
||||
|
||||
{% enddocs %}
|
||||
17
models/descriptions/bridge/source_chain.md
Normal file
17
models/descriptions/bridge/source_chain.md
Normal file
@ -0,0 +1,17 @@
|
||||
{% docs source_chain %}
|
||||
|
||||
The name of the blockchain network from which the assets are being bridged.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- Ethereum
|
||||
- Polygon
|
||||
- Arbitrum
|
||||
- Optimism
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing cross-chain asset flows and source chain preferences.
|
||||
- Enables chain-level analytics, volume tracking, and cross-chain comparisons.
|
||||
- Supports bridge ecosystem analysis and user behavior insights.
|
||||
|
||||
{% enddocs %}
|
||||
16
models/descriptions/bridge/source_chain_id.md
Normal file
16
models/descriptions/bridge/source_chain_id.md
Normal file
@ -0,0 +1,16 @@
|
||||
{% docs source_chain_id %}
|
||||
|
||||
The numeric identifier associated with the source blockchain network. This is specific to the chain and helps in uniquely identifying it.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 1 (Ethereum Mainnet)
|
||||
- 137 (Polygon)
|
||||
- 42161 (Arbitrum One)
|
||||
|
||||
**Business Context:**
|
||||
- Used for programmatic chain identification and filtering.
|
||||
- Enables automated chain-level analytics and cross-chain data processing.
|
||||
- Supports bridge protocol integration and chain-specific logic.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs amount_in %}
|
||||
|
||||
The decimal adjusted amount of a token of the inbound token for the swap. If there token's decimal is not available, this value will be NULL.
|
||||
The decimal-adjusted amount of the inbound token for the swap.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1.5 (for 1.5 tokens)
|
||||
- 100.0 (for 100 tokens)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis, reporting, and user-friendly analytics.
|
||||
- Enables value-based calculations and cross-token comparisons.
|
||||
- Supports dashboards and business intelligence for DEX platforms.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs amount_in_unadj %}
|
||||
|
||||
The non decimal adjusted amount of a token of the inbound token for the swap.
|
||||
The non-decimal adjusted amount of the inbound token for the swap.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 1500000 (for 1.5 tokens with 6 decimals)
|
||||
- 1000000000000000000 (for 1 token with 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Essential for reconstructing the exact on-chain value of swap inputs.
|
||||
- Used for technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Enables accurate calculation of swap volumes and liquidity flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs amount_in_usd %}
|
||||
|
||||
The US Dollar equivalent of a token of the inbound token for the swap. If the token's decimal is not available, this value will be NULL.
|
||||
The USD value of the inbound token amount, converted at the time of the swap.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1500.00 (for $1,500 worth of tokens)
|
||||
- 0.50 (for $0.50 worth of tokens)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of swap volumes in USD terms.
|
||||
- Enables value-based analytics and aggregation of swap volumes in USD.
|
||||
- Supports dashboards and business intelligence for DEX platforms.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,6 +1,15 @@
|
||||
{% docs amount_out %}
|
||||
|
||||
The decimal adjusted amount of a token of the outbound token for the swap. If the token's decimal is not available, this value will be NULL.
|
||||
The decimal-adjusted amount of the outbound token for the swap.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1.5 (for 1.5 tokens)
|
||||
- 100.0 (for 100 tokens)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis, reporting, and user-friendly analytics.
|
||||
- Enables value-based calculations and cross-token comparisons.
|
||||
- Supports dashboards and business intelligence for DEX platforms.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs amount_out_unadj %}
|
||||
|
||||
The non decimal adjusted amount of a token of the outbound token for the swap.
|
||||
The non-decimal adjusted amount of the outbound token for the swap.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 1500000 (for 1.5 tokens with 6 decimals)
|
||||
- 1000000000000000000 (for 1 token with 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Essential for reconstructing the exact on-chain value of swap outputs.
|
||||
- Used for technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Enables accurate calculation of swap volumes and liquidity flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,6 +1,15 @@
|
||||
{% docs amount_out_usd %}
|
||||
|
||||
The US Dollar equivalent of a token of the outbound token for the swap. If the token's decimal is not available, this value will be NULL.
|
||||
The USD value of the outbound token amount, converted at the time of the swap.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1500.00 (for $1,500 worth of tokens)
|
||||
- 0.50 (for $0.50 worth of tokens)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of swap volumes in USD terms.
|
||||
- Enables value-based analytics and aggregation of swap volumes in USD.
|
||||
- Supports dashboards and business intelligence for DEX platforms.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs swap_platform %}
|
||||
|
||||
The name of the platform where the swap occurred.
|
||||
The name of the platform where the swap occurred.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- PancakeSwap
|
||||
- Uniswap
|
||||
- SushiSwap
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying and analyzing DEX platform usage.
|
||||
- Enables platform-level analytics, volume tracking, and protocol comparisons.
|
||||
- Supports DEX ecosystem analysis and user behavior insights.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs swapper %}
|
||||
|
||||
Address that initiated the swap
|
||||
Address that initiated the swap.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking swap users and their trading activity.
|
||||
- Enables user-level analytics, trading patterns, and swapper behavior analysis.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs symbol_in %}
|
||||
|
||||
The symbol of the inbound token, if available.
|
||||
The token symbol for the inbound token in the swap.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- USDC
|
||||
- WETH
|
||||
- APT
|
||||
|
||||
**Business Context:**
|
||||
- Used for user-friendly analytics, reporting, and dashboards.
|
||||
- Enables token-level filtering, grouping, and visualization.
|
||||
- Supports cross-token comparisons and swap analysis.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs symbol_out %}
|
||||
|
||||
The symbol of the outbound token, if available.
|
||||
The token symbol for the outbound token in the swap.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- USDC
|
||||
- WETH
|
||||
- APT
|
||||
|
||||
**Business Context:**
|
||||
- Used for user-friendly analytics, reporting, and dashboards.
|
||||
- Enables token-level filtering, grouping, and visualization.
|
||||
- Supports cross-token comparisons and swap analysis.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs token_in %}
|
||||
|
||||
The full address of the inbound token. This string contains the account, module, and resource.
|
||||
The address of the inbound token in the swap.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying input tokens and their swap activity.
|
||||
- Enables token-level analytics, volume tracking, and cross-token analysis.
|
||||
- Supports DEX ecosystem monitoring and token flow visualization.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs token_out %}
|
||||
|
||||
The full address of the outbound token. This string contains the account, module, and resource.
|
||||
The address of the outbound token in the swap.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying output tokens and their swap activity.
|
||||
- Enables token-level analytics, volume tracking, and cross-token analysis.
|
||||
- Supports DEX ecosystem monitoring and token flow visualization.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,55 +0,0 @@
|
||||
|
||||
{% docs bridge_platform %}
|
||||
|
||||
The platform or protocol from which the bridge transaction or event originates.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs bridge_sender %}
|
||||
|
||||
The address that initiated the bridge deposit or transfer. This address is the sender of the tokens/assets being bridged to the destination chain.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs bridge_receiver %}
|
||||
|
||||
The designated address set to receive the bridged tokens on the target chain after the completion of the bridge transaction. For non-evm chains, the hex address is decoded/encoded to match the data format of the destination chain, where possible.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs destination_chain %}
|
||||
|
||||
The name of the blockchain network to which the assets are being bridged.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs destination_chain_id %}
|
||||
|
||||
The numeric identifier associated with the destination blockchain network. This is specific to the chain and helps in uniquely identifying it.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs bridge_address %}
|
||||
|
||||
The address of the contract responsible for handling the bridge deposit or transfer. This contract mediates the transfer and ensures that assets are sent and received appropriately.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
|
||||
{% docs bridge_token_address %}
|
||||
|
||||
The address associated with the token that is being bridged. It provides a unique identifier for the token within its origin blockchain.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs source_chain_id %}
|
||||
|
||||
The numeric identifier associated with the source blockchain network. This is specific to the chain and helps in uniquely identifying it.
|
||||
|
||||
{% enddocs %}
|
||||
|
||||
{% docs source_chain %}
|
||||
|
||||
The name of the blockchain network from which the assets are being bridged.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs nft_aggregator_name%}
|
||||
{% docs nft_aggregator_name %}
|
||||
|
||||
The name of the aggregator platform where the sale took place. If the sale did not take place via an aggregator platform, then the value will be null.
|
||||
The name of the NFT aggregator or routing service involved in the event, if applicable.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- Gem
|
||||
- Genie
|
||||
- None
|
||||
|
||||
**Business Context:**
|
||||
- Used for grouping and filtering NFT events by aggregator.
|
||||
- Enables aggregator-level analytics, trend analysis, and reporting.
|
||||
- Supports dashboards and user-facing NFT discovery tools.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_amount%}
|
||||
{% docs nft_amount %}
|
||||
|
||||
The total amount, specified by the mint token address, used as payment to mint the specified number of NFTs corresponding to this token id.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1.0 (for 1 unit of the transaction currency)
|
||||
- 0.25 (for 0.25 units of the transaction currency)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of NFT minting costs.
|
||||
- Enables value-based analytics and aggregation of mint volumes in native currency terms.
|
||||
- Supports dashboards and business intelligence for NFT projects.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_amount_usd%}
|
||||
{% docs nft_amount_usd %}
|
||||
|
||||
The USD value of 'amount'.
|
||||
The USD value of 'amount', representing the payment to mint the specified number of NFTs, converted at the time of the transaction.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 100.00 (for $100 payment)
|
||||
- 0.50 (for $0.50 payment)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of NFT minting costs in USD terms.
|
||||
- Enables value-based analytics and aggregation of mint volumes in USD.
|
||||
- Supports dashboards and business intelligence for NFT projects.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs nft_buyer_address %}
|
||||
|
||||
The address of the buyer of the NFT in the transaction.
|
||||
The address of the buyer of the NFT in the transaction.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking NFT buyers and purchase activity.
|
||||
- Enables user-level analytics, purchase reporting, and marketplace analysis.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_creator_fee %}
|
||||
|
||||
The decimal adjusted amount of fees paid to the NFT collection as royalty payments for this NFT event in the transaction's currency.
|
||||
The creator royalty fee paid as part of the NFT sale or mint, in decimal-adjusted units of the transaction currency.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for 1 cent fee)
|
||||
- 2.5 (for 2.5 units of the transaction currency)
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing creator revenue and royalty structures.
|
||||
- Enables comparison of creator fees across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_creator_fee_raw %}
|
||||
|
||||
The non-decimal adjusted amount of fees paid to the NFT collection as royalty payments for this NFT event in the transaction's currency.
|
||||
The non-decimal adjusted amount of creator royalty fees paid for this NFT event in the transaction's currency.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 100000000 (for 1 unit with 8 decimals)
|
||||
- 500000000000000000 (for 0.5 unit at 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Used for reconstructing the exact on-chain value of creator fees.
|
||||
- Enables technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Supports accurate calculation of creator fee volumes and value flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_creator_fee_usd %}
|
||||
|
||||
The amount of fees paid to the NFT collection as royalty payments for this NFT event in US dollars.
|
||||
The creator royalty fee paid as part of the NFT sale or mint, converted to USD at the time of the transaction.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for $0.01 fee)
|
||||
- 2.5 (for $2.50 fee)
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing creator revenue and royalty structures in USD terms.
|
||||
- Enables comparison of creator fees across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_currency_address %}
|
||||
|
||||
The token contract address for this NFT event. This will be `ETH` for native ETH transactions.
|
||||
The contract address of the currency used for the NFT event (mint or sale).
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1::aptos_coin::AptosCoin
|
||||
- 0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying the payment currency for NFT events.
|
||||
- Enables currency-level analytics, filtering, and reporting.
|
||||
- Supports joining with token metadata and price information.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs nft_currency_symbol %}
|
||||
|
||||
The token symbol for this NFT event.
|
||||
The token symbol for this NFT event.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- APT
|
||||
- USDC
|
||||
- WETH
|
||||
|
||||
**Business Context:**
|
||||
- Used for user-friendly analytics, reporting, and dashboards.
|
||||
- Enables currency-level filtering, grouping, and visualization.
|
||||
- Supports cross-currency comparisons and project analysis.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs nft_from_address %}
|
||||
|
||||
The sending address of the NFT in the transaction.
|
||||
The account address that sent or originated the NFT in a mint or transfer event.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking NFT creators, senders, and transferors.
|
||||
- Enables user-level analytics, provenance, and ownership history.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
@ -2,4 +2,14 @@
|
||||
|
||||
The number of NFTs minted in this event.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 1
|
||||
- 10
|
||||
|
||||
**Business Context:**
|
||||
- Used for quantifying NFT minting activity and project launches.
|
||||
- Enables project-level analytics, trend analysis, and reporting.
|
||||
- Supports dashboards and user-facing NFT discovery tools.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_platform_address %}
|
||||
|
||||
The address of the exchange used for the transaction.
|
||||
The contract address of the NFT marketplace or platform where the event occurred.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1::marketplace::Marketplace
|
||||
- 0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
|
||||
|
||||
**Business Context:**
|
||||
- Used for identifying NFT marketplaces and platforms.
|
||||
- Enables platform-level analytics, filtering, and reporting.
|
||||
- Supports joining with metadata and project information.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs nft_platform_exchange_version %}
|
||||
|
||||
The version of the exchange contract used for the transaction.
|
||||
The version or identifier of the NFT marketplace or platform where the event occurred.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- v1
|
||||
- v2
|
||||
- 2023-01-01
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking platform upgrades, changes, and event context.
|
||||
- Enables version-level analytics, trend analysis, and reporting.
|
||||
- Supports dashboards and user-facing NFT discovery tools.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_platform_fee %}
|
||||
|
||||
The decimal adjusted amount of fees paid to the platform for this NFT event in the transaction's currency.
|
||||
The platform fee paid as part of the NFT sale or mint, in decimal-adjusted units of the transaction currency.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for 1 cent fee)
|
||||
- 2.5 (for 2.5 units of the transaction currency)
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing platform revenue and fee structures.
|
||||
- Enables comparison of platform fees across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_platform_fee_raw %}
|
||||
|
||||
The non-decimal adjusted amount of fees paid to the platform for this NFT event in the transaction's currency.
|
||||
The non-decimal adjusted amount of platform fees paid for this NFT event in the transaction's currency.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 100000000 (for 1 unit with 8 decimals)
|
||||
- 500000000000000000 (for 0.5 unit at 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Used for reconstructing the exact on-chain value of platform fees.
|
||||
- Enables technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Supports accurate calculation of platform fee volumes and value flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_platform_fee_usd %}
|
||||
|
||||
The amount of fees paid to the platform for this NFT event in US dollars.
|
||||
The platform fee paid as part of the NFT sale or mint, converted to USD at the time of the transaction.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for $0.01 fee)
|
||||
- 2.5 (for $2.50 fee)
|
||||
|
||||
**Business Context:**
|
||||
- Used for analyzing platform revenue and fee structures in USD terms.
|
||||
- Enables comparison of platform fees across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,16 @@
|
||||
{% docs nft_platform_name %}
|
||||
|
||||
The name of the exchange used for the trade.
|
||||
The name of the NFT marketplace or platform where the event occurred.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- bluemove
|
||||
- topaz
|
||||
- souffl3
|
||||
|
||||
**Business Context:**
|
||||
- Used for grouping and filtering NFT events by platform.
|
||||
- Enables platform-level analytics, trend analysis, and reporting.
|
||||
- Supports dashboards and user-facing NFT discovery tools.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_price %}
|
||||
|
||||
The amount of the NFT event in the currency in which the transaction occurred.
|
||||
The price of the NFT event (mint or sale), in decimal-adjusted units of the transaction currency.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 1.0 (for 1 unit of the transaction currency)
|
||||
- 0.25 (for 0.25 units of the transaction currency)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis, reporting, and cross-project comparisons.
|
||||
- Enables value-based analytics and aggregation of NFT volumes in native currency terms.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -2,4 +2,14 @@
|
||||
|
||||
The non-decimal adjusted amount of the NFT event in the currency in which the transaction occurred.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 100000000 (for 1 NFT at 1 unit with 8 decimals)
|
||||
- 500000000000000000 (for 0.5 NFT at 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Used for reconstructing the exact on-chain value of NFT sales or mints.
|
||||
- Enables technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Supports accurate calculation of NFT volumes and value flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_price_usd %}
|
||||
|
||||
The amount of the NFT event in US dollars. This will be 0 for tokens without a decimal adjustment or hourly price.
|
||||
The price of the NFT event (mint or sale), converted to USD at the time of the transaction.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 100.00 (for $100 sale)
|
||||
- 0.50 (for $0.50 mint)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis, reporting, and cross-project comparisons.
|
||||
- Enables value-based analytics and aggregation of NFT volumes in USD terms.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs nft_seller_address %}
|
||||
|
||||
The address of the seller of the NFT in the transaction.
|
||||
The address of the seller of the NFT in the transaction.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking NFT sellers and sale activity.
|
||||
- Enables user-level analytics, sales reporting, and marketplace analysis.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,14 @@
|
||||
{% docs nft_to_address %}
|
||||
|
||||
The receiving address of the NFT in the transaction.
|
||||
The account address that received the NFT in a mint or transfer event.
|
||||
|
||||
**Data type:** String
|
||||
**Example:**
|
||||
- 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
|
||||
|
||||
**Business Context:**
|
||||
- Used for tracking NFT recipients, buyers, and new owners.
|
||||
- Enables user-level analytics, ownership history, and transfer analysis.
|
||||
- Supports linking to address labels and user profiles.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_total_fees %}
|
||||
|
||||
The total amount of fees paid relating to the NFT purchase in the transaction currency. This includes royalty payments to creators and platform fees. Please note, this does not include the gas fee.
|
||||
The total amount of fees paid relating to the NFT purchase, in decimal-adjusted units. This includes royalty payments to creators and platform fees, but does not include the gas fee.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for 1 cent fee)
|
||||
- 2.5 (for 2.5 units of the transaction currency)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of NFT fee structures.
|
||||
- Enables comparison of fee burdens across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_total_fees_raw %}
|
||||
|
||||
The non-decimal adjusted total amount of fees paid relating to the NFT purchase in the transaction currency. This includes royalty payments to creators and platform fees. Please note, this does not include the gas fee.
|
||||
The non-decimal adjusted total amount of fees paid relating to the NFT purchase in the transaction currency. This includes royalty payments to creators and platform fees. Does not include gas fee.
|
||||
|
||||
**Data type:** Integer
|
||||
**Example:**
|
||||
- 100000000 (for 1 unit with 8 decimals)
|
||||
- 500000000000000000 (for 0.5 unit at 18 decimals)
|
||||
|
||||
**Business Context:**
|
||||
- Used for reconstructing the exact on-chain value of NFT fees.
|
||||
- Enables technical audits, protocol analytics, and downstream decimal adjustment.
|
||||
- Supports accurate calculation of NFT fee volumes and value flows.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,15 @@
|
||||
{% docs nft_total_fees_usd %}
|
||||
|
||||
The total amount of fees paid relating to the NFT purchase in US dollars. This includes royalty payments to creators and platform fees. Please note, this does not include the gas fee.
|
||||
The total amount of fees paid relating to the NFT purchase, converted to USD. This includes royalty payments to creators and platform fees, but does not include the gas fee.
|
||||
|
||||
**Data type:** Decimal
|
||||
**Example:**
|
||||
- 0.01 (for 1 cent fee)
|
||||
- 2.5 (for $2.50 fee)
|
||||
|
||||
**Business Context:**
|
||||
- Used for financial analysis and reporting of NFT fee structures in USD terms.
|
||||
- Enables comparison of fee burdens across projects, platforms, and time.
|
||||
- Supports dashboards and business intelligence for NFT marketplaces.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,28 @@
|
||||
{% docs defi__ez_bridge_activity %}
|
||||
|
||||
A convenience table that aggregates bridge activity for bridge deposits and transfers sent from the following protocols: CELER, LAYER ZERO, MOVER, and WORMHOLE. Note, this table only includes records for the protocols listed above with live, onchain bridge activity and may not represent the complete bridging picture.
|
||||
## Description
|
||||
This table provides enriched bridge activity data for Aptos, combining raw on-chain bridge events from multiple protocols with token metadata (symbols, decimals) and price information. It includes decimal-adjusted amounts, token symbols, and USD values, making it suitable for analytics and reporting.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing cross-chain bridge flows and protocol usage in USD
|
||||
- Building dashboards for bridge volume, user activity, and token flows
|
||||
- Comparing bridge activity across protocols and tokens
|
||||
- Supporting DeFi and cross-chain research, monitoring, and reporting
|
||||
- Powering downstream models for DeFi and bridge aggregations
|
||||
|
||||
## Important Relationships
|
||||
- Sources raw bridge data from `defi.fact_bridge_activity`
|
||||
- Joins token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Joins price data from `price.ez_prices_hourly` for USD values
|
||||
- Can be related to DEX swap data in `defi.ez_dex_swaps` for DeFi flow analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each bridge event
|
||||
- `platform`: Bridge protocol name
|
||||
- `symbol`: Token symbol being bridged
|
||||
- `amount`, `amount_usd`: Decimal-adjusted and USD value of bridge amount
|
||||
- `sender`, `receiver`: Addresses involved in the bridge event
|
||||
- `block_timestamp`: Time of the bridge event
|
||||
- `source_chain`, `destination_chain`: Names of source and destination chains
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,28 @@
|
||||
{% docs defi__ez_dex_swaps %}
|
||||
|
||||
A convenience table that contains DEX swap activity for the following protocols: animeswap, auxexchange, batswap, cellana, cetus, hippo, liquidswap, pancake, sushi, thala, and tsunami. This table contains combines the raw on chain data with decimal adjustments, token symbols, or prices.
|
||||
## Description
|
||||
This table provides enriched DEX swap data for Aptos, combining raw on-chain swap events from multiple protocols with token metadata (symbols, decimals) and price information. It includes decimal-adjusted amounts, token symbols, and USD values, making it suitable for analytics and reporting.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing DEX trading volumes and protocol market share in USD
|
||||
- Building dashboards for token flows, swap trends, and user activity
|
||||
- Comparing swap activity across protocols and tokens
|
||||
- Supporting DeFi research, trading strategies, and liquidity analysis
|
||||
- Powering downstream models for DeFi aggregations and reporting
|
||||
|
||||
## Important Relationships
|
||||
- Sources raw swap data from `defi.fact_dex_swaps`
|
||||
- Joins token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Joins price data from `price.ez_prices_hourly` for USD values
|
||||
- Can be related to bridge activity in `defi.ez_bridge_activity` for cross-protocol analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each swap event
|
||||
- `platform`: DEX protocol name
|
||||
- `symbol_in`, `symbol_out`: Token symbols for swap input/output
|
||||
- `amount_in`, `amount_out`: Decimal-adjusted swap amounts
|
||||
- `amount_in_usd`, `amount_out_usd`: USD value of swap amounts
|
||||
- `swapper`: Address of the user executing the swap
|
||||
- `block_timestamp`: Time of the swap event
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,28 @@
|
||||
{% docs defi__fact_bridge_activity %}
|
||||
|
||||
A fact table that aggregates bridge activity for bridge deposits and transfers sent from the following protocols: CELER, LAYER ZERO, MOVER, and WORMHOLE. Note, this table only includes records for the protocols listed above with live, onchain bridge activity and may not represent the complete bridging picture.
|
||||
## Description
|
||||
This table aggregates raw on-chain bridge activity for Aptos, including deposits and transfers from protocols such as Celer, LayerZero, Mover, and Wormhole. It captures protocol-level bridge events, including token addresses, amounts, sender/receiver addresses, and chain metadata, without enrichment or price attribution.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing cross-chain bridge flows and protocol usage
|
||||
- Auditing raw bridge events for compliance or research
|
||||
- Building dashboards for bridge volume, user activity, and token flows
|
||||
- Supporting downstream enrichment models for DeFi and cross-chain analytics
|
||||
- Monitoring bridge protocol adoption and trends
|
||||
|
||||
## Important Relationships
|
||||
- Serves as the source for enriched bridge data in `defi.ez_bridge_activity`
|
||||
- Token metadata is joined from `core.dim_tokens` for symbol/decimals
|
||||
- Can be linked to price data in `price.ez_prices_hourly` for USD values
|
||||
- Related to DEX swap data in `defi.fact_dex_swaps` for DeFi flow analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each bridge event
|
||||
- `platform`: Bridge protocol name
|
||||
- `token_address`: Token address being bridged
|
||||
- `amount_unadj`: Raw, non-decimal-adjusted bridge amount
|
||||
- `sender`, `receiver`: Addresses involved in the bridge event
|
||||
- `block_timestamp`: Time of the bridge event
|
||||
- `source_chain_name`, `destination_chain_name`: Names of source and destination chains
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,27 @@
|
||||
{% docs defi__fact_dex_swaps %}
|
||||
|
||||
A fact table that contains DEX swap activity for the following protocols: animeswap, auxexchange, batswap, cellana, cetus, hippo, liquidswap, pancake, sushi, thala, and tsunami. This fact table only contains the raw on chain data with no decimal adjustments, token symbols, or prices appiled.
|
||||
## Description
|
||||
This table records all raw on-chain DEX swap events on Aptos for protocols including animeswap, auxexchange, batswap, cellana, cetus, hippo, liquidswap, pancake, sushi, thala, and tsunami. It provides the unadjusted, protocol-level swap data, including token addresses, amounts, and swapper addresses, without any decimal adjustment, token symbol enrichment, or price attribution.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing DEX trading activity and protocol market share
|
||||
- Building custom swap aggregations and liquidity analytics
|
||||
- Auditing raw swap flows for compliance or research
|
||||
- Powering dashboards for DEX volume, user activity, and token flows
|
||||
- Supporting downstream enrichment models for DeFi analytics
|
||||
|
||||
## Important Relationships
|
||||
- Serves as the source for enriched swap data in `defi.ez_dex_swaps`
|
||||
- Token metadata is joined from `core.dim_tokens` for symbol/decimals
|
||||
- Can be linked to price data in `price.ez_prices_hourly` for USD values
|
||||
- Related to bridge activity in `defi.fact_bridge_activity` for cross-protocol analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each swap event
|
||||
- `platform`: DEX protocol name
|
||||
- `token_in`, `token_out`: Token addresses for swap input/output
|
||||
- `amount_in_unadj`, `amount_out_unadj`: Raw, non-decimal-adjusted swap amounts
|
||||
- `swapper`: Address of the user executing the swap
|
||||
- `block_timestamp`: Time of the swap event
|
||||
|
||||
{% enddocs %}
|
||||
27
models/descriptions/tables/nft__ez_nft_mints.md
Normal file
27
models/descriptions/tables/nft__ez_nft_mints.md
Normal file
@ -0,0 +1,27 @@
|
||||
{% docs nft__ez_nft_mints %}
|
||||
|
||||
## Description
|
||||
This table provides enriched NFT mint data for Aptos, combining raw on-chain mint events with token metadata (symbols, decimals) and price information. It includes decimal-adjusted prices, token symbols, and USD values, making it suitable for analytics and reporting.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing NFT minting activity and project launches in USD
|
||||
- Building dashboards for NFT mint volume, user activity, and project trends
|
||||
- Comparing mint activity across projects and tokens
|
||||
- Supporting NFT research, monitoring, and reporting
|
||||
- Powering downstream models for NFT aggregations and analytics
|
||||
|
||||
## Important Relationships
|
||||
- Sources raw mint data from `nft.fact_nft_mints`
|
||||
- Joins token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Joins price data from `price.ez_prices_hourly` for USD values
|
||||
- Can be related to NFT sales data in `nft.ez_nft_sales` for lifecycle analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each mint event
|
||||
- `nft_address`, `tokenid`: NFT contract and token identifiers
|
||||
- `nft_from_address`, `nft_to_address`: Addresses involved in the mint
|
||||
- `block_timestamp`: Time of the mint event
|
||||
- `project_name`: Name of the NFT project
|
||||
- `total_price`, `total_price_usd`: Decimal-adjusted and USD value of mint price
|
||||
|
||||
{% enddocs %}
|
||||
28
models/descriptions/tables/nft__ez_nft_sales.md
Normal file
28
models/descriptions/tables/nft__ez_nft_sales.md
Normal file
@ -0,0 +1,28 @@
|
||||
{% docs nft__ez_nft_sales %}
|
||||
|
||||
## Description
|
||||
This table provides enriched NFT sales data for Aptos, combining raw on-chain sale events with token metadata (symbols, decimals) and price information. It includes decimal-adjusted prices, token symbols, and USD values, making it suitable for analytics and reporting.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing NFT sales activity and marketplace trends in USD
|
||||
- Building dashboards for NFT sales volume, user activity, and project performance
|
||||
- Comparing sales activity across projects, platforms, and tokens
|
||||
- Supporting NFT research, monitoring, and reporting
|
||||
- Powering downstream models for NFT aggregations and analytics
|
||||
|
||||
## Important Relationships
|
||||
- Sources raw sales data from `nft.fact_nft_sales`
|
||||
- Joins token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Joins price data from `price.ez_prices_hourly` for USD values
|
||||
- Can be related to NFT mint data in `nft.ez_nft_mints` for lifecycle analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each sale event
|
||||
- `nft_address`, `tokenid`: NFT contract and token identifiers
|
||||
- `seller_address`, `buyer_address`: Addresses involved in the sale
|
||||
- `block_timestamp`: Time of the sale event
|
||||
- `project_name`, `platform_name`: Names of the NFT project and marketplace
|
||||
- `total_price`, `total_price_usd`: Decimal-adjusted and USD value of sale price
|
||||
- `platform_fee`, `creator_fee`, `total_fees`: Fee amounts in both raw and USD terms
|
||||
|
||||
{% enddocs %}
|
||||
27
models/descriptions/tables/nft__fact_nft_mints.md
Normal file
27
models/descriptions/tables/nft__fact_nft_mints.md
Normal file
@ -0,0 +1,27 @@
|
||||
{% docs nft__fact_nft_mints %}
|
||||
|
||||
## Description
|
||||
This table records all raw on-chain NFT mint events on Aptos, capturing the creation of new NFTs across supported marketplaces and protocols. It includes the addresses involved, NFT identifiers, project names, and raw price data, without enrichment or price attribution.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing NFT minting activity and project launches
|
||||
- Auditing raw NFT mint events for compliance or research
|
||||
- Building dashboards for NFT mint volume, user activity, and project trends
|
||||
- Supporting downstream enrichment models for NFT analytics
|
||||
- Monitoring NFT project adoption and minting trends
|
||||
|
||||
## Important Relationships
|
||||
- Serves as the source for enriched NFT mint data in `nft.ez_nft_mints`
|
||||
- Can be joined with token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Can be linked to price data in `price.ez_prices_hourly` for USD values
|
||||
- Related to NFT sales data in `nft.fact_nft_sales` for lifecycle analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each mint event
|
||||
- `nft_address`, `tokenid`: NFT contract and token identifiers
|
||||
- `nft_from_address`, `nft_to_address`: Addresses involved in the mint
|
||||
- `block_timestamp`: Time of the mint event
|
||||
- `project_name`: Name of the NFT project
|
||||
- `total_price_raw`: Raw, non-decimal-adjusted mint price
|
||||
|
||||
{% enddocs %}
|
||||
27
models/descriptions/tables/nft__fact_nft_sales.md
Normal file
27
models/descriptions/tables/nft__fact_nft_sales.md
Normal file
@ -0,0 +1,27 @@
|
||||
{% docs nft__fact_nft_sales %}
|
||||
|
||||
## Description
|
||||
This table records all raw on-chain NFT sale events on Aptos, capturing sales across supported marketplaces and protocols. It includes seller, buyer, NFT identifiers, project/platform names, and raw price/fee data, without enrichment or price attribution.
|
||||
|
||||
## Key Use Cases
|
||||
- Analyzing NFT sales activity and marketplace trends
|
||||
- Auditing raw NFT sale events for compliance or research
|
||||
- Building dashboards for NFT sales volume, user activity, and project performance
|
||||
- Supporting downstream enrichment models for NFT analytics
|
||||
- Monitoring NFT project adoption and sales trends
|
||||
|
||||
## Important Relationships
|
||||
- Serves as the source for enriched NFT sales data in `nft.ez_nft_sales`
|
||||
- Can be joined with token metadata from `core.dim_tokens` for symbol/decimals
|
||||
- Can be linked to price data in `price.ez_prices_hourly` for USD values
|
||||
- Related to NFT mint data in `nft.fact_nft_mints` for lifecycle analysis
|
||||
|
||||
## Commonly-used Fields
|
||||
- `tx_hash`, `event_index`: Unique identifiers for each sale event
|
||||
- `nft_address`, `tokenid`: NFT contract and token identifiers
|
||||
- `seller_address`, `buyer_address`: Addresses involved in the sale
|
||||
- `block_timestamp`: Time of the sale event
|
||||
- `project_name`, `platform_name`: Names of the NFT project and marketplace
|
||||
- `total_price_raw`, `platform_fee_raw`, `creator_fee_raw`: Raw, non-decimal-adjusted price and fee amounts
|
||||
|
||||
{% enddocs %}
|
||||
@ -50,17 +50,17 @@ models:
|
||||
tests:
|
||||
- not_null
|
||||
- name: SYMBOL_IN
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("symbol_in") }}'
|
||||
- name: SYMBOL_OUT
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("symbol_out") }}'
|
||||
- name: AMOUNT_IN
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("amount_in") }}'
|
||||
- name: AMOUNT_OUT
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("amount_out") }}'
|
||||
- name: AMOUNT_IN_USD
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("amount_in_usd") }}'
|
||||
- name: AMOUNT_OUT_USD
|
||||
description: '{{ doc("token_out") }}'
|
||||
description: '{{ doc("amount_out_usd") }}'
|
||||
- name: SWAPPER
|
||||
description: '{{ doc("swapper") }}'
|
||||
tests:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
version: 2
|
||||
models:
|
||||
- name: nft__ez_nft_mints
|
||||
description: A convenience model that combines fact nft mints with tokens and prices
|
||||
description: '{{ doc("nft__ez_nft_mints") }}'
|
||||
tests:
|
||||
- dbt_utils.unique_combination_of_columns:
|
||||
combination_of_columns:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
version: 2
|
||||
models:
|
||||
- name: nft__ez_nft_sales
|
||||
description: A convenience model that combines fact nft sales with tokens and prices
|
||||
description: '{{ doc("nft__ez_nft_sales") }}'
|
||||
tests:
|
||||
- dbt_utils.unique_combination_of_columns:
|
||||
combination_of_columns:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
version: 2
|
||||
models:
|
||||
- name: nft__fact_nft_mints
|
||||
description: This table contains NFT mints events
|
||||
description: '{{ doc("nft__fact_nft_mints") }}'
|
||||
columns:
|
||||
- name: BLOCK_NUMBER
|
||||
description: '{{ doc("nft_block_number") }}'
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
version: 2
|
||||
models:
|
||||
- name: nft__fact_nft_sales
|
||||
description: This table contains NFT sale events from bluemove, mercato, okx, seashrine,souffl3,topaz, and wapal
|
||||
description: '{{ doc("nft__fact_nft_sales") }}'
|
||||
columns:
|
||||
- name: BLOCK_NUMBER
|
||||
description: '{{ doc("nft_block_number") }}'
|
||||
|
||||
Loading…
Reference in New Issue
Block a user