📰 2024-02-16: Weekly Prophet!

[andrewhong5297]

This is your weekly summary of 35 PRs merged from 21 wizards. Great job everyone! 🎉
We had 52 added models 🟢 and 112 modified models 🟠 for 16 Sectors.

Sector	🔧 # PRs	🟢 # Added	🟠 # Modified	🧙 # Authors
dex	9	0	9	4
prices	7	1	9	7
models	1	0	1	1
_sector	21	44	29	10
strike	1	1	0	1
evms	1	0	17	1
lodestar	1	1	0	1
rollup_economics	2	0	2	2
addresses	1	1	1	1
base_sources	1	1	0	1
oneinch	1	0	1	1
zeroex	1	0	1	1
fluxfinance	1	1	0	1
balancer	1	0	1	1
chainlink	1	0	40	1
bebop	1	2	1	1

SECTOR: dex

toggle to see all model updates

MODEL: dex_info.sql

🟠 Modified by:

🔧 PR: #5325, Added Moonbase , Citadelswap and Autotronic dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-16
📝 Summary: In this SQL model, two rows were added to the temporary table. The first row represents a project called 'Moonbase' with corresponding values for name, marketplace type, and x_username. The second row represents a project called 'Citadelswap' with corresponding values for name, marketplace type, and x_username.

🔧 PR: #5325, Added sharkswap dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-15
📝 Summary: In this SQL model, a new row has been added to the temporary table. The row represents a project called 'SharkSwap' with the name 'SharkSwapDEX'. It is categorized as a direct marketplace type and associated with an x_username.

🔧 PR: #5325, add horizondex on base
🧙 Author: @pachecospig on 2024-02-15
📝 Summary: The model added a new row to the existing list of values. The new row includes the values 'horizondex', 'HorizonDex', 'Direct', and 'HorizonDex'.

🔧 PR: #5325, Added torus dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-14
📝 Summary: In the given SQL model, a new row has been added to the temporary table. The row represents a project named 'Torus' with attributes 'Direct' and 'torus_farm'.

🔧 PR: #5325, Added plantbaseswap dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-14
📝 Summary: The model added a new row to the existing list of values. The new row includes the values 'plantbaseswap', 'Plantbaseswap', 'Direct', and 'PlantBaseSwap'.

🔧 PR: #5325, Finalizing dex.trades_beta
🧙 Author: @Hosuke on 2024-02-13
📝 Summary: In this SQL model, there were some changes made to the values being inserted. The incorrect names '1inch Limit Order Protocol' and '0x API' were fixed by changing them to '1inch LOP' and 'zeroex', respectively. These changes ensure that the correct names are used for these entries in the database.

🔧 PR: #5325, Added solidly dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: In the given SQL model, a new row has been added to the temporary table. The row includes values for the columns 'project', 'name', 'marketplace_type', and 'x_username'. The added row represents a project named 'Solidly' with corresponding values for other columns.

🔧 PR: #5325, Added sobal dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: In this SQL model, a new row has been added to the temporary table. The row includes values for the columns 'project', 'name', 'marketplace_type', and 'x_username'. The added row represents a project called 'Sobal' with corresponding values for its name, marketplace type, and x_username.

🔧 PR: #5325, Added derpdex dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-12
📝 Summary: In the given SQL model, a new row has been added to the temporary table. The row includes values for the columns 'project', 'name', 'marketplace_type', and 'x_username'. The added row represents a project named 'DerpDex' with corresponding values for other columns.

SECTOR: prices

toggle to see all model updates

MODEL: prices_base_tokens.sql

🟠 Modified by:

🔧 PR: #5324, Add base tokens from coinpaprika
🧙 Author: @tiagofilipenunes on 2024-02-16
📝 Summary: The token symbols that were added or removed are: Added: TOSHI, DOGINME, PRIME, RSR, SDEX, TBTC,
MBS, ISKRA TOKEN (ISK), VELA TOKEN (VELA),
TOWER Token (TOWER), FRAME Token (FRAME),
OMNI CATS (OMNI), BASEX Coin(BSX),
FXDX Exchange(FXDX), ANY INU(AI),
BETSWIRL(BETS), MAID SWEEPERS(SWPRS),
MYSTCL(MYST) , OMNI404(O404) ,
SQUID GAME(SQUID) , SEAMLESS(SEAM)
USDM Mountain Protocol(USDM)
Xidoltech(XID) , FARLAUNCH(FAR)
Troves(TROVES) FREN PET
Fren Pet(FREN PET). BEXCHANGE(BEX).
DUCKY CITY EARN(DCE). GECKO(GECKO).
RAI Finance(SOFI). Overnight DAI+(DAI+).
RATSBASE(RATS). GAMER(GMR). Removed: DEGEN and DAI+.

🔧 PR: #5324, Update prices_base_tokens.sql
🧙 Author: @0xOuterGod on 2024-02-15
📝 Summary: The added token symbols are DEGEN, DAI+, USD+. The removed token symbol is AERO.

MODEL: prices_ethereum_tokens.sql

🟠 Modified by:

🔧 PR: #5327, Update prices_ethereum_tokens.sql to add USDe support
🧙 Author: @amin3m on 2024-02-15
📝 Summary: The added token symbols are: USDe

🔧 PR: #5327, Add missing LST and LRT prices
🧙 Author: @viniabussafi on 2024-02-12
📝 Summary: The added token symbols are GYD and EZETH. The removed token symbol is JBOT.

🔧 PR: #5327, update prices.usd with LRT token and USDC
🧙 Author: @GoodDataBadGuy on 2024-02-12
📝 Summary: The added token symbols are: ankrETH, swETH, mETH

🔧 PR: #5327, Update prices_ethereum_tokens.sql
🧙 Author: @lydiapuspita on 2024-02-12
📝 Summary: The token symbols that were added or removed are: JBOT, RBX, GYD, EZETH, MUBI, PEAS

MODEL: prices_trusted_tokens.sql

🟢 Added by:

🔧 PR: #5130, Add static price stability rank to enhance amount_usd calculation
🧙 Author: @Hosuke on 2024-02-13
📝 Summary: This SQL model creates a table that contains information about different blockchain symbols and their corresponding contract addresses. It enables data analysts to easily access and analyze this information for various purposes such as tracking token balances, monitoring transactions, or conducting market research.

MODEL: prices_arbitrum_tokens.sql

🟠 Modified by:

🔧 PR: #5329, Add missing LST and LRT prices
🧙 Author: @viniabussafi on 2024-02-12
📝 Summary: The token symbols that were added or removed are: CBETH, AETH

MODEL: prices_polygon_tokens.sql

🟠 Modified by:

🔧 PR: #5295, Add missing LST and LRT prices
🧙 Author: @viniabussafi on 2024-02-12
📝 Summary: The token symbols that were added or removed are: GTC, GMT, TEL

🔧 PR: #5295, update prices.usd with LRT token and USDC
🧙 Author: @GoodDataBadGuy on 2024-02-12
📝 Summary: The token symbols that were added or removed are: USDC.e, USDC

SECTOR: models

toggle to see all model updates

MODEL: tokens_ethereum_erc20.sql

🟠 Modified by:

🔧 PR: #5356, [EASY] Add missing tokens
🧙 Author: @harisang on 2024-02-16
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.

SECTOR: _sector

toggle to see all model updates

MODEL: dex_base_base_trades.sql

🟠 Modified by:

🔧 PR: #5325, Added Moonbase , Citadelswap and Autotronic dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-16
📝 Summary: In this SQL model, two references were added: 'moonbase_base_base_trades' and 'citadelswap_base_base_trades'. These references are included in the base_union common table expression.

🔧 PR: #5325, Added sharkswap dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-15
📝 Summary: In this diff, a reference to the model 'sharkswap_base_base_trades' was added. This reference is included in a list of other models that are being referenced.

🔧 PR: #5325, add horizondex on base
🧙 Author: @pachecospig on 2024-02-15
📝 Summary: The model added a reference to 'horizondex_base_base_trades'.

🔧 PR: #5325, Added torus dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-14
📝 Summary: In this diff, a reference to the model 'torus_base_base_trades' was added. This reference is included in a list of other models that are being referenced. The rest of the code remains unchanged.

🔧 PR: #5325, Added plantbaseswap dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-14
📝 Summary: In this diff, a reference to the model 'plantbaseswap_base_base_trades' was added.

🔧 PR: #5325, Added sobal dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: In this diff, a reference to the model 'sobal_base_base_trades' was added.

🔧 PR: #5325, Added derpdex dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-12
📝 Summary: In this diff, a reference to the model 'derpdex_base_base_trades' was added. This reference is included in a list of other models that are being referenced.

MODEL: autotronic_base_base_trades.sql

🟢 Added by:

🔧 PR: #5323, Added Moonbase , Citadelswap and Autotronic dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-16
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query Uniswap V2 trades. It pulls data from two sources, 'AutotronicPair_evt_Swap' and 'AutotronicFactory_evt_PairCreated', using the specified column name for pairs.

MODEL: citadelswap_base_base_trades.sql

🟢 Added by:

🔧 PR: #5323, Added Moonbase , Citadelswap and Autotronic dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-16
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the CitadelSwap platform. It pulls data from two sources, 'CitadelPair_evt_Swap' and 'CitadelFactory_evt_PairCreated', both located in the 'citadelswap_base' project of the blockchain.

MODEL: moonbase_base_base_trades.sql

🟢 Added by:

🔧 PR: #5323, Added Moonbase , Citadelswap and Autotronic dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-16
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query Uniswap trades on the Moonbase blockchain. It uses two source tables, 'Pair_evt_Swap' and 'UniswapFactory_evt_PairCreated', from the Moonbase_base project version 1.

MODEL: sharkswap_base_base_trades.sql

🟢 Added by:

🔧 PR: #5348, Added sharkswap dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-15
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Sharkswap platform. It pulls data from two sources, 'SharkswapPair_evt_Swap' and 'SharkswapFactory_evt_PairCreated', and includes a column named 'pair'.

MODEL: horizondex_base_base_trades.sql

🟢 Added by:

🔧 PR: #5319, add horizondex on base
🧙 Author: @pachecospig on 2024-02-15
📝 Summary: This SQL model creates a table that extracts data from two sources, 'horizondex_base' and 'Factory_evt_PoolCreated'. It selects specific columns from these sources and performs calculations on them. The resulting table includes information such as blockchain, project version, block date and time, token amounts bought and sold, addresses of the tokens involved in the transaction (bought/sold), taker/maker details, project contract address, transaction hash,and event index. This model enables data analysts to analyze trading activity on the Horizondex platform.

MODEL: dex_base_trades.sql

🟠 Modified by:

🔧 PR: #5319, add horizondex on base
🧙 Author: @pachecospig on 2024-02-15
📝 Summary: In this diff, the references to three base trade models (dex_optimism_base_trades, dex_polygon_base_trades, and dex_zksync_base_trades) were removed.

MODEL: dex_trades_beta.sql

🟠 Modified by:

🔧 PR: #5130, add horizondex on base
🧙 Author: @pachecospig on 2024-02-15
📝 Summary: The model is using a set variable called 'as_is_models' which includes two referenced models: 'oneinch_lop_own_trades' and 'zeroex_native_trades'. The line starting with '-' indicates that the reference to the model 'zeroex_native_trades' has been removed. Additionally, there is a common table expression (CTE) named 'curve' being defined.

🔧 PR: #5130, Finalizing dex.trades_beta
🧙 Author: @Hosuke on 2024-02-13
📝 Summary: The main logic added in this SQL model is the inclusion of existing dbt lineages for specific projects. These projects are 'oneinch_lop_own_trades' and 'zeroex_native_trades'. The model also includes a new CTE called 'as_is_dexs' which selects data from these existing models based on certain conditions. Finally, there is a loop that performs a UNION ALL operation to combine the selected data from multiple CTEs including 'curve', 'as_is_dexs', and 'dexs'.

🔧 PR: #5130, Add static price stability rank to enhance amount_usd calculation
🧙 Author: @Hosuke on 2024-02-13
📝 Summary: The main logic added in this diff is the removal of the 'prices_model' source from the 'curve' common table expression (CTE). The CTE now only includes references to a base trades table and an ERC20 tokens model. Additionally, there is a filter applied to exclude any projects with the name 'curve'.

MODEL: contracts_contract_creator_address_list.sql

🟠 Modified by:

🔧 PR: #5338, Add creator_address to contracts_contract_creator_address_list.sql
🧙 Author: @Hirangi5 on 2024-02-15
📝 Summary: In this SQL model, several addresses and corresponding names were added to the 'curated_list' CTE. Additionally, a left join was made between the 'filtered_list' table and another table called 'contracts_project_name_mappings'. The join condition was modified to compare the lowercase values of two columns.

MODEL: rabbithole_arbitrum_rewards.sql

🟠 Modified by:

🔧 PR: #5351, rabbithole > boost schema
🧙 Author: @0xRobin on 2024-02-15
📝 Summary: The main logic of the diff is that the source for QuestFactory_evt_MintFeePaid in the rabbithole_referral_rewards model has been changed from 'rabbithole_arbitrum' to 'boost_arbitrum'.

MODEL: rabbithole_base_rewards.sql

🟠 Modified by:

🔧 PR: #5351, rabbithole > boost schema
🧙 Author: @0xRobin on 2024-02-15
📝 Summary: The main logic change in this SQL model is the source of the QuestFactory_evt_MintFeePaid data. Previously, it was sourced from 'rabbithole_base', but now it is sourced from 'boost_base'. This change affects the blockchain parameter value for the rabbithole_referral_rewards model.

MODEL: rabbithole_optimism_rewards.sql

🟠 Modified by:

🔧 PR: #5351, rabbithole > boost schema
🧙 Author: @0xRobin on 2024-02-15
📝 Summary: The main logic of the diff is that the source for QuestFactory_evt_MintFeePaid in the rabbithole_referral_rewards model has been changed from 'rabbithole_optimism' to 'boost_optimism'.

MODEL: rabbithole_polygon_rewards.sql

🟠 Modified by:

🔧 PR: #5351, rabbithole > boost schema
🧙 Author: @0xRobin on 2024-02-15
📝 Summary: The main logic change in this SQL model is the source of the QuestFactory_evt_MintFeePaid table. It was originally sourced from 'rabbithole_polygon' but has been changed to 'boost_polygon'. The rest of the model remains unchanged.

MODEL: lending_ethereum_base_borrow.sql

🟠 Modified by:

🔧 PR: #5328, Add strike to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: The model added a reference to 'strike_ethereum_base_borrow' and removed the reference to 'fluxfinance_ethereum_base_borrow'.

🔧 PR: #5328, Add fluxfinance to lending
🧙 Author: @tomfutago on 2024-02-13
📝 Summary: In this diff, the model is updated to include a new reference to 'fluxfinance_ethereum_base_borrow' while removing the reference to 'spark_ethereum_base_borrow'.

MODEL: lending_ethereum_base_supply.sql

🟠 Modified by:

🔧 PR: #5328, Add strike to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: In this SQL model, the reference to 'fluxfinance_ethereum_base_supply' was removed and two new references were added: 'fluxfinance_ethereum_base_supply' and 'strike_ethereum_base_supply'.

🔧 PR: #5328, Add fluxfinance to lending
🧙 Author: @tomfutago on 2024-02-13
📝 Summary: In this diff, the model is updated to include a new reference to 'fluxfinance_ethereum_base_supply' while removing the reference to 'spark_ethereum_base_supply'.

MODEL: inscription_scroll_all.sql

🟢 Added by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: This SQL model creates a new table called 'inscription_all' that enables data analysts to analyze blockchain transactions. It uses the 'scroll' blockchain and pulls transaction data from the specified source. The first inscription block is set to 386653, which corresponds to October 29, 2023 at 08:30.

MODEL: inscription_scroll_deploys.sql

🟢 Added by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: This SQL model creates and enables the deployment of inscriptions for a specific blockchain. It takes in all inscriptions from a given blockchain and deploys them accordingly.

MODEL: inscription_all.sql

🟠 Modified by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a reference to the 'inscription_scroll_all' table was added to the list of tables being included in the model.

MODEL: inscription_deploys.sql

🟠 Modified by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a reference to the model 'inscription_scroll_deploys' was added. This means that the SQL model now includes a dependency on 'inscription_scroll_deploys'.

MODEL: inscription_mints.sql

🟠 Modified by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a reference to the model 'inscription_scroll_mints' was added. This means that the SQL model now includes a reference to another table called 'inscription_scroll_mints'.

MODEL: inscription_scroll_mints.sql

🟢 Added by:

🔧 PR: #5341, Add Scroll to inscriptions tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: This SQL model creates and enables the ability to mint inscriptions for a specific blockchain. It takes in all inscriptions from the specified blockchain and performs the necessary operations to mint new ones.

MODEL: lending_arbitrum_base_borrow.sql

🟠 Modified by:

🔧 PR: #5344, Add lodestar to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: In this diff, the model 'radiant_arbitrum_base_borrow' was removed from the list of models and three new models were added: 'lodestar_v0_arbitrum_base_borrow', 'lodestar_v1_arbitrum_base_borrow', and 'radiant_arbitrum_base_borrow'.

MODEL: lending_arbitrum_base_supply.sql

🟠 Modified by:

🔧 PR: #5344, Add lodestar to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: In this SQL model, the reference to 'radiant_arbitrum_base_supply' was removed and references to 'lodestar_v0_arbitrum_base_supply' and 'lodestar_v1_arbitrum_base_supply' were added.

MODEL: dex_optimism_base_trades.sql

🟠 Modified by:

🔧 PR: #5335, Added gridex dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-14
📝 Summary: In this diff, a reference to the model 'gridex_optimism_base_trades' was added.

🔧 PR: #5335, Added solidly dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: The model added a reference to 'solidly_v3_optimism_base_trades' in addition to the existing references to 'chainhop_optimism_base_trades', 'curvefi_optimism_base_trades', and 'rubicon_optimism_base_trades'.

MODEL: gridex_optimism_base_trades.sql

🟢 Added by:

🔧 PR: #5339, Added gridex dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-14
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the Uniswap decentralized exchange. The table includes information about the blockchain (Optimism), project (Gridex), and version, as well as columns for taker, maker, pair, and other optional columns.

MODEL: eas_arbitrum_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestation_details' with columns for blockchain, project, and version. It enables data analysts to store and analyze attestation details specific to the 'arbitrum' blockchain in the 'eas' project with version 1.

MODEL: eas_arbitrum_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestations' that enables data analysts to store and analyze attestation data from the Arbitrum blockchain for the EAS project. It includes information such as the blockchain type, project name, version, and decoded project name.

MODEL: eas_arbitrum_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates and enables the 'eas_schema_details' table, which provides information about the blockchain, project, and version details for the EAS schema. This table can be used by data analysts to track and analyze changes in the EAS schema over time.

MODEL: eas_arbitrum_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a schema called 'eas_schemas' with the following attributes: blockchain (set to 'arbitrum'), project (set to 'eas'), version (set to '1'), decoded_project_name (set to 'arbitrum_eas'), and uid_column_name (set to 'uuid'). It enables data analysts to organize and manage data related to the Arbitrum EAS project using these specified attributes.

MODEL: eas_base_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestation_details' in the database. It enables data analysts to store and analyze attestation details related to the EAS project on the base blockchain. The version of this model is 1.

MODEL: eas_base_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestations' that enables data analysts to store and analyze attestation data related to the base blockchain project. The table includes information such as the project version, decoded project name, and other relevant details for analysis.

MODEL: eas_base_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates and enables the 'eas_schema_details' table in the 'base' blockchain for the 'eas' project. It provides schema details such as version number.

MODEL: eas_base_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a schema called 'eas_schemas' in the 'base' blockchain project. It is version 1 and has a decoded project name of 'base_eas'. This model enables data analysts to organize and manage their data within this specific schema for analysis purposes.

MODEL: eas_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a union of multiple tables (eas_arbitrum_attestation_details, eas_base_attestation_details, eas_ethereum_attestation_details, eas_optimism_attestation_details, and eas_polygon_attestation_details) to retrieve attestation details from different blockchains. It selects various columns such as blockchain, project, version, schema UID, attestion UID, ordinality, data type, field name etc. The model also includes an optional incremental predicate based on the block time column. This enables data analysts to easily query and analyze attestion details across different blockchains in a unified manner.

MODEL: eas_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a union of multiple tables related to attestations on different blockchains. It retrieves various attributes such as blockchain, project, version, attestation details (attester, recipient), request information (is_revocable), raw data and value, expiration and revocation times, attestation state (revoked or not), contract address and transaction details. This model enables data analysts to analyze and compare attestations across different blockchains in a unified manner.

MODEL: eas_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a union of multiple schema details tables for different blockchains (Arbitrum, Ethereum, Optimism, and Polygon). It enables data analysts to query information such as blockchain type, project name, version number, schema UID, ordinality value of the field in the schema definition table. Additionally it provides data type and field name details along with block number and time stamp information. Transaction hash and event index are also included in the output.

MODEL: eas_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a union of multiple schemas related to different blockchains (Arbitrum, Ethereum, Optimism, and Polygon). It selects various columns such as blockchain type, project details, version information, schema details like UID and array representation. Other fields include revocability status of the schema contract address used in the blockchain transaction. The model also includes filtering based on incremental predicate for block time. This enables data analysts to query and analyze data from different blockchain schemas in a unified manner.

MODEL: eas_ethereum_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestation_details' that enables data analysts to store and analyze attestation details related to the Ethereum blockchain for the EAS project. The table includes information such as blockchain type, project name, and version number.

MODEL: eas_ethereum_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestations' that enables data analysts to store and analyze attestation data related to the Ethereum blockchain. The table includes information about the project, version, and decoded project name for each attestation.

MODEL: eas_ethereum_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates and enables a schema called 'eas_schema_details' for data analysts. It is specific to the Ethereum blockchain and the EAS project, with version 1.

MODEL: eas_ethereum_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a schema called 'eas_schemas' for the Ethereum blockchain. It is specifically designed for the Ethereum Attestation Service (EAS) project and version 1. This schema enables data analysts to work with and analyze data related to attestation on the Ethereum blockchain within the EAS project.

MODEL: eas_optimism_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestation_details' with columns for blockchain, project, and version. It enables data analysts to store and analyze attestation details specific to the Optimism blockchain in the EAS project.

MODEL: eas_optimism_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestations' that enables data analysts to store and analyze attestation data from the Optimism blockchain for the EAS project. The table includes information such as the version of the project and decoded project name.

MODEL: eas_optimism_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates and enables a schema called 'eas_schema_details' with the specified blockchain, project, and version details. It provides a standardized structure for storing information related to the EAS (Ethereum Alarm Service) on the Optimism blockchain.

MODEL: eas_optimism_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a schema called 'eas_schemas' with the following attributes: blockchain (set to 'optimism'), project (set to 'eas'), version (set to '1'), and decoded_project_name (set to 'attestationstation_v1'). It enables data analysts to organize and query data related to the EAS project on the Optimism blockchain.

MODEL: eas_polygon_attestation_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called eas_attestation_details that enables data analysts to store and analyze attestation details for the EAS project on the Polygon blockchain. The version of this model is 1.

MODEL: eas_polygon_attestations.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table called 'eas_attestations' that enables data analysts to store and analyze attestation data related to the Polygon blockchain. The table includes columns for blockchain, project, version, decoded project name, and schema column name.

MODEL: eas_polygon_schema_details.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates and enables a schema called 'eas_schema_details' with the specified details. It is designed for use in analyzing data related to the Polygon blockchain within the EAS project, version 1.

MODEL: eas_polygon_schemas.sql

🟢 Added by:

🔧 PR: #5258, Add EAS
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a schema called 'eas_schemas' with the following attributes: blockchain (set to 'polygon'), project (set to 'eas'), version (set to '1'), and decoded_project_name (set to 'polygon_eas'). It enables data analysts to organize and query data related to the Polygon EAS project on the Polygon blockchain.

MODEL: tokens_base_transfers.sql

🟠 Modified by:

🔧 PR: #5346, prep cross-chain base_transfers spell
🧙 Author: @jeff-dude on 2024-02-14
📝 Summary: The main logic added in this SQL model is the inclusion of two new references: 'tokens_bnb_base_transfers' and 'tokens_polygon_base_transfers'. Additionally, there is a change in the incremental predicate from 'block_time' to 'block_date'.

MODEL: torus_base_base_trades.sql

🟢 Added by:

🔧 PR: #5334, Added torus dex to dex.trades
🧙 Author: @ARDev097 on 2024-02-14
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query Uniswap V2 trades. It pulls data from the 'TorusPair_evt_Swap' and 'TorusFactory_evt_PairCreated' sources in the 'torus_base' project, using the specified blockchain, project, and version parameters. The resulting table includes information about pairs involved in swaps under the column name 'pair'.

MODEL: plantbaseswap_base_base_trades.sql

🟢 Added by:

🔧 PR: #5318, Added plantbaseswap dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-14
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the Uniswap V2 decentralized exchange. It pulls data from two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', in the project 'plantbaseswap'. The model is specifically designed for blockchain analysis on the base network.

MODEL: solidly_v3_optimism_base_trades.sql

🟢 Added by:

🔧 PR: #5335, Added solidly dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the Uniswap V3 protocol. The trades are specific to the Optimism blockchain and sourced from the 'SolidlyV3Pool_evt_Swap' and 'SolidlyV3Factory_evt_PoolCreated' events in the Solidly V3 Optimism project.

MODEL: sobal_base_base_trades.sql

🟢 Added by:

🔧 PR: #5317, Added sobal dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-13
📝 Summary: This SQL model creates a view that combines data from the sobal_base.Vault_evt_Swap table. It selects specific columns from the table and renames them accordingly. The resulting view includes information such as blockchain, project, version, block month and date, block time and number, token amounts bought and sold, addresses of tokens bought and sold, taker/maker details,and transaction hash. This enables data analysts to easily access this consolidated information for analysis purposes.

MODEL: tokens_base_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a new table called 'balances_enrich' by enriching the existing 'tokens_base_base_balances_daily' table. It enables data analysts to have access to enriched balance information for the base blockchain on a daily basis.

MODEL: tokens_base_base_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a table called 'balances_daily' that is based on the source tables 'tokens_base' and 'balances_base_0001'. It enables data analysts to analyze daily balances for tokens.

MODEL: tokens_ethereum_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a new table called 'balances_enrich' by enriching the data from an existing table called 'tokens_ethereum_base_balances_daily'. It enables data analysts to analyze daily balances for Ethereum tokens on the blockchain.

MODEL: tokens_ethereum_base_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a table called 'balances_daily' that is based on the source table 'balances_ethereum_0004' from the 'tokens_ethereum' database. It enables data analysts to analyze daily balances for Ethereum tokens.

MODEL: tokens_optimism_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a new table called 'balances_enrich' by enriching the data from the 'tokens_optimism_base_balances_daily' table. It focuses on the blockchain 'optimism' and provides daily balances information. This model enables data analysts to analyze enriched balance data for daily transactions on the optimism blockchain.

MODEL: tokens_optimism_base_balances_daily.sql

🟢 Added by:

🔧 PR: #5290, Balances daily
🧙 Author: @aalan3 on 2024-02-13
📝 Summary: This SQL model creates a table called 'balances_daily' that is based on the source table 'balances_optimism_0001' from the database 'tokens_optimism'. It enables data analysts to analyze daily balances for tokens in the Optimism network.

MODEL: derpdex_base_base_trades.sql

🟢 Added by:

🔧 PR: #5325, Added derpdex dex to dex.trades
🧙 Author: @Jason4276 on 2024-02-12
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze and query Uniswap V3 trades. It pulls data from two sources, 'Pair_evt_Swap' and 'Factory_evt_PoolCreated', in the derpdex_base project on the base blockchain.

MODEL: tokens_base_balances.sql

🟠 Modified by:

🔧 PR: #5316, Make balances public for Ethereum Optimism and Base
🧙 Author: @aalan3 on 2024-02-12
📝 Summary: The diff of the SQL model shows that some lines were added and removed. The main logic of what was added or removed cannot be determined without seeing the actual content of the diff. Please provide the specific content so that I can summarize it for you.

SECTOR: strike

toggle to see all model updates

MODEL: strike_lending_ethereum_ctokens.sql

🟢 Added by:

🔧 PR: #5336, Add strike to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table that includes the asset symbol, ctoken address, and asset address for various assets such as WBTC, ETH, USDC, etc. This enables data analysts to easily access and analyze information about these assets in their queries.

SECTOR: evms

toggle to see all model updates

MODEL: evms_blocks.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' is added to the SQL model. This source is used to retrieve data from the 'blocks' table in the 'scroll' database.

MODEL: evms_contracts.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' with the table name 'contracts' was added to the existing list of sources ('goerli', 'zksync', and 'zora'). The SELECT statement remains unchanged.

MODEL: evms_creation_traces.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: The line that starts with '+' indicates that a new source called 'scroll' has been added to the SQL model. This source is being used in the SELECT statement along with three other existing sources ('goerli', 'zksync', and 'zora'). The '*' symbol suggests that all columns from these sources are being selected.

MODEL: evms_erc1155_approvalsforall.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' with the event 'evt_ApprovalForAll' has been added to the SQL model.

MODEL: evms_erc1155_transfersbatch.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: A new source called 'scroll' with the table 'erc1155_scroll' and event 'evt_transferbatch' was added to the SQL model.

MODEL: evms_erc1155_transferssingle.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' is added to the SQL model. This source is used to retrieve data from the 'erc1155_scroll' table using the event type 'evt_transfersingle'. The rest of the code remains unchanged.

MODEL: evms_erc20_approvals.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' with the event type 'evt_approval' is added to the SQL model. This source is being selected along with three other existing sources ('goerli', 'zksync', and 'zora').

MODEL: evms_erc20_transfers.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source named 'scroll' with the event type 'evt_transfer' is added to the existing list of sources ('goerli', 'zksync', and 'zora'). The SELECT statement remains unchanged.

MODEL: evms_erc721_approvals.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' with the event 'evt_Approval' from the table 'erc721_scroll' is added to an existing SQL model.

MODEL: evms_erc721_approvalsforall.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this SQL model, a new source called 'scroll' with the event 'evt_ApprovalForAll' has been added. The existing sources include 'goerli', 'zksync', and 'zora'. The SELECT statement remains unchanged.

MODEL: evms_erc721_transfers.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' with the event type 'evt_transfer' is added to the existing list of sources ('goerli', 'zksync', and 'zora'). The SELECT statement remains unchanged.

MODEL: evms_info.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: A new row was added to the SQL model. The row represents a cryptocurrency called 'Scroll' with various attributes such as name, layer, rollup type, symbol, contract address, explorer URL, and timestamp.

MODEL: evms_logs.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: In this diff, a new source called 'scroll' is added to the list of sources in the SQL model.

MODEL: evms_logs_decoded.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: The line that was added includes a new source called 'scroll' with the table name 'logs_decoded'. This new source is included in the list of sources being selected from.

MODEL: evms_traces.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: The line that was added includes a new source called 'scroll' with the table name 'traces'.

MODEL: evms_traces_decoded.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: The model added a new data source called 'scroll' with the table 'traces_decoded'.

MODEL: evms_transactions.sql

🟠 Modified by:

🔧 PR: #5340, Add Scroll to evms tables
🧙 Author: @hildobby on 2024-02-14
📝 Summary: A new source called 'scroll' with the table 'transactions' was added to the SQL model.

SECTOR: lodestar

toggle to see all model updates

MODEL: lodestar_arbitrum_ctokens.sql

🟢 Added by:

🔧 PR: #5344, Add lodestar to lending
🧙 Author: @tomfutago on 2024-02-14
📝 Summary: This SQL model creates a table that includes the asset symbol, version, ctoken address, and asset address for various tokens. It enables data analysts to easily access this information for analysis and reporting purposes.

SECTOR: rollup_economics

toggle to see all model updates

MODEL: l2_revenue.sql

🟠 Modified by:

🔧 PR: #5309, Rollup Econ - Add Scroll Revenue
🧙 Author: @Jam516 on 2024-02-14
📝 Summary: The added logic includes grouping the result by two columns, 'day' and 'name', and performing a UNION ALL operation. It also calculates the l2_rev and l2_rev_usd values based on certain conditions using CASE statements. Additionally, it joins two sources ('scroll.transactions' and 'prices.usd') based on specific criteria. The WHERE clause includes conditional statements for incremental updates as well as filtering by block_time values.

MODEL: l1_data_fees.sql

🟠 Modified by:

🔧 PR: #5293, Rollup Econ - Handle for Multiple OP Versions
🧙 Author: @MSilb7 on 2024-02-14
📝 Summary: The main logic added in this SQL model is to retrieve transaction data from the 'ethereum.transactions' table. The SELECT statement includes various columns such as protocol_name, block_number, hash, gas_spent, gas_spent_usd, data_length, gas_used and calldata_gas_used. The transactions are joined with two different tables ('addresses_ethereum_optimism_batchinbox_combinations' and 'addresses_ethereum_optimism_outputoracle_combinations') based on the sender and receiver addresses. Additionally, a join is made with the 'prices.usd' table to calculate the USD value of gas spent. Filters are applied for block_time and minute values to limit the results.

SECTOR: addresses

toggle to see all model updates

MODEL: [ad