📰 2024-04-26: Weekly Prophet!

[andrewhong5297]

This is your weekly summary of 27 PRs merged from 16 wizards. Great job everyone! 🎉
We had 64 added models 🟢 and 77 modified models 🟠 for 13 Sectors.

Sector	🔧 # PRs	🟢 # Added	🟠 # Modified	🧙 # Authors
dex	1	6	3	1
prices	6	0	6	5
yield_yak	1	10	1	1
cex	4	17	41	2
_sector	7	10	8	6
safe	1	4	4	1
chainlink	1	7	9	1
nexusmutual	1	3	0	1
models	2	0	2	1
sol_gun	1	1	0	1
addresses_events	1	4	2	1
rollup_economics	1	0	1	1
_base_sources	1	2	0	1

SECTOR: dex

toggle to see all model updates

MODEL: dex_scroll_atomic_arbitrages.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table that calculates atomic arbitrage opportunities within a decentralized exchange (DEX) on the specified blockchain. It enables data analysts to analyze and identify potential arbitrage opportunities between different tokens traded on the DEX, providing insights into trading strategies and market inefficiencies.

MODEL: dex_zora_atomic_arbitrages.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This dbt SQL model creates a table that calculates atomic arbitrage opportunities on the specified blockchain. It enables data analysts to analyze and identify potential arbitrage opportunities within transactions on the Zora blockchain.

MODEL: dex_scroll_sandwiched.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a new table that enables data analysts to analyze sandwiched transactions on a specific blockchain, such as 'scroll'. It references transaction data from the source and populates the sandwiches table for further analysis.

MODEL: dex_scroll_sandwiches.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This SQL model creates a new table that enables data analysts to analyze sandwich trading patterns on a decentralized exchange (DEX) for a specific blockchain, such as 'scroll'. The model includes transaction data sourced from the specified blockchain to provide insights into DEX trading activities related to sandwich trades.

MODEL: dex_zora_sandwiched.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This SQL model creates a view that calculates sandwich attacks on the Zora blockchain DEX. It enables data analysts to analyze and monitor potential instances of sandwich attacks within the Zora blockchain transactions.

MODEL: dex_zora_sandwiches.sql

🟢 Added by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This SQL model creates a view that enables data analysts to analyze sandwich trading patterns on the Zora blockchain by pulling transaction data from the source table.

MODEL: dex_atomic_arbitrages.sql

🟠 Modified by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two references to dbt models were added: 'dex_scroll_atomic_arbitrages' and 'dex_zora_atomic_arbitrages'.

MODEL: dex_sandwiched.sql

🟠 Modified by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two references were added in the dbt SQL model: 'dex_scroll_sandwiched' and 'dex_zora_sandwiched'.

MODEL: dex_sandwiches.sql

🟠 Modified by:

🔧 PR: #5814, MEV Spells for Scroll & Zora
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two new references to models dex_scroll_sandwiches and dex_zora_sandwiches were added in the SQL query.

SECTOR: prices

toggle to see all model updates

MODEL: prices_ethereum_tokens.sql

🟠 Modified by:

🔧 PR: #5817, Update prices_ethereum_tokens.sql
🧙 Author: @lydiapuspita on 2024-04-25
📝 Summary: OMNI

🔧 PR: #5817, Added SAFE token to ethereum price feed
🧙 Author: @safeintern on 2024-04-24
📝 Summary: The token symbols that were added or removed are: RSWETH, SAFE

🔧 PR: #5817, Add RSWETH to prices.usd
🧙 Author: @viniabussafi on 2024-04-23
📝 Summary: The token symbols that were added or removed are: TRUMP, RSWETH

MODEL: prices_fantom_tokens.sql

🟠 Modified by:

🔧 PR: #5826, fantom prices: remove bad price feed
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: The token symbols that were removed are: SEX

MODEL: prices_gnosis_tokens.sql

🟠 Modified by:

🔧 PR: #5794, added 4 tokens : OLAS, sDAI, stETH and EURe - on gnosis chain
🧙 Author: @PoloX2021 on 2024-04-23
📝 Summary: The token symbols that were added are: WSTETH, SDAI, EURe, OLAS, stETH

MODEL: prices_native_tokens.sql

🟠 Modified by:

🔧 PR: #5803, Update prices_native_tokens.sql
🧙 Author: @lydiapuspita on 2024-04-23
📝 Summary: The token symbols that were added are: ROSE, SAGA, KAS, EGLD, NTRN, FLR and AR.

SECTOR: yield_yak

toggle to see all model updates

MODEL: yield_yak_arbitrum_deposits.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This SQL model creates a dataset that focuses on yield yak deposits and withdrawals specifically for the Arbitrum blockchain. It enables data analysts to analyze deposit events within the Yield Yak platform on the Arbitrum network.

MODEL: yield_yak_arbitrum_reinvests.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This SQL model creates a table that calculates and tracks the reinvestments of yield generated by Yak Finance on the Arbitrum blockchain. It enables data analysts to analyze and monitor the reinvestment activities within Yak Finance's ecosystem on Arbitrum.

MODEL: yield_yak_arbitrum_withdraws.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This model creates a table that captures yield yak deposits and withdrawals specifically for the Arbitrum blockchain, focusing on events where withdrawals occur. This enables data analysts to track and analyze deposit and withdrawal activities related to yield yak on the Arbitrum blockchain.

MODEL: yield_yak_avalanche_c_deposits.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This SQL model creates a table that yields data on yak deposits and withdrawals specifically for the Avalanche C blockchain. It enables data analysts to analyze and track deposit events related to yaks on the specified blockchain.

MODEL: yield_yak_avalanche_c_reinvests.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This SQL model creates a table that calculates and tracks reinvestments in yield yak on the Avalanche C blockchain. It enables data analysts to analyze and monitor the reinvestment activity within this specific blockchain ecosystem.

MODEL: yield_yak_avalanche_c_withdraws.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This SQL model creates a table that tracks yield yak deposits and withdrawals specifically for the Avalanche C blockchain. It enables data analysts to analyze and monitor withdrawal events related to yield yak on the specified blockchain.

MODEL: yield_yak_balances.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This model creates a unified view of yield data from multiple sources by combining balance information from different blockchain contracts. It enables data analysts to easily query and analyze deposit token balances over time across various blockchain platforms.

MODEL: yield_yak_deposits.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This model combines data from two different yield yak deposit tables, enabling data analysts to analyze and compare deposit information across multiple blockchain networks. The model allows for a comprehensive view of deposit amounts, user addresses, transaction details, and other relevant information for further analysis and insights.

MODEL: yield_yak_reinvests.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This model combines data from two different tables related to yield farming on Avalanche and Arbitrum blockchains. It enables data analysts to analyze reinvestment activities, including details such as transaction hashes, block information, deposit amounts, APY (Annual Percentage Yield), and other relevant metrics across both blockchain networks in a single query result.

MODEL: yield_yak_withdraws.sql

🟢 Added by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: This model combines data from two different yield yak withdraw tables into one unified dataset. It allows data analysts to easily query and analyze withdrawal information across multiple blockchain platforms, including details such as transaction hashes, block numbers, user addresses, and withdrawal amounts.

MODEL: yield_yak_avalanche_c_sources.yml

🟠 Modified by:

🔧 PR: #5737, Added balances for Yield Yak vaults
🧙 Author: @yy-analytics on 2024-04-25
📝 Summary: [changes too large] The model yield_yak_avalanche_c_sources.yml was modified.

SECTOR: cex

toggle to see all model updates

MODEL: cex_arbitrum_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters including references to cex_evms_addresses, the blockchain variable, and a source function for traces. The SQL query that selected specific columns from the table was removed.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable defining the blockchain as 'arbitrum' and a macro call 'cex_evms' with specific parameters. Added a SELECT statement to query data from the 'cex_evms_addresses' table, selecting specific columns and renaming one column.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters including references to cex_evms_addresses table and a source for traces based on the specified blockchain. The previous SQL query selecting specific columns from cex_evms_addresses was removed. A variable blockchain is set to 'arbitrum'.

MODEL: cex_avalanche_c_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. Removed a SELECT statement that hardcoded values for blockchain, address, cex_name, distinct_name, added_by, and added_date.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable defining the blockchain, and a macro call cex_evms with specific parameters. Added a SELECT statement to query data from the cex_evms_addresses table, selecting specific columns and assigning 'avalanche_c' as the blockchain value.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: A parameter blockchain is set to 'avalanche_c'. The SQL query selecting specific columns from a table is replaced with a call to the cex_evms macro, passing in parameters such as cex_addresses, blockchain, and traces.

MODEL: cex_base_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called using the reference to the model 'cex_evms_addresses' and other specified parameters.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call that passed parameters. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table with an additional column for the blockchain value set as 'base'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms that references the model cex_evms_addresses. The macro takes parameters for cex addresses, blockchain type, and traces source.

MODEL: cex_bnb_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. A variable named blockchain is set to 'bnb'.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call that passed parameters. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table with hardcoded values for 'blockchain'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. A variable named blockchain is set to 'bnb'.

MODEL: cex_celo_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms that references the model cex_evms_addresses. The macro takes parameters for cex addresses, blockchain type, and traces source. Removed a select statement that hardcoded 'celo' as the blockchain value and selected specific columns from the table.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable for 'blockchain' and a macro call to 'cex_evms'. Added a SELECT statement querying data from the model reference 'cex_evms_addresses', selecting specific columns along with the hardcoded value 'celo' as blockchain.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms that references the model cex_evms_addresses. The macro takes parameters for cex addresses, blockchain type, and traces source. Removed a select statement that hardcoded 'celo' as the blockchain value and selected specific columns from the table.

MODEL: cex_ethereum_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: A variable for 'blockchain' is set to 'ethereum'. The SELECT statement was removed and replaced with a call to the cex_evms macro, passing in references to cex_evms_addresses, the blockchain variable, and traces sourced from the specified blockchain.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call that passed parameters. Added a SELECT statement to query data from the 'cex_evms_addresses' table with specific columns selected and hardcoded value for blockchain.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: A variable blockchain is set to 'ethereum'. The SQL query selecting specific columns from a table is replaced with a call to the cex_evms macro, passing in parameters such as cex_addresses, blockchain, and traces.

MODEL: cex_fantom_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. Removed a select statement that hardcoded values for blockchain, address, cex_name, distinct_name, added_by, and added_date.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable defining the blockchain as 'fantom' and a macro call 'cex_evms' with specific parameters. Added a SELECT statement to query data from the 'cex_evms_addresses' table, selecting specific columns along with the 'fantom' blockchain value.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. A variable named blockchain is set to 'fantom'.

MODEL: cex_gnosis_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters for cex_addresses, blockchain, and traces. The macro is used to select data from the table specified in the parameter, along with additional columns related to blockchain information.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call related to 'gnosis' blockchain. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table for the 'gnosis' blockchain.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'. A variable named blockchain is set to 'gnosis'.

MODEL: cex_linea_addresses.sql

🟢 Added by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: This model creates a dbt table that enables data analysts to analyze centralized exchange (CEX) Ethereum Virtual Machines (EVMs) by joining CEX addresses with trace data from the specified blockchain.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: This model creates a dbt table that enables data analysts to analyze centralized exchange (CEX) Ethereum Virtual Machines (EVMs) by pulling data from specified CEX addresses and blockchain traces.

MODEL: cex_optimism_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms that references the model cex_evms_addresses. The macro includes parameters for blockchain and traces, with the value of blockchain being set to 'optimism'.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call that passed parameters to the macro. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table, with an additional column for the blockchain value being set as 'optimism'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters for cex_addresses, blockchain, and traces. The macro is used to select data from the table specified in the parameter, along with additional columns related to blockchain information.

MODEL: cex_polygon_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: A variable for 'blockchain' is set to 'polygon'. The SELECT statement was replaced with a call to the cex_evms macro, passing in references to cex_evms_addresses, the blockchain variable, and traces sourced from the specified blockchain.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a Jinja variable assignment and a function call, and replaced it with a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table for the blockchain 'polygon'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters for cex addresses, blockchain type, and traces source. Removed a select statement that hardcoded the blockchain value and selected specific columns from the table.

MODEL: cex_scroll_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters including cex_addresses, blockchain, and traces. The macro is called using the reference to the model 'cex_evms_addresses' and other specified variables.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call with parameters. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table, including the hardcoded value 'scroll' for the blockchain column.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'.

MODEL: cex_zkevm_addresses.sql

🟢 Added by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: This SQL model creates a table that provides information on CEX (Centralized Exchange) addresses for a specific blockchain. It enables data analysts to analyze and track activities related to CEX addresses on the specified blockchain, using trace data as the source of information.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: This model creates a table that enables data analysts to analyze Centralized Exchange (CEX) Ethereum Virtual Machines (EVMs) by linking CEX addresses with blockchain traces for the specified EVM type.

MODEL: cex_zksync_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters including cex_addresses, blockchain, and traces. The macro is used to select data from the table 'cex_evms_addresses' based on the specified blockchain.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable defining the blockchain as 'zksync' and a macro call to generate CEX EVMS data. Added a SELECT statement to retrieve specific columns from the 'cex_evms_addresses' table, with an additional column for the blockchain value set as 'zksync'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'.

MODEL: cex_zora_addresses.sql

🟠 Modified by:

🔧 PR: #5804, Revert 'Revert 'Only keep relevant CEX EVM addresses (#5804)' (#5824)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms with parameters cex_addresses, blockchain, and traces. The macro is called with references to the model 'cex_evms_addresses' and a source named 'traces'.

🔧 PR: #5804, Revert 'Only keep relevant CEX EVM addresses (#5804)'
🧙 Author: @jeff-dude on 2024-04-24
📝 Summary: Removed a set variable and a macro call, and replaced it with a SELECT statement that retrieves specific columns from the 'cex_evms_addresses' table for the blockchain 'zora'.

🔧 PR: #5804, Only keep relevant CEX EVM addresses
🧙 Author: @hildobby on 2024-04-24
📝 Summary: Added a dbt macro call cex_evms that references the model cex_evms_addresses. The macro takes parameters for cex addresses, blockchain type, and traces source. Removed a select statement that hardcoded 'zora' as the blockchain value and selected specific columns from the table.

MODEL: cex_algorand_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table with columns for blockchain, address, CEX name, distinct name, added by user, and date added. It enables data analysts to track and manage various addresses associated with different blockchains on multiple centralized exchanges (CEXs) along with relevant details such as who added them and when they were added.

MODEL: cex_aptos_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a dataset with columns for blockchain, address, exchange name, distinct name, added by user, and date added. It enables data analysts to track and analyze the relationships between blockchain addresses and various exchanges where they are used or associated with.

MODEL: cex_bitcoin_addresses.sql

🟠 Modified by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_bitcoin_addresses.sql was modified.

MODEL: cex_cardano_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table with columns for blockchain, address, exchange name, distinct name, added by user, and date added. It enables data analysts to track and manage addresses associated with different exchanges on the Cardano blockchain.

MODEL: cex_evms_addresses.sql

🟠 Modified by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_evms_addresses.sql was modified.

MODEL: cex_cosmos_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table with columns for blockchain, address, exchange name, distinct name, added by user, and date added. It enables data analysts to track and analyze the relationships between different blockchains and their associated addresses on various exchanges.

MODEL: cex_elrond_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table with columns for blockchain, address, CEX name, distinct name, added by user, and date added. It enables data analysts to track and analyze information related to addresses associated with different blockchains on various centralized exchanges (CEXs), including details such as who added the information and when it was added.

MODEL: cex_eos_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_eos_addresses.sql was added.

MODEL: cex_injective_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a table with columns for blockchain, address, CEX name, distinct name, added by user, and date added. It enables data analysts to track and analyze information related to addresses on the Injective blockchain associated with the LAToken exchange.

MODEL: cex_litecoin_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_litecoin_addresses.sql was added.

MODEL: cex_polkadot_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a dataset with information on blockchain addresses associated with various exchanges. It enables data analysts to track and analyze the relationships between specific blockchain addresses, exchange names, distinct names, and details of who added them and when they were added.

MODEL: cex_ripple_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_ripple_addresses.sql was added.

MODEL: cex_solana_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_solana_addresses.sql was added.

MODEL: cex_tron_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: [changes too large] The model cex_tron_addresses.sql was added.

MODEL: cex_zilliqa_addresses.sql

🟢 Added by:

🔧 PR: #5802, Add CEX addresses for EVM chains, Bitcoin, Solana, Aptos, Cardano, Algorand, EOS, Cosmos, Elrond, Polkadot, Ripple, Tron, Zilliqa & Litecoin
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a dataset with columns for blockchain, address, exchange name, distinct name, added by user, and date added. It enables data analysts to track and analyze the relationships between blockchain addresses and exchanges where they are used or associated with specific users.

SECTOR: _sector

toggle to see all model updates

MODEL: dex_base_trades.sql

🟠 Modified by:

🔧 PR: #5819, Add zkevm to dex_base_trades.sql
🧙 Author: @chef-seaweed on 2024-04-24
📝 Summary: A reference to a new dbt model called 'dex_zkevm_base_trades' was added to the existing list of references.

MODEL: dex_zkevm_base_trades.sql

🟢 Added by:

🔧 PR: #5815, Add Pancakeswap trades on Polygon zkEVM to dex.trades
🧙 Author: @chef-seaweed on 2024-04-23
📝 Summary: This model combines data from two PancakeSwap base trade tables for ZK-EVM blockchains. It creates a unified view of trade information including token amounts, addresses, transaction details, and more. Additionally, it enhances the dataset by adding specific transaction columns like 'from', 'to', and 'index'. This consolidated dataset enables data analysts to analyze trading activities across different versions of PancakeSwap on ZK-EVM blockchains comprehensively.

MODEL: pancakeswap_v2_zkevm_base_trades.sql

🟢 Added by:

🔧 PR: #5815, Add Pancakeswap trades on Polygon zkEVM to dex.trades
🧙 Author: @chef-seaweed on 2024-04-23
📝 Summary: This model creates a table called uniswap_compatible_v2_trades that enables data analysts to analyze trades compatible with Uniswap v2 on the 'zkevm' blockchain for the 'pancakeswap' project. It includes information sourced from events related to swaps and pair creations in PancakeSwap's v2 version on zkevm.

MODEL: pancakeswap_v3_zkevm_base_trades.sql

🟢 Added by:

🔧 PR: #5815, Add Pancakeswap trades on Polygon zkEVM to dex.trades
🧙 Author: @chef-seaweed on 2024-04-23
📝 Summary: This new dbt SQL model creates a table called uniswap_compatible_v3_trades that enables data analysts to analyze and track trades on the PancakeSwap project using version 3 of the ZK-EVM blockchain. It sources data from events related to swaps and pool creations in the PancakeSwap V3 protocol on ZK-EVM.

MODEL: magiceden_polygon_base_trades.sql

🟠 Modified by:

🔧 PR: #5806, Fix magiceden duplicates
🧙 Author: @0xRobin on 2024-04-23
📝 Summary: Added logic to filter trades based on the relationship between buyer/seller and maker in erc721_fees CTE. Removed a comment about duplicates and a specific tx_hash filter from erc721_trades CTE.

🔧 PR: #5806, magiceden on polygon: remove troubled tx causing dupes
🧙 Author: @jeff-dude on 2024-04-22
📝 Summary: Added a comment explaining the presence of duplicates in the source data and suggesting investigation for potential fixes. A filter was added to exclude specific transaction hash from the dataset.

🔧 PR: #5806, Hot fix magiceden_polygon_base_trades
🧙 Author: @couralex6 on 2024-04-21
📝 Summary: A tag 'prod_exclude' was added to the dbt SQL model.

MODEL: dex_solana_bot_trades.sql

🟠 Modified by:

🔧 PR: #5805, feat: add solgun bot trades spellbook
🧙 Author: @whalehunting on 2024-04-23
📝 Summary: A reference to a new model sol_gun_solana_bot_trades was added in the SQL code.

MODEL: sol_gun_solana_bot_trades.sql

🟢 Added by:

🔧 PR: #5805, feat: add solgun bot trades spellbook
🧙 Author: @whalehunting on 2024-04-23
📝 Summary: This model creates a dataset that combines fee payments in SOL tokens with bot trades on the Solana blockchain. It includes details such as trade amounts, symbols, user IDs, and transaction information. The model also identifies the last trade within each transaction based on inner instruction indexes. This enables data analysts to analyze and track fee payments associated with specific trades on the Solana blockchain effectively.

MODEL: inscription_linea_all.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates an 'inscription_all' table that enables data analysts to track and analyze transactions related to a specific blockchain, starting from the first inscription block at height 56003.

MODEL: inscription_zkevm_all.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates an 'inscription_all' table that enables data analysts to track and analyze inscriptions related to a specific blockchain (in this case, 'zkevm'). The table includes information about transactions and the first inscription block. This allows analysts to study the evolution of inscriptions on the specified blockchain starting from block 1191503.

MODEL: inscription_linea_deploys.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a new table that enables data analysts to track and analyze deployments of inscriptions for a specific blockchain, in this case, 'linea'. It references an existing table containing all inscriptions for the specified blockchain.

MODEL: inscription_zkevm_deploys.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This SQL model creates a new table that enables data analysts to analyze and track inscription deploys for a specific blockchain (in this case, 'zkevm'). It references an existing table containing all inscriptions for the specified blockchain.

MODEL: inscription_all.sql

🟠 Modified by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two references were added in the dbt SQL model: 'inscription_linea_all' and 'inscription_zkevm_all'.

MODEL: inscription_deploys.sql

🟠 Modified by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two references were added in the dbt SQL model: 'inscription_linea_deploys' and 'inscription_zkevm_deploys'.

MODEL: inscription_mints.sql

🟠 Modified by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: Two references were added in the dbt SQL model: 'inscription_linea_mints' and 'inscription_zkevm_mints'.

MODEL: inscription_linea_mints.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This model creates a new table that enables data analysts to track and analyze information related to inscription mints for a specific blockchain, in this case, 'linea'.

MODEL: inscription_zkevm_mints.sql

🟢 Added by:

🔧 PR: #5812, Linea & zkEVM inscriptions
🧙 Author: @hildobby on 2024-04-23
📝 Summary: This SQL model creates and enables data analysts to track and analyze inscription mints for a specific blockchain (in this case, 'zkevm'). It references another model that contains all inscriptions for the specified blockchain.

SECTOR: safe

toggle to see all model updates

MODEL: safe_celo_transactions.sql

🟠 Modified by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: Added a join to the 'celo' transactions source and removed a join to the 'ethereum' transactions source. The model now filters based on specific conditions related to Celo transactions.

MODEL: safe_native_transfers_all.sql

🟠 Modified by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: A reference to a new dbt SQL model called 'safe_zkevm_matic_transfers' was added.

MODEL: safe_safes_all.sql

🟠 Modified by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: A reference to a new model called 'safe_zkevm_safes' was added in the dbt SQL model.

MODEL: safe_transactions_all.sql

🟠 Modified by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: A reference to a new dbt SQL model called 'safe_zkevm_transactions' was added in this pull request.

MODEL: safe_zkevm_matic_transfers.sql

🟢 Added by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: This model creates a SQL query that calculates the amount in USD for transactions on the 'zkevm' blockchain involving the token 'MATIC'. It retrieves data from traces and safe addresses, ensuring successful non-self calls with positive values. The query includes conditions based on project start date and incremental updates to prevent deployment issues. Additionally, it joins price data to convert transaction amounts into USD based on symbol and block time.

MODEL: safe_zkevm_safes.sql

🟢 Added by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: This model creates a dataset that identifies blockchain addresses, their creation versions, block dates and months, creation times, and transaction hashes. It filters data based on successful delegate calls to singleton Safe addresses with specific setup methods and gas usage thresholds. The model also includes conditional logic for incremental loading optimization based on timestamps.

MODEL: safe_zkevm_singletons.sql

🟢 Added by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: This model fetches all known singleton/mastercopy addresses used via factories from the specified sources. It enables data analysts to access and analyze unique addresses associated with singleton or mastercopy instances created by different proxy factories in the Gnosis Safe ZK-EVM environment.

MODEL: safe_zkevm_transactions.sql

🟢 Added by:

🔧 PR: #5758, Add zkevm to safe models
🧙 Author: @danielpartida on 2024-04-24
📝 Summary: This model retrieves data related to blockchain transactions, including block date, transaction details, gas usage, method type, and more. It enables analysts to track and analyze specific transaction methods within the blockchain network for further insights and optimizations.

SECTOR: chainlink

toggle to see all model updates

MODEL: chainlink_arbitrum_ccip_send_requested.sql

🟠 Modified by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: Added the column tx_hash to the SELECT statement and removed a line that was previously removing the column destination_blockchain.

MODEL: chainlink_arbitrum_ccip_tokens_transferred_logs.sql

🟢 Added by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: This model creates a dataset that combines information from the 'arbitrum' blockchain logs for events related to token locking and burning. It extracts relevant data such as block details, contract addresses, transaction hashes, and total tokens involved. By filtering based on specific topics and project start date, analysts can track locked and burned tokens over time for analysis or reporting purposes.

MODEL: chainlink_avalanche_c_ccip_send_requested.sql

🟠 Modified by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: Added the column tx_hash to be selected as the maximum value from the combined_logs table, in addition to selecting and grouping by other existing columns.

MODEL: chainlink_avalanche_c_ccip_tokens_transferred_logs.sql

🟢 Added by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: This model creates a SQL query that retrieves data from the 'avalanche_c' blockchain logs. It selects specific columns related to transactions, including block details, contract addresses, transaction hashes, and token amounts. The query filters for two different topics ('Locked' and 'Burned') with corresponding conditions based on the project start date. This model enables data analysts to analyze token locking and burning activities on the Avalanche C blockchain starting from a specified date.

MODEL: chainlink_base_ccip_send_requested.sql

🟠 Modified by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: Added the column tx_hash to be selected as the maximum value from the combined_logs table.

MODEL: chainlink_base_ccip_tokens_transferred_logs.sql

🟢 Added by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: This model creates a dataset that combines information from two different types of transactions ('Locked' and 'Burned') on the blockchain. It includes details such as block hash, contract address, transaction hash, block number, timestamps, and token amounts. This enables data analysts to analyze and track the movement of tokens within the specified project start date for further insights or reporting purposes.

MODEL: chainlink_bnb_ccip_send_requested.sql

🟠 Modified by:

🔧 PR: #5759, add in burned event
🧙 Author: @AnonJon on 2024-04-23
📝 Summary: Added the column tx_hash to be selected as the maximum value from the combined_logs table.

MODEL: chainlink_bnb_ccip_tokens_transferred_logs.sql

🟢 Added by:

🔧 PR: #5759, [add in burned event](https: