Initial/setup (#1)

* initial commit

* inserted at

* overview updates

* labels and docs

* docs

.gitignore

@@ -0,0 +1,16 @@
+
+target/
+dbt_modules/
+# newer versions of dbt use this directory instead of dbt_modules for test dependencies
+dbt_packages/
+logs/
+
+.venv/
+.python-version
+
+# Visual Studio Code files
+*/.vscode
+*.code-workspace
+.history/
+**/.DS_Store
+.vscode/

README.md

@@ -1 +1,45 @@
-# avalanche-models
+## Profile Set Up
+
+#### Use the following within profiles.yml 
+----
+
+```yml
+avalanche:
+  target: dev
+  outputs:
+    dev:
+      type: snowflake
+      account: <ACCOUNT>
+      role: <ROLE>
+      user: <USERNAME>
+      password: <PASSWORD>
+      region: <REGION>
+      database: AVALANCHE_DEV
+      warehouse: <WAREHOUSE>
+      schema: silver
+      threads: 12
+      client_session_keep_alive: False
+      query_tag: <TAG>
+    prod:
+      type: snowflake
+      account: <ACCOUNT>
+      role: <ROLE>
+      user: <USERNAME>
+      password: <PASSWORD>
+      region: <REGION>
+      database: AVALANCHE
+      warehouse: <WAREHOUSE>
+      schema: silver
+      threads: 12
+      client_session_keep_alive: False
+      query_tag: <TAG>
+```
+
+
+
+### Resources:
+- Learn more about dbt [in the docs](https://docs.getdbt.com/docs/introduction)
+- Check out [Discourse](https://discourse.getdbt.com/) for commonly asked questions and answers
+- Join the [chat](https://community.getdbt.com/) on Slack for live discussions and support
+- Find [dbt events](https://events.getdbt.com) near you
+- Check out [the blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices

dbt_project.yml

@@ -0,0 +1,39 @@
+# Name your project! Project names should contain only lowercase characters
+# and underscores. A good package name should reflect your organization's
+# name or the intended use of these models
+name: "avalanche_models"
+version: "1.0.0"
+config-version: 2
+
+# This setting configures which "profile" dbt uses for this project.
+profile: "avalanche"
+
+# These configurations specify where dbt should look for different types of files.
+# The `source-paths` config, for example, states that models in this project can be
+# found in the "models/" directory. You probably won't need to change these!
+model-paths: ["models"]
+analysis-paths: ["analysis"]
+test-paths: ["tests"]
+seed-paths: ["data"]
+macro-paths: ["macros"]
+snapshot-paths: ["snapshots"]
+
+target-path: "target" # directory which will store compiled SQL files
+clean-targets: # directories to be removed by `dbt clean`
+  - "target"
+  - "dbt_modules"
+  - "dbt_packages"
+
+on-run-start:
+  - "{{ create_sps() }}"
+  - "{{ create_udfs() }}"
+
+# Configuring models
+# Full documentation: https://docs.getdbt.com/docs/configuring-models
+
+# In this example config, we tell dbt to build all models in the example/ directory
+# as tables. These settings can be overridden in the individual model files
+# using the `{{ config(...) }}` macro.
+
+vars:
+  "dbt_date:time_zone": GMT

macros/create_sps.sql

@@ -0,0 +1,6 @@
+{% macro create_sps() %}
+    {% if target.database == 'AVALANCHE' %}
+        CREATE schema IF NOT EXISTS _internal;
+{{ sp_create_prod_clone('_internal') }};
+    {% endif %}
+{% endmacro %}

macros/create_udfs.sql

@@ -0,0 +1,11 @@
+{% macro create_udfs() %}
+    {% set sql %}
+    CREATE schema if NOT EXISTS silver;
+{{ create_js_hex_to_int() }};
+{{ create_udf_hex_to_int(
+        schema = "public"
+    ) }}
+
+    {% endset %}
+    {% do run_query(sql) %}
+{% endmacro %}

macros/custom_naming_macros.sql

@@ -0,0 +1,11 @@
+{% macro generate_schema_name(custom_schema_name=none, node=none) -%}
+    {% set node_name = node.name %}
+    {% set split_name = node_name.split('__') %}
+    {{ split_name[0] | trim }}
+{%- endmacro %}
+
+{% macro generate_alias_name(custom_alias_name=none, node=none) -%}
+    {% set node_name = node.name %}
+    {% set split_name = node_name.split('__') %}
+    {{ split_name[1] | trim }}
+{%- endmacro %}

macros/js_hextoint.sql

@@ -0,0 +1,6 @@
+{% macro create_js_hex_to_int() %}
+    CREATE
+    OR REPLACE FUNCTION {{ target.schema }}.js_hex_to_int (
+        s STRING
+    ) returns DOUBLE LANGUAGE javascript AS 'if (S !== null) { yourNumber = parseInt(S, 16); } return yourNumber'
+{% endmacro %}

macros/python/udfs.sql

@@ -0,0 +1,21 @@
+{% macro create_udf_hex_to_int(schema) %}
+create or replace function {{ schema }}.udf_hex_to_int(hex string)
+returns string
+language python
+runtime_version = '3.8'
+handler = 'hex_to_int'
+as
+$$
+def hex_to_int(hex) -> str:
+  """
+  Converts hex (of any size) to int (as a string). Snowflake and java script can only handle up to 64-bit (38 digits of precision)
+  select hex_to_int('200000000000000000000000000000211');
+  >> 680564733841876926926749214863536423441
+  select hex_to_int('0x200000000000000000000000000000211');
+  >> 680564733841876926926749214863536423441
+  select hex_to_int(NULL);
+  >> NULL
+  """
+  return str(int(hex, 16)) if hex else None
+$$;
+{% endmacro %}

macros/run_sp_create_prod_clone.sql

@@ -0,0 +1,10 @@
+{% macro run_sp_create_prod_clone() %}
+    {% set clone_query %}
+    call avalanche._internal.create_prod_clone(
+        'avalanche',
+        'avalanche_dev',
+        'internal_dev'
+    );
+{% endset %}
+    {% do run_query(clone_query) %}
+{% endmacro %}

macros/sp_create_prod_clone.sql

@@ -0,0 +1,76 @@
+{% macro sp_create_prod_clone(target_schema) -%}
+
+create or replace procedure {{ target_schema }}.create_prod_clone(source_db_name string, destination_db_name string, role_name string)
+returns boolean 
+language javascript
+execute as caller
+as
+$$
+    snowflake.execute({sqlText: `BEGIN TRANSACTION;`});
+    try {
+        snowflake.execute({sqlText: `DROP DATABASE IF EXISTS ${DESTINATION_DB_NAME}`});
+        snowflake.execute({sqlText: `CREATE DATABASE ${DESTINATION_DB_NAME} CLONE ${SOURCE_DB_NAME}`});
+        snowflake.execute({sqlText: `DROP SCHEMA ${DESTINATION_DB_NAME}._INTERNAL`}); /* this only needs to be in prod */
+
+        var existing_schemas = snowflake.execute({sqlText: `SELECT table_schema
+            FROM ${DESTINATION_DB_NAME}.INFORMATION_SCHEMA.TABLE_PRIVILEGES
+            WHERE grantor IS NOT NULL
+            GROUP BY 1
+            UNION
+            SELECT 'PUBLIC';`});
+
+        while (existing_schemas.next()) {
+            var schema = existing_schemas.getColumnValue(1);
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON SCHEMA ${DESTINATION_DB_NAME}.${schema} TO ROLE ${ROLE_NAME} COPY CURRENT GRANTS;`});
+            snowflake.execute({sqlText: `REVOKE OWNERSHIP ON FUTURE FUNCTIONS IN SCHEMA ${DESTINATION_DB_NAME}.${schema} FROM ROLE DBT_CLOUD_AVALANCHE`});
+            snowflake.execute({sqlText: `REVOKE OWNERSHIP ON FUTURE PROCEDURES IN SCHEMA ${DESTINATION_DB_NAME}.${schema} FROM ROLE DBT_CLOUD_AVALANCHE`});
+            snowflake.execute({sqlText: `REVOKE OWNERSHIP ON FUTURE TABLES IN SCHEMA ${DESTINATION_DB_NAME}.${schema} FROM ROLE DBT_CLOUD_AVALANCHE`});
+            snowflake.execute({sqlText: `REVOKE OWNERSHIP ON FUTURE VIEWS IN SCHEMA ${DESTINATION_DB_NAME}.${schema} FROM ROLE DBT_CLOUD_AVALANCHE`});
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON FUTURE FUNCTIONS IN SCHEMA ${DESTINATION_DB_NAME}.${schema} TO ROLE ${ROLE_NAME};`});
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON FUTURE PROCEDURES IN SCHEMA ${DESTINATION_DB_NAME}.${schema} TO ROLE ${ROLE_NAME};`});
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON FUTURE TABLES IN SCHEMA ${DESTINATION_DB_NAME}.${schema} TO ROLE ${ROLE_NAME};`});
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON FUTURE VIEWS IN SCHEMA ${DESTINATION_DB_NAME}.${schema} TO ROLE ${ROLE_NAME};`});
+        }
+
+        var existing_tables = snowflake.execute({sqlText: `SELECT table_schema, table_name
+            FROM ${DESTINATION_DB_NAME}.INFORMATION_SCHEMA.TABLE_PRIVILEGES
+            WHERE grantor IS NOT NULL
+            GROUP BY 1,2;`});
+
+        while (existing_tables.next()) {
+            var schema = existing_tables.getColumnValue(1);
+            var table_name = existing_tables.getColumnValue(2);
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON TABLE ${DESTINATION_DB_NAME}.${schema}.${table_name} TO ROLE ${ROLE_NAME} COPY CURRENT GRANTS;`});
+        }
+
+        var existing_functions = snowflake.execute({sqlText: `SELECT function_schema, function_name, concat('(',array_to_string(regexp_substr_all(argument_signature, 'VARCHAR|NUMBER|FLOAT|ARRAY|VARIANT|OBJECT|DOUBLE'),','),')') as argument_signature
+            FROM ${DESTINATION_DB_NAME}.INFORMATION_SCHEMA.FUNCTIONS;`});
+
+        while (existing_functions.next()) {
+            var schema = existing_functions.getColumnValue(1);
+            var function_name = existing_functions.getColumnValue(2);
+            var argument_signature = existing_functions.getColumnValue(3);
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON FUNCTION ${DESTINATION_DB_NAME}.${schema}.${function_name}${argument_signature} to role ${ROLE_NAME} REVOKE CURRENT GRANTS;`});
+        }
+
+        var existing_procedures = snowflake.execute({sqlText: `SELECT procedure_schema, procedure_name, concat('(',array_to_string(regexp_substr_all(argument_signature, 'VARCHAR|NUMBER|FLOAT|ARRAY|VARIANT|OBJECT|DOUBLE'),','),')') as argument_signature
+            FROM ${DESTINATION_DB_NAME}.INFORMATION_SCHEMA.PROCEDURES;`});
+
+        while (existing_procedures.next()) {
+            var schema = existing_procedures.getColumnValue(1);
+            var procedure_name = existing_procedures.getColumnValue(2);
+            var argument_signature = existing_procedures.getColumnValue(3);
+            snowflake.execute({sqlText: `GRANT OWNERSHIP ON PROCEDURE ${DESTINATION_DB_NAME}.${schema}.${procedure_name}${argument_signature} to role ${ROLE_NAME} REVOKE CURRENT GRANTS;`});
+        }
+
+        snowflake.execute({sqlText: `GRANT OWNERSHIP ON DATABASE ${DESTINATION_DB_NAME} TO ROLE ${ROLE_NAME};`})
+        snowflake.execute({sqlText: `COMMIT;`});
+    } catch (err) {
+        snowflake.execute({sqlText: `ROLLBACK;`});
+        throw(err);
+    }
+    
+    return true
+$$
+
+{%- endmacro %}

macros/tests/sequence_gaps.sql

@@ -0,0 +1,34 @@
+{% test sequence_gaps(
+    model,
+    partition_by,
+    column_name
+) %}
+{%- set partition_sql = partition_by | join(", ") -%}
+{%- set previous_column = "prev_" ~ column_name -%}
+WITH source AS (
+    SELECT
+        {{ partition_sql + "," if partition_sql }}
+        {{ column_name }},
+        LAG(
+            {{ column_name }},
+            1
+        ) over (
+            {{ "PARTITION BY " ~ partition_sql if partition_sql }}
+            ORDER BY
+                {{ column_name }} ASC
+        ) AS {{ previous_column }}
+    FROM
+        {{ model }}
+)
+SELECT
+    {{ partition_sql + "," if partition_sql }}
+    {{ previous_column }},
+    {{ column_name }},
+    {{ column_name }} - {{ previous_column }}
+    - 1 AS gap
+FROM
+    source
+WHERE
+    {{ column_name }} - {{ previous_column }} <> 1
+ORDER BY
+    gap DESC {% endtest %}

macros/tests/tx_gaps.sql

@@ -0,0 +1,33 @@
+{% macro tx_gaps(
+        model
+    ) %}
+    WITH block_base AS (
+        SELECT
+            block_number,
+            tx_count
+        FROM
+            {{ ref('silver__blocks') }}
+    ),
+    model_name AS (
+        SELECT
+            block_number,
+            COUNT(
+                DISTINCT tx_hash
+            ) AS model_tx_count
+        FROM
+            {{ model }}
+        GROUP BY
+            block_number
+    )
+SELECT
+    block_base.block_number,
+    tx_count,
+    model_name.block_number,
+    model_tx_count
+FROM
+    block_base
+    LEFT JOIN model_name
+    ON block_base.block_number = model_name.block_number
+WHERE
+    tx_count <> model_tx_count
+{% endmacro %}

models/bronze/bronze__blocks.sql

@@ -0,0 +1,23 @@
+{{ config (
+    materialized = 'view'
+) }}
+
+SELECT
+    record_id,
+    offset_id,
+    block_id,
+    block_timestamp,
+    network,
+    chain_id,
+    tx_count,
+    header,
+    ingested_at,
+    _inserted_timestamp
+FROM
+    {{ source(
+        'prod',
+        'avalanche_blocks'
+    ) }}
+    qualify(ROW_NUMBER() over(PARTITION BY block_id
+ORDER BY
+    _inserted_timestamp DESC)) = 1

models/bronze/bronze__transactions.sql

@@ -0,0 +1,21 @@
+{{ config (
+    materialized = 'view'
+) }}
+
+SELECT
+    record_id,
+    tx_id,
+    tx_block_index,
+    offset_id,
+    block_id,
+    block_timestamp,
+    network,
+    chain_id,
+    tx,
+    ingested_at,
+    _inserted_timestamp
+FROM
+    {{ source(
+        'prod',
+        'avalanche_txs'
+    ) }}

models/doc_descriptions/blocks/avax_block_header_json.md

@@ -0,0 +1,5 @@
+{% docs avax_block_header_json %}
+
+This JSON column contains the block header details. 
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_blockchain.md

@@ -0,0 +1,5 @@
+{% docs avax_blockchain %}
+
+The blockchain on which transactions are being confirmed.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_blocks_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_blocks_hash %}
+
+The hash of the block header for a given block. 
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_blocks_nonce.md

@@ -0,0 +1,5 @@
+{% docs avax_blocks_nonce %}
+
+Block nonce is a value used during mining to demonstrate proof of work for a given block. 
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_blocks_table_doc.md

@@ -0,0 +1,5 @@
+{% docs avax_blocks_table_doc %}
+
+This table contains block level data for the Avalanche Blockchain. This table can be used to analyze trends at a block level, for example gas fees vs. total transactions over time. For more information on EVM transactions, please see [Etherscan Resources](https://etherscan.io/directory/Learning_Resources/Ethereum) or [The Ethereum Organization](https://ethereum.org/en/developers/docs/blocks/)
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_difficulty.md

@@ -0,0 +1,5 @@
+{% docs avax_difficulty %}
+
+The effort required to mine the block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_extra_data.md

@@ -0,0 +1,5 @@
+{% docs avax_extra_data %}
+
+Any data included by the validator for a given block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_gas_limit.md

@@ -0,0 +1,5 @@
+{% docs avax_gas_limit %}
+
+Total gas limit provided by all transactions in the block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_gas_used.md

@@ -0,0 +1,5 @@
+{% docs avax_gas_used %}
+
+Total gas used in the block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_miner.md

@@ -0,0 +1,5 @@
+{% docs avax_miner %}
+
+Miner who successfully added a given block to the blockchain. 
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_network.md

@@ -0,0 +1,5 @@
+{% docs avax_network %}
+
+The network on the blockchain used by a transaction.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_parent_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_parent_hash %}
+
+The hash of the block from which a given block is generated. Also known as the parent block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_receipts_root.md

@@ -0,0 +1,5 @@
+{% docs avax_receipts_root %}
+
+The root of the state trie.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_sha3_uncles.md

@@ -0,0 +1,5 @@
+{% docs avax_sha3_uncles %}
+
+The mechanism which Ethereum Javascript RLP encodes an empty string.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_size.md

@@ -0,0 +1,5 @@
+{% docs avax_size %}
+
+Block size, which is determined by a given block's gas limit.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_total_difficulty.md

@@ -0,0 +1,5 @@
+{% docs avax_total_difficulty %}
+
+Total difficulty of the chain at a given block. 
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_tx_count.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_count %}
+
+Total number of transactions within a block.
+
+{% enddocs %}

models/doc_descriptions/blocks/avax_uncle_blocks.md

@@ -0,0 +1,5 @@
+{% docs avax_uncle_blocks %}
+
+Uncle blocks occur when two blocks are mined and broadcasted at the same time, with the same block number. The block validated across the most nodes will be added to the primary chain, and the other one becomes an uncle block. Miners do receive rewards for uncle blocks.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_event_index.md

@@ -0,0 +1,5 @@
+{% docs avax_event_index %}
+
+Event number within a transaction.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_event_inputs.md

@@ -0,0 +1,5 @@
+{% docs avax_event_inputs %}
+
+The decoded event inputs for a given event.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_event_name.md

@@ -0,0 +1,5 @@
+{% docs avax_event_name %}
+
+The decoded event name for a given event.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_event_removed.md

@@ -0,0 +1,5 @@
+{% docs avax_event_removed %}
+
+Whether the event has been removed from the transaction.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_event_sig.md

@@ -0,0 +1,5 @@
+{% docs avax_origin_sig %}
+
+The function signature of this transaction.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_log_id_events.md

@@ -0,0 +1,5 @@
+{% docs avax_log_id_events %}
+
+This is the primary key for this table. This is a concatenation of the transaction hash and the event index at which the event occurred. 
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_logs_contract_address.md

@@ -0,0 +1,5 @@
+{% docs avax_logs_contract_address %}
+
+The address interacted with for a given event.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_logs_contract_name.md

@@ -0,0 +1,5 @@
+{% docs avax_logs_contract_name %}
+
+The name of the contract or token, where possible.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_logs_data.md

@@ -0,0 +1,5 @@
+{% docs avax_logs_data %}
+
+The un-decoded event data.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_logs_table_doc.md

@@ -0,0 +1,5 @@
+{% docs avax_logs_table_doc %}
+
+This table contains flattened event logs from transactions on the Avalanche Blockchain. Transactions may have multiple events, which are denoted by the event index for a transaction hash. Therefore, this table is unique on the combination of transaction hash and event index. Event names are decoded in this table where possible. The event inputs column will contain the log details in JSON format. Specific fields can be pulled from this column using the following sample format: ```event_inputs:<FILED_NAME>::<DATA TYPE> as <FIELD_NAME>```. 
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_logs_tx_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_logs_tx_hash %}
+
+Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. This field will not be unique in this table, as a given transaction can include multiple events.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_origin_from.md

@@ -0,0 +1,5 @@
+{% docs avax_origin_from %}
+
+The from address of this transaction.
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_origin_to.md

@@ -0,0 +1,5 @@
+{% docs avax_origin_to %}
+
+The to address of this transaction. 
+
+{% enddocs %}

models/doc_descriptions/event_logs/avax_topics.md

@@ -0,0 +1,5 @@
+{% docs avax_topics %}
+
+The un-decoded event input topics.
+
+{% enddocs %}

models/doc_descriptions/general/__overview__.md

@@ -0,0 +1,79 @@
+{% docs __overview__ %}
+
+# Welcome to the Flipside Crypto Avalanche C-Chain Models Documentation!
+
+# NOTE: Data is in 'lite mode' - meaning, histrorical data has not yet been backfilled. Please see `min(block_timestamp)`
+
+## **What is Flipside?**
+
+[Flipside Crypto](https://flipsidecrypto.xyz/earn) provides Community Enabled Crypto Analytics, allowing our users to create and share data insights on the crypto projects they care most about.
+
+**Flipside Crypto puts pre-modeled and labeled blockchain data in the hands of communities.**
+
+Through dashboard and visualization tools, as well as auto-generated API endpoints, data analysts can easily create queries that answer any question via a tool called [Velocity](https://app.flipsidecrypto.com/velocity?nav=Discover).
+
+**Community members earn bounties for answering questions with data.**
+
+Bounties provide incentive and direction, so crypto projects can quickly source the data insights they need in order to grow.
+
+**Flipside works directly with leading crypto projects to reward on-demand analytics through structured bounty programs.**
+
+Questions sourced directly from the community provide insight into what communities care about as well as analytics needed to drive ecosystem engagement and growth.
+
+## **What does this documentation cover?**
+The documentation included here details the design of the Avalanche tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/earn) For more information on how these models are built, please see [the github repository.](https://github.com/FlipsideCrypto/avalanche-models)
+
+### **Quick Links to Table Documentation**
+
+- [fact_blocks](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche_models.core__fact_blocks)
+- [fact_event_logs](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche_models.core__fact_event_logs)
+- [fact_traces](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche_models.core__fact_traces)
+- [fact_transactions](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche_models.core__fact_transactions)
+- [dim_lables](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche_models.core__dim_labels)
+
+## **Data Model Overview**
+
+The Avalanche models are built a few different ways, but the core fact table are built using three layers of sql models: **bronze, silver, and gold (or core).**
+
+- Bronze: Data is loaded in from the source as a view
+- Silver: All necessary parsing, filtering, de-duping, and other transformations are done here
+- Gold (or core): Final views and tables that are available in Velocity
+
+The dimension tables are sourced from a variety of on-chain and off-chain sources.
+
+Convenience views (denoted ez_) are a combination of different fact and dimension tables. 
+
+A user-defined-function (UDF) is available to decode hex encoded values to integers in this database. You can call this UDF by using `avalanche.public.udf_hex_to_int(FIELD)`.
+
+
+## **Using dbt docs**
+### Navigation
+
+You can use the ```Project``` and ```Database``` navigation tabs on the left side of the window to explore the models in the project.
+
+### Database Tab
+
+This view shows relations (tables and views) grouped into database schemas. Note that ephemeral models are *not* shown in this interface, as they do not exist in the database.
+
+### Graph Exploration
+
+You can click the blue icon on the bottom-right corner of the page to view the lineage graph of your models.
+
+On model pages, you'll see the immediate parents and children of the model you're exploring. By clicking the Expand button at the top-right of this lineage pane, you'll be able to see all of the models that are used to build, or are built from, the model you're exploring.
+
+Once expanded, you'll be able to use the ```--models``` and ```--exclude``` model selection syntax to filter the models in the graph. For more information on model selection, check out the [dbt docs](https://docs.getdbt.com/docs/model-selection-syntax).
+
+Note that you can also right-click on models to interactively filter and explore the graph.
+
+
+### **More information**
+- [Flipside](https://flipsidecrypto.xyz/earn)
+- [Velocity](https://app.flipsidecrypto.com/velocity?nav=Discover)
+- [Tutorials](https://docs.flipsidecrypto.com/our-data/tutorials)
+- [Github](https://github.com/FlipsideCrypto/avalanche-models)
+- [Query Editor Shortcuts](https://docs.flipsidecrypto.com/velocity/query-editor-shortcuts)
+- [What is dbt?](https://docs.getdbt.com/docs/introduction)
+
+
+
+{% enddocs %}

models/doc_descriptions/general/avax_block_number.md

@@ -0,0 +1,5 @@
+{% docs avax_block_number %}
+
+Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block.   
+
+{% enddocs %}

models/doc_descriptions/general/avax_block_timestamp.md

@@ -0,0 +1,5 @@
+{% docs avax_block_timestamp %}
+
+The date and time at which the block was produced.  
+
+{% enddocs %}

models/doc_descriptions/general/avax_decimals.md

@@ -0,0 +1,5 @@
+{% docs avax_decimals %}
+
+The number of decimal places this contract needs adjusted where token values exist. For example, use the decimal field to correctly transform raw amounts in ```fact_token_transfers```. 
+
+{% enddocs %}

models/doc_descriptions/general/avax_from_address.md

@@ -0,0 +1,5 @@
+{% docs avax_from_address %}
+
+The sending address of this transaction. 
+
+{% enddocs %}

models/doc_descriptions/general/avax_ingested_at.md

@@ -0,0 +1,5 @@
+{% docs avax_ingested_at %}
+
+Internal column.
+
+{% enddocs %}

models/doc_descriptions/general/avax_to_address.md

@@ -0,0 +1,5 @@
+{% docs avax_to_address %}
+
+The receiving address of this transaction. This can be a contract address. 
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label.md

@@ -0,0 +1,5 @@
+{% docs avax_project_name %}
+
+The name of the project for this address. 
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_address.md

@@ -0,0 +1,5 @@
+{% docs avax_label_address %}
+
+Address that the label is for. This is the field that should be used to join other tables with labels. 
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_address_name.md

@@ -0,0 +1,5 @@
+{% docs avax_label_address_name %}
+
+The most granular label for this address.  
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_blockchain.md

@@ -0,0 +1,5 @@
+{% docs avax_label_blockchain %}
+
+The name of the blockchain.
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_creator.md

@@ -0,0 +1,5 @@
+{% docs avax_label_creator %}
+
+The name of the creator of the label.
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_subtype.md

@@ -0,0 +1,5 @@
+{% docs avax_label_subtype %}
+
+A sub-category nested within label type providing further detail.
+
+{% enddocs %}

models/doc_descriptions/labels/avax_label_type.md

@@ -0,0 +1,5 @@
+{% docs avax_label_type %}
+
+A high-level category describing the addresses main function or ownership.
+
+{% enddocs %}

models/doc_descriptions/labels/avax_labels_table_doc.md

@@ -0,0 +1,5 @@
+{% docs avax_labels_table %}
+
+This table contains labels for addresses on the Avalanche Blockchain. 
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_block_no.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_block_no %}
+
+The block number of this transaction.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_blocktime.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_blocktime %}
+
+The block timestamp of this transaction.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_call_data.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_call_data %}
+
+The raw JSON data for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_from.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_from %}
+
+The sending address of this trace. This is not necessarily the from address of the transaction. 
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_gas.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_gas %}
+
+The gas supplied for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_gas_used.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_gas_used %}
+
+The gas used for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_identifier.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_identifier %}
+
+This field represents the position and type of the trace within the transaction. 
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_input.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_input %}
+
+The input data for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_output.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_output %}
+
+The output data for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_sub.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_sub %}
+
+The amount of nested sub traces for this trace.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_table_doc.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_table_doc %}
+
+This table contains flattened trace data for internal contract calls on the Avalanche Blockchain. Hex encoded fields can be decoded to integers by using `avalanche.public.udf_hex_to_int()`.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_to.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_to %}
+
+The receiving address of this trace. This is not necessarily the to address of the transaction. 
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_tx_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_tx_hash %}
+
+The transaction hash for the trace. Please note, this is not necessarily unique in this table as transactions frequently have multiple traces. 
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_type.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_type %}
+
+The type of internal transaction. Common trace types are `CALL`, `DELEGATECALL`, and `STATICCALL`.
+
+{% enddocs %}

models/doc_descriptions/traces/avax_traces_value.md

@@ -0,0 +1,5 @@
+{% docs avax_traces_value %}
+
+The amount of ETH transferred in this trace.
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_cumulative_gas_used.md

@@ -0,0 +1,5 @@
+{% docs avax_cumulative_gas_used %}
+
+The total amount of gas used when this transaction was executed in the block. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_block_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_block_hash %}
+
+Block hash is a unique 66-character identifier that is generate when a block is produced. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_fee.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_fee %}
+
+Amount paid to validate the transaction in ETH. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_gas_limit.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_gas_limit %}
+
+Maximum amount of gas allocated for the transaction. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_gas_price.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_gas_price %}
+
+Cost per unit of gas in Gwei. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_gas_used.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_gas_used %}
+
+Gas used by transaction.
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_hash.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_hash %}
+
+Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_input_data.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_input_data %}
+
+This column contains additional data for this transaction, and is commonly used as part of a contract interaction or as a message to the recipient.  
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_json.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_json %}
+
+This JSON column contains the transaction details, including event logs. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_nonce.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_nonce %}
+
+The number of transactions sent from a given address. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_origin_sig.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_origin_sig %}
+
+The function signature of the contract call. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_position.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_position %}
+
+The position of the transaction within the block. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_status.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_status %}
+
+Status of the transaction. 
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_tx_table_doc.md

@@ -0,0 +1,5 @@
+{% docs avax_tx_table_doc %}
+
+This table contains transaction level data for the Avalanche Blockchain. Each transaction will have a unique transaction hash, along with transactions fees and a ETH value transferred when applicable. Transactions may be native ETH transfers or interactions with contract addresses. For more information, please see [The Ethereum Organization - Transactions](https://ethereum.org/en/developers/docs/transactions/)
+
+{% enddocs %}

models/doc_descriptions/transactions/avax_value.md

@@ -0,0 +1,5 @@
+{% docs avax_value %}
+
+The value transacted in ETH. 
+
+{% enddocs %}

models/gold/core__dim_labels.sql

@@ -0,0 +1,22 @@
+{{ config(
+    materialized = 'view',
+    persist_docs ={ "relation": true,
+    "columns": true }
+) }}
+
+SELECT
+    blockchain,
+    creator,
+    address,
+    address_name,
+    label_type,
+    label_subtype,
+    project_name
+FROM
+    {{ source(
+        'crosschain',
+        'address_labels'
+    ) }}
+WHERE
+    blockchain = 'avalanche'
+    AND address LIKE '0x%'

models/gold/core__dim_labels.yml

@@ -0,0 +1,57 @@
+version: 2
+models:
+  - name: core__dim_labels
+    description: '{{ doc("avax_labels_table") }}'
+    tests:
+      - dbt_utils.unique_combination_of_columns:
+          combination_of_columns:
+            - BLOCKCHAIN
+            - CREATOR
+            - ADDRESS
+    columns:
+      - name: BLOCKCHAIN
+        description: '{{ doc("avax_label_blockchain") }}'
+        tests:
+          - not_null
+          - dbt_expectations.expect_column_values_to_be_in_set:
+              value_set: ['avalanche']
+      - name: CREATOR
+        description: '{{ doc("avax_label_creator") }}'
+        tests:
+          - not_null
+      - name: ADDRESS
+        description: '{{ doc("avax_label_address") }}'
+        tests:
+          - not_null
+          - dbt_expectations.expect_column_values_to_match_regex:
+              regex: 0[xX][0-9a-fA-F]+
+      - name: ADDRESS_NAME
+        description: '{{ doc("avax_labels_table") }}'
+        tests:
+          - dbt_expectations.expect_column_values_to_be_in_type_list:
+              column_type_list:
+                - STRING
+                - VARCHAR
+      - name: LABEL_TYPE
+        description: '{{ doc("avax_label_type") }}'
+        tests:
+          - not_null
+          - dbt_expectations.expect_column_values_to_be_in_set:
+              value_set: ['flotsam', 'nft', 'defi', 'dex', 'cex', 'dapp', 'token', 'operator', 'layer2', 'chadmin', 'project']
+      - name: LABEL_SUBTYPE
+        description: '{{ doc("avax_label_subtype") }}'
+        tests:
+          - not_null
+          - dbt_expectations.expect_column_values_to_be_in_type_list:
+              column_type_list:
+                - STRING
+                - VARCHAR
+      - name: PROJECT_NAME
+        description: '{{ doc("avax_project_name") }}'
+        tests:
+          - not_null
+          - dbt_expectations.expect_column_values_to_be_in_type_list:
+              column_type_list:
+                - STRING
+                - VARCHAR
+

models/gold/core__fact_blocks.sql

@@ -0,0 +1,26 @@
+{{ config(
+    materialized = 'view',
+    persist_docs ={ "relation": true,
+    "columns": true }
+) }}
+
+SELECT
+    block_number,
+    block_timestamp,
+    network,
+    blockchain,
+    tx_count,
+    difficulty,
+    total_difficulty,
+    extra_data,
+    gas_limit,
+    gas_used,
+    HASH,
+    parent_hash,
+    receipts_root,
+    sha3_uncles,
+    SIZE,
+    uncle_blocks,
+    block_header_json
+FROM
+    {{ ref('silver__blocks') }}

models/gold/core__fact_blocks.yml

@@ -0,0 +1,40 @@
+version: 2
+models:
+  - name: core__fact_blocks
+    description: '{{ doc("avax_blocks_table_doc") }}'   
+
+    columns:
+      - name: BLOCK_NUMBER
+        description: '{{ doc("avax_block_number") }}'   
+      - name: BLOCK_TIMESTAMP
+        description: '{{ doc("avax_block_timestamp") }}'
+      - name: NETWORK
+        description: '{{ doc("avax_network") }}'
+      - name: BLOCKCHAIN
+        description: '{{ doc("avax_blockchain") }}'
+      - name: TX_COUNT
+        description: '{{ doc("avax_tx_count") }}'
+      - name: DIFFICULTY
+        description: '{{ doc("avax_difficulty") }}'
+      - name: TOTAL_DIFFICULTY
+        description: '{{ doc("avax_total_difficulty") }}'
+      - name: EXTRA_DATA
+        description: '{{ doc("avax_extra_data") }}'
+      - name: GAS_LIMIT
+        description: '{{ doc("avax_gas_limit") }}'
+      - name: GAS_USED
+        description: '{{ doc("avax_gas_used") }}'
+      - name: HASH
+        description: '{{ doc("avax_blocks_hash") }}'
+      - name: PARENT_HASH
+        description: '{{ doc("avax_parent_hash") }}'
+      - name: RECEIPTS_ROOT
+        description: '{{ doc("avax_receipts_root") }}'
+      - name: SHA3_UNCLES
+        description: '{{ doc("avax_sha3_uncles") }}'
+      - name: SIZE
+        description: '{{ doc("avax_size") }}' 
+      - name: UNCLE_BLOCKS
+        description: '{{ doc("avax_uncle_blocks") }}' 
+      - name: BLOCK_HEADER_JSON
+        description: '{{ doc("avax_block_header_json") }}'

models/gold/core__fact_event_logs.sql

@@ -0,0 +1,25 @@
+{{ config(
+    materialized = 'view',
+    persist_docs ={ "relation": true,
+    "columns": true }
+) }}
+
+SELECT
+    block_number,
+    block_timestamp,
+    tx_hash,
+    origin_function_signature,
+    origin_from_address,
+    origin_to_address,
+    event_index,
+    contract_address,
+    contract_name,
+    event_name,
+    event_inputs,
+    topics,
+    DATA,
+    event_removed,
+    tx_status,
+    _log_id
+FROM
+    {{ ref('silver__logs') }}

models/gold/core__fact_event_logs.yml

@@ -0,0 +1,38 @@
+version: 2
+models:
+  - name: core__fact_event_logs
+    description: '{{ doc("avax_logs_table_doc") }}'
+
+    columns:
+      - name: BLOCK_NUMBER
+        description: '{{ doc("avax_block_number") }}'   
+      - name: BLOCK_TIMESTAMP
+        description: '{{ doc("avax_block_timestamp") }}'
+      - name: TX_HASH
+        description: '{{ doc("avax_logs_tx_hash") }}'
+      - name: EVENT_INDEX
+        description: '{{ doc("avax_event_index") }}'
+      - name: CONTRACT_ADDRESS
+        description: '{{ doc("avax_logs_contract_address") }}'
+      - name: CONTRACT_NAME
+        description: '{{ doc("avax_logs_contract_name") }}'
+      - name: EVENT_NAME
+        description: '{{ doc("avax_event_name") }}'
+      - name: EVENT_INPUTS
+        description: '{{ doc("avax_event_inputs") }}'
+      - name: TOPICS
+        description: '{{ doc("avax_topics") }}'
+      - name: DATA
+        description: '{{ doc("avax_logs_data") }}'
+      - name: EVENT_REMOVED
+        description: '{{ doc("avax_event_removed") }}'  
+      - name: _LOG_ID
+        description: '{{ doc("avax_log_id_events") }}'  
+      - name: TX_STATUS
+        description: '{{ doc("avax_tx_status") }}' 
+      - name: ORIGIN_FUNCTION_SIGNATURE
+        description: '{{ doc("avax_origin_sig") }}'
+      - name: ORIGIN_FROM_ADDRESS
+        description: '{{ doc("avax_origin_from") }}'
+      - name: ORIGIN_TO_ADDRESS
+        description: '{{ doc("avax_origin_to") }}'