initial updates

README.md

@@ -1,5 +1,5 @@
 
-# Please find and replace all instances of `xyz` with your project name.
+# Please find and replace all instances of `evmos` with your project name.
 
 ## Profile Set Up
 
@@ -7,7 +7,7 @@
 ----
 
 ```yml
-xyz:
+evmos:
   target: dev
   outputs:
     dev:
@@ -17,7 +17,7 @@ xyz:
       user: <USERNAME>
       password: <PASSWORD>
       region: <REGION>
-      database: xyz_DEV
+      database: evmos_DEV
       warehouse: <WAREHOUSE>
       schema: silver
       threads: 4
@@ -73,5 +73,5 @@ dbt run --var '{"UPDATE_SNOWFLAKE_TAGS":True}' -s models/core/core__fact_swaps.s
 
 ```
 select *
-from table(xyz.information_schema.tag_references('xyz.core.fact_blocks', 'table'));
+from table(evmos.information_schema.tag_references('evmos.core.fact_blocks', 'table'));
 ```

dbt_project.yml

@@ -1,14 +1,14 @@
 # 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: "xyz_models"
+name: "evmos_models"
 version: "1.0.0"
 config-version: 2
 
 require-dbt-version: ">=1.4.0"
 
 # This setting configures which "profile" dbt uses for this project.
-profile: "xyz"
+profile: "evmos"
 
 # These configurations specify where dbt should look for different types of files.
 # The `model-paths` config, for example, states that models in this project can be

macros/create_sps.sql

@@ -1,5 +1,5 @@
 {% macro create_sps() %}
-    {% if target.database == 'xyz' %}
+    {% if target.database == 'evmos' %}
         CREATE SCHEMA IF NOT EXISTS _internal;
         {{ sp_create_prod_clone('_internal') }};
     {% endif %}

macros/run_sp_create_prod_clone.sql

@@ -1,6 +1,6 @@
 {% macro run_sp_create_prod_clone() %}
 {% set clone_query %}
-call xyz._internal.create_prod_clone('xyz', 'xyz_dev', 'internal_dev');
+call evmos._internal.create_prod_clone('evmos', 'evmos_dev', 'internal_dev');
 {% endset %}
 
 {% do run_query(clone_query) %}

macros/tags/add_database_or_schema_tags.sql

@@ -1,7 +1,7 @@
 {% macro add_database_or_schema_tags() %}
     {{ set_database_tag_value(
         'BLOCKCHAIN_NAME',
-        'xyz'
+        'EVMOS'
     ) }}
       {{ set_database_tag_value(
         'BLOCKCHAIN_TYPE',

models/descriptions/__overview__.md

@@ -1,10 +1,10 @@
 {% docs __overview__ %}
 
-# Welcome to the Flipside Crypto xyz Models Documentation
+# Welcome to the Flipside Crypto EVMOS Models Documentation
 
 ## **What does this documentation cover?**
-The documentation included here details the design of the xyz
- 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/xyz-models/)
+The documentation included here details the design of the evmos
+ 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/evmos-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.
@@ -17,7 +17,7 @@ There is more information on how to use dbt docs in the last section of this doc
 
 **Click on the links below to jump to the documentation for each schema.**
 
-### Core Tables (`xyz`.`CORE`.`<table_name>`)
+### Core Tables (`evmos`.`CORE`.`<table_name>`)
 
 **Dimension Tables:**
 
@@ -33,8 +33,7 @@ There is more information on how to use dbt docs in the last section of this doc
 
 ## **Data Model Overview**
 
-The xyz
- models are built a few different ways, but the core fact tables are built using three layers of sql models: **bronze, silver, and gold (or core).**
+The evmos models are built a few different ways, but the core fact tables 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
@@ -68,7 +67,7 @@ Note that you can also right-click on models to interactively filter and explore
 - [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/xyz-models)
+- [Github](https://github.com/FlipsideCrypto/evmos-models)
 - [What is dbt?](https://docs.getdbt.com/docs/introduction)
 
 {% enddocs %}

models/sources.yml

@@ -2,7 +2,7 @@ version: 2
 
 sources:
   - name: crosschain
-    database: "{{ 'crosschain' if target.database == 'xyz' else 'crosschain_dev' }}"
+    database: "{{ 'crosschain' if target.database == 'evmos' else 'crosschain_dev' }}"
     schema: core
     tables:
       - name: dim_date_hours

profiles.yml

@@ -1,4 +1,4 @@
-xyz:
+evmos:
   target: dev
   outputs:
     dev: