fix: prelaunch

.github/workflows/dbt_run_dev_refresh.yml

@@ -3,11 +3,11 @@ run-name: dbt_run_dev_refresh
 
 on:
   workflow_dispatch:
-  # schedule:
+    # schedule:
     # TODO enable schedule when ready
     # Runs "at 9:00 UTC" (see https://crontab.guru)
-    # - cron: '0 9 * * *'
-    
+    - cron: "0 9 * * *"
+
 env:
   USE_VARS: "${{ vars.USE_VARS }}"
   DBT_PROFILES_DIR: "${{ vars.DBT_PROFILES_DIR }}"
@@ -32,4 +32,4 @@ jobs:
         dbt run-operation run_sp_create_prod_clone
       environment: workflow_prod
       warehouse: ${{ vars.WAREHOUSE }}
-    secrets: inherit 
+    secrets: inherit

.github/workflows/dbt_test_daily.yml

@@ -3,9 +3,9 @@ run-name: dbt_test_daily
 
 on:
   workflow_dispatch:
-  #schedule:
-  # Run at 1600 UTC daily (see https://crontab.guru)
-  #- cron: "0 9 * * *"
+    #schedule:
+    # Run at 1600 UTC daily (see https://crontab.guru)
+    - cron: "0 9 * * *"
 env:
   USE_VARS: "${{ vars.USE_VARS }}"
   DBT_PROFILES_DIR: "${{ vars.DBT_PROFILES_DIR }}"

.github/workflows/dbt_test_weekly.yml

@@ -3,9 +3,9 @@ run-name: dbt_test_weekly
 
 on:
   workflow_dispatch:
-  #schedule:
-  # Run at 1600 UTC Monday (see https://crontab.guru)
-  #- cron: "0 9 * * 1"
+    #schedule:
+    # Run at 1600 UTC Monday (see https://crontab.guru)
+    - cron: "0 9 * * 1"
 env:
   USE_VARS: "${{ vars.USE_VARS }}"
   DBT_PROFILES_DIR: "${{ vars.DBT_PROFILES_DIR }}"

models/descriptions/__overview__.md

@@ -3,10 +3,12 @@
 # Welcome to the Flipside Crypto Aurora Models Documentation
 
 ## **What does this documentation cover?**
+
 The documentation included here details the design of the Aurora
- tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/) For more information on how these models are built, please see [the github repository.](https://github.com/flipsideCrypto/aurora-models/)
+tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/) For more information on how these models are built, please see [the github repository.](https://github.com/flipsideCrypto/aurora-models/)
 
 ## **How do I use these docs?**
+
 The easiest way to navigate this documentation is to use the Quick Links below. These links will take you to the documentation for each table, which contains a description, a list of the columns, and other helpful information.
 
 If you are experienced with dbt docs, feel free to use the sidebar to navigate the documentation, as well as explore the relationships between tables and the logic building them.
@@ -19,17 +21,12 @@ There is more information on how to use dbt docs in the last section of this doc
 
 ### Core Tables (`AURORA`.`CORE`.`<table_name>`)
 
-**Dimension Tables:**
-
-
 **Fact Tables:**
 
-
-
-**Convenience Tables:**
-
-
-
+- [fact_blocks]()
+- [fact_transactions]()
+- [fact_logs]()
+- [fact_receipts]()
 
 ## **Data Model Overview**
 
@@ -41,16 +38,17 @@ The Aurora models are built a few different ways, but the core fact tables are b
 
 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. These views are built to make it easier to query the data.
+Convenience views (denoted ez\_) are a combination of different fact and dimension tables. These views are built to make it easier to query the data.
 
 ## **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.
+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.
+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
 
@@ -58,16 +56,16 @@ You can click the blue icon on the bottom-right corner of the page to view the l
 
 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).
+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/)
 - [Velocity](https://app.flipsidecrypto.com/velocity?nav=Discover)
 - [Tutorials](https://docs.flipsidecrypto.com/our-data/tutorials)
 - [Github](https://github.com/FlipsideCrypto/aurora-models)
 - [What is dbt?](https://docs.getdbt.com/docs/introduction)
 
-{% enddocs %}
+{% enddocs %}

models/silver/silver__transactions.sql

@@ -44,7 +44,7 @@ base_tx AS (
         ) :: INT AS gas,
         utils.udf_hex_to_int(
             A.data :gasPrice :: STRING
-        ) :: INT / pow(
+        ) :: FLOAT / pow(
             10,
             9
         ) AS gas_price,
@@ -57,13 +57,13 @@ base_tx AS (
         ) AS origin_function_signature,
         COALESCE(utils.udf_hex_to_int(
             A.data :maxFeePerGas :: STRING
-        ) :: INT / pow(
+        ) :: FLOAT / pow(
             10,
             9
         ), 0)  AS max_fee_per_gas,
         COALESCE( utils.udf_hex_to_int(
             A.data :maxPriorityFeePerGas :: STRING
-        ) :: INT / pow(
+        ) :: FLOAT / pow(
             10,
             9
         ), 0) AS max_priority_fee_per_gas,