mirror of
https://github.com/FlipsideCrypto/avalanche-models.git
synced 2026-02-06 11:06:55 +00:00
docs (#9)
This commit is contained in:
parent
d7b0eec545
commit
513df9b9c1
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,5 +0,0 @@
|
||||
{% docs avax_eth_amount %}
|
||||
|
||||
ETH value transferred.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +0,0 @@
|
||||
{% docs avax_ez_eth_transfers_table_doc %}
|
||||
|
||||
This table contains all native ETH transfers, including equivalent USD amounts. The origin addresses correspond to the to and from addresses from the `fact_transactions` table. The `identifier` and `tx_hash` columns relate this table back to `fact_traces`, which contains more details on the transfers.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +0,0 @@
|
||||
{% docs avax_eth_origin_from %}
|
||||
|
||||
The from address at the transaction level.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +0,0 @@
|
||||
{% docs avax_transfer_table_doc %}
|
||||
|
||||
This table contains events on the Ethereum Blockchain with an event name of 'Transfer'. The contract address is the token transferred, and the raw amount field is the amount of tokens transferred. Please note this amount is not decimal adjusted. Decimal adjustments for a token address can be found in ```dim_contracts```. This table will not contain transfers of native ETH.
|
||||
|
||||
{% enddocs %}
|
||||
5
models/doc_descriptions/transfers/avax_eth_amount.md
Normal file
5
models/doc_descriptions/transfers/avax_eth_amount.md
Normal file
@ -0,0 +1,5 @@
|
||||
{% docs avax_amount %}
|
||||
|
||||
AVAX value transferred.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,6 +1,6 @@
|
||||
|
||||
{% docs avax_eth_amount_usd %}
|
||||
|
||||
ETH value transferred, in USD.
|
||||
AVAX value transferred, in USD.
|
||||
|
||||
{% enddocs %}
|
||||
@ -0,0 +1,5 @@
|
||||
{% docs avax_ez_eth_transfers_table_doc %}
|
||||
|
||||
This table contains all native AVAX transfers, including equivalent USD amounts. The origin addresses correspond to the to and from addresses from the `fact_transactions` table. The `identifier` and `tx_hash` columns relate this table back to `fact_traces`, which contains more details on the transfers.
|
||||
|
||||
{% enddocs %}
|
||||
@ -1,5 +1,5 @@
|
||||
{% docs avax_ez_transfer_table_doc %}
|
||||
|
||||
This table will contain all events in the ```fact_token_transfers table```, along with joined columns such as token price, symbol, and decimals where possible that allow for easier analysis of token transfer events. Please note Native ETH transfers are not included here.
|
||||
This table will contain all events in the ```fact_token_transfers table```, along with joined columns such as token price, symbol, and decimals where possible that allow for easier analysis of token transfer events. Please note Native AVAX transfers are not included here.
|
||||
|
||||
{% enddocs %}
|
||||
@ -0,0 +1,5 @@
|
||||
{% docs avax_transfer_table_doc %}
|
||||
|
||||
This table contains events on the Avalanche Blockchain with an event name of 'Transfer'. The contract address is the token transferred, and the raw amount field is the amount of tokens transferred. Please note this amount is not decimal adjusted. Decimal adjustments for a token address can be found in ```dim_contracts```. This table will not contain transfers of native ETH.
|
||||
|
||||
{% enddocs %}
|
||||
@ -15,13 +15,9 @@ models:
|
||||
- name: ETH_TO_ADDRESS
|
||||
description: '{{ doc("avax_transfer_to_address") }}'
|
||||
- name: AMOUNT
|
||||
description: '{{ doc("avax_eth_amount") }}'
|
||||
- name: TOKEN_PRICE
|
||||
description: '{{ doc("avax_transfer_token_price") }}'
|
||||
description: '{{ doc("avax_amount") }}'
|
||||
- name: AMOUNT_USD
|
||||
description: '{{ doc("avax_eth_amount_usd") }}'
|
||||
- name: HAS_PRICE
|
||||
description: '{{ doc("avax_transfer_has_price") }}'
|
||||
- name: ORIGIN_FUNCTION_SIGNATURE
|
||||
description: '{{ doc("avax_origin_sig") }}'
|
||||
- name: ORIGIN_FROM_ADDRESS
|
||||
|
||||
Loading…
Reference in New Issue
Block a user