📰 2024-04-12: Weekly Prophet!

[andrewhong5297]

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

Sector	🔧 # PRs	🟢 # Added	🟠 # Modified	🧙 # Authors
dex	3	0	3	3
nft	1	0	1	1
labels	1	0	2	1
prices	5	0	5	5
staking	1	0	2	1
banana_gun	1	0	1	1
sol_trading_bot	1	0	1	1
_sector	7	12	11	6
tigris	1	0	34	1
balancer	1	0	2	1
zeroex	1	0	1	1
lido	1	0	1	1
addresses_events	1	1	0	1
odos	1	0	5	1

SECTOR: dex

toggle to see all model updates

MODEL: dex_info.sql

🟠 Modified by:

🔧 PR: #5723, Add Velocore to dex.trades on zkSync Era
🧙 Author: @tomfutago on 2024-04-05
📝 Summary: A new project called 'Velocore' was added to the list of projects in the SQL model.

🔧 PR: #5723, Added auragi swap dex to dex.trades
🧙 Author: @archie17277 on 2024-04-05
📝 Summary: Added 'auragi' with corresponding details to the list of values. Removed 'derpdex' from the list of values.

MODEL: dex_aggregator_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: The reference models that were added or removed in the diff are: odos_trades.

SECTOR: nft

toggle to see all model updates

MODEL: nft_marketplaces_info.sql

🟠 Modified by:

🔧 PR: #5753, Add Hyperspace to nft.marketplaces_info
🧙 Author: @hildobby on 2024-04-08
📝 Summary: A row for 'Hyperspace' with corresponding values was added to the temporary table.

SECTOR: labels

toggle to see all model updates

MODEL: labels_balancer_v2_pools_arbitrum.sql

🟠 Modified by:

🔧 PR: #5709, [READY FOR REVIEW] round of improvements to balancer spells
🧙 Author: @viniabussafi on 2024-04-07
📝 Summary: Added a section to the SQL model that selects specific columns from two sources and performs a CROSS JOIN UNNEST operation. The added logic retrieves data based on certain conditions and assigns static values to some columns.

MODEL: labels_balancer_v2_pools_optimism.sql

🟠 Modified by:

🔧 PR: #5709, [READY FOR REVIEW] round of improvements to balancer spells
🧙 Author: @viniabussafi on 2024-04-07
📝 Summary: Added a subquery to select pool information including ID, token address, normalized weight, symbol, and pool type from two sources joined on specific conditions. The weights are adjusted by dividing by 10^18.

SECTOR: prices

toggle to see all model updates

MODEL: prices_ethereum_tokens.sql

🟠 Modified by:

🔧 PR: #5752, chore: add price feed for SECT token
🧙 Author: @whalehunting on 2024-04-11
📝 Summary: FLOKI, SECT

🔧 PR: #5752, Update prices_ethereum_tokens.sql
🧙 Author: @safeintern on 2024-04-08
📝 Summary: ALT, PIXEL, OLAS, MNT, ARKM, FLOKI

🔧 PR: #5752, prices_tokens remove dupe
🧙 Author: @jeff-dude on 2024-04-08
📝 Summary: The token symbols that were added or removed are: AEVO, TREE, PIXEL, OLAS, MNT

🔧 PR: #5752, Update prices_ethereum_tokens.sql
🧙 Author: @lydiapuspita on 2024-04-08
📝 Summary: ETHFI, ALT, AEVO

🔧 PR: #5752, Update prices_ethereum_tokens.sql
🧙 Author: @jayneld on 2024-04-07
📝 Summary: TREE

SECTOR: staking

toggle to see all model updates

MODEL: staking_ethereum_entities_depositor_addresses.sql

🟠 Modified by:

🔧 PR: #5766, Add ETH stakers
🧙 Author: @hildobby on 2024-04-11
📝 Summary: Rows for new exchanges and their corresponding details were added to the SQL model.

MODEL: staking_ethereum_info.sql

🟠 Modified by:

🔧 PR: #5766, Add ETH stakers
🧙 Author: @hildobby on 2024-04-11
📝 Summary: A new entity 'Kelp DAO' with the corresponding x_username 'KelpDAO' was added to the temp_table.

SECTOR: banana_gun

toggle to see all model updates

MODEL: banana_gun_solana_bot_trades.sql

🟠 Modified by:

🔧 PR: #5761, chore: add new banana gun + sol trading bot fee wallets [easy]
🧙 Author: @whalehunting on 2024-04-11
📝 Summary: Fee receivers 6 and 7 were added to the list of addresses to exclude in certain conditions. This ensures that trades signed by FeeWallet are excluded when matching specific criteria.

SECTOR: sol_trading_bot

toggle to see all model updates

MODEL: sol_trading_bot_solana_bot_trades.sql

🟠 Modified by:

🔧 PR: #5761, chore: add new banana gun + sol trading bot fee wallets [easy]
🧙 Author: @whalehunting on 2024-04-11
📝 Summary: Two new sets of buy and sell fee receivers were added, along with their corresponding conditions in the SQL queries. The existing fee receiver variables were renamed to include a suffix '_1', and additional checks for the new fee receivers were included in the WHERE clauses to exclude trades signed by these wallets.

SECTOR: _sector

toggle to see all model updates

MODEL: pancakeswap_v2_arbitrum_base_trades.sql

🟠 Modified by:

🔧 PR: #5721, Add Pancakeswap Stableswap on Arbitrum on dex.trades
🧙 Author: @chef-seaweed on 2024-04-08
📝 Summary: A new CTE called 'dexs_macro' was added to the model, which includes a selection of data from a specific source. Another CTE named 'dexs' was also added, selecting and joining data from two different sources based on certain conditions. The final SELECT statement combines data from both CTEs and presents it in a unified format for further analysis.

MODEL: nft_avalanche_c_base_trades.sql

🟠 Modified by:

🔧 PR: #5742, Add Chikn NFT Trades Avalanche_c - Ready for review
🧙 Author: @henrystats on 2024-04-07
📝 Summary: Changed the reference from 'campfire_avalanche_c_base_trades' to 'chikn_avalanche_c_base_trades' in the list of nft_models.

MODEL: chikn_avalanche_c_base_trades.sql

🟢 Added by:

🔧 PR: #5742, Add Chikn NFT Trades Avalanche_c - Ready for review
🧙 Author: @henrystats on 2024-04-07
📝 Summary: This model creates a base table of trades related to the 'joepegs' project on the Avalanche blockchain. It includes details such as block time, NFT token ID, trade type, amount, buyer/seller information, price in raw form, contract addresses and transaction hashes. Additionally, it allows for adding NFT transaction data to enhance analysis capabilities for data analysts working with transactions involving NFTs within this specific project context.

MODEL: eas_celo_attestation_details.sql

🟢 Added by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: This dbt SQL model creates a table called eas_attestation_details that provides details on attestations for the Celo blockchain within the EAS project. It enables data analysts to analyze and report on attestation information specific to this project and blockchain version.

MODEL: eas_celo_attestations.sql

🟢 Added by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: This dbt SQL model creates a table called eas_attestations that enables data analysts to track attestations on the Celo blockchain for the EAS project. It includes a column named schemaUID and is part of version 1 of the project schema.

MODEL: eas_celo_schema_details.sql

🟢 Added by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: This SQL model creates a schema details table for the Celo blockchain project in the EAS system, enabling data analysts to access and analyze specific information related to this project's version 1.

MODEL: eas_celo_schemas.sql

🟢 Added by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: This SQL model creates a table named eas_schemas that allows data analysts to store information related to blockchain, project, and version. This enables tracking and analysis of schemas specific to the Celo blockchain for the EAS project version 1.

MODEL: eas_attestation_details.sql

🟠 Modified by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: A reference to a model named 'eas_celo_attestation_details' was added, while a reference to a model named 'eas_scroll_attestation_details' was removed.

MODEL: eas_attestations.sql

🟠 Modified by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: A reference to a model named 'eas_celo_attestations' was added, while a reference to a model named 'eas_scroll_attestations' was removed from the list of references in this dbt SQL model.

MODEL: eas_schema_details.sql

🟠 Modified by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: A reference to a model named 'eas_celo_schema_details' was added, while a reference to a model named 'eas_scroll_schema_details' was removed from the list of models being referenced.

MODEL: eas_schemas.sql

🟠 Modified by:

🔧 PR: #5749, Add Celo to EAS
🧙 Author: @tomfutago on 2024-04-07
📝 Summary: A reference to a model named 'eas_celo_schemas' was added, while a reference to a model named 'eas_scroll_schemas' was removed from the list of referenced models.

MODEL: dex_zksync_base_trades.sql

🟠 Modified by:

🔧 PR: #5739, Add Velocore to dex.trades on zkSync Era
🧙 Author: @tomfutago on 2024-04-05
📝 Summary: Three new references to different base trades tables were added in the dbt SQL model.

🔧 PR: #5739, Add Syncswap V2 to dex.trades on zkSync
🧙 Author: @lgingerich on 2024-04-05
📝 Summary: A reference to 'syncswap_zksync_base_trades' was removed, and references to 'syncswap_v1_zksync_base_trades' and 'syncswap_v2_zksync_base_trades' were added.

MODEL: velocore_v0_zksync_base_trades.sql

🟢 Added by:

🔧 PR: #5708, Add Velocore to dex.trades on zkSync Era
🧙 Author: @tomfutago on 2024-04-05
📝 Summary: This dbt SQL model creates a table called uniswap_compatible_v2_trades that enables data analysts to analyze and track trades on the Zksync blockchain for the Velocore project. It sources data from events related to pair swaps and pair creations in Velocore's Zksync implementation, allowing for further analysis of trading activities within this specific context.

MODEL: velocore_v1_zksync_base_trades.sql

🟢 Added by:

🔧 PR: #5708, Add Velocore to dex.trades on zkSync Era
🧙 Author: @tomfutago on 2024-04-05
📝 Summary: This dbt SQL model creates a table called uniswap_compatible_v2_trades that enables data analysts to analyze and query trade data specific to the 'zksync' blockchain for the 'velocore' project. The model sources information from two different events, Pair_evt_Swap and Factory_evt_PairCreated, from the 'velocore_v1_zksync' source.

MODEL: velocore_v2_zksync_base_trades.sql

🟢 Added by:

🔧 PR: #5708, Add Velocore to dex.trades on zkSync Era
🧙 Author: @tomfutago on 2024-04-05
📝 Summary: This model extracts data from a source related to token swaps on the Velocore platform, focusing on two-token swaps involving ETH and ERC20 tokens. It categorizes trades as buys or sells, identifies takers and makers, calculates token amounts exchanged, and records relevant details like block time and transaction hash. The model enables analysts to track swap activities within specific parameters for further analysis in the context of blockchain transactions.

MODEL: dex_arbitrum_base_trades.sql

🟠 Modified by:

🔧 PR: #5723, Added auragi swap dex to dex.trades
🧙 Author: @archie17277 on 2024-04-05
📝 Summary: A reference to a new model called 'auragi_arbitrum_base_trades' was added in the dbt SQL model.

MODEL: auragi_arbitrum_base_trades.sql

🟢 Added by:

🔧 PR: #5723, Added auragi swap dex to dex.trades
🧙 Author: @archie17277 on 2024-04-05
📝 Summary: This dbt SQL model creates a table called uniswap_compatible_v2_trades that enables data analysts to analyze and track trades on the Uniswap decentralized exchange specifically for the Arbitrum blockchain. It sources data from events related to pair swaps and pair creations within the specified project and version, facilitating analysis of trading activities on Uniswap for the Auragi project on Arbitrum.

MODEL: dex_base_trades.sql

🟠 Modified by:

🔧 PR: #5724, add zora uniswap v2 into dex.trades
🧙 Author: @andrewhong5297 on 2024-04-05
📝 Summary: A new reference to 'dex_zora_base_trades' was added in the model.

MODEL: dex_zora_base_trades.sql

🟢 Added by:

🔧 PR: #5724, add zora uniswap v2 into dex.trades
🧙 Author: @andrewhong5297 on 2024-04-05
📝 Summary: This model creates a union of data from the 'uniswap_v2_zora_base_trades' table, enabling data analysts to analyze trade information such as token amounts, addresses, takers, makers, contract details and transaction hashes for Zora blockchain projects. Additionally, it adds columns for 'from', 'to', and 'index' to facilitate further analysis on transaction details.

MODEL: uniswap_v2_zora_base_trades.sql

🟢 Added by:

🔧 PR: #5724, add zora uniswap v2 into dex.trades
🧙 Author: @andrewhong5297 on 2024-04-05
📝 Summary: This dbt SQL model creates a table called uniswap_compatible_v2_trades that enables data analysts to analyze and track trades compatible with Uniswap version 2 on the Zora blockchain project. It sources data from events related to pair swaps and pair creations in the Uniswap V2 Zora factory.

MODEL: syncswap_v1_zksync_base_trades.sql

🟠 Modified by:

🔧 PR: #5739, Add Syncswap V2 to dex.trades on zkSync
🧙 Author: @lgingerich on 2024-04-05
📝 Summary: Added a new variable syncswap_v1_start_date and replaced all occurrences of the previous variable syncswap_start_date with this new variable in the SQL model. The logic remains the same, where it checks for incremental updates based on block time or filters data based on a specific start date.

MODEL: syncswap_v2_zksync_base_trades.sql

🟢 Added by:

🔧 PR: #5739, Add Syncswap V2 to dex.trades on zkSync
🧙 Author: @lgingerich on 2024-04-05
📝 Summary: This model creates a dataset that combines information from multiple SyncSwap V2 pools. It enables data analysts to analyze swap transactions within these pools, including details such as token amounts, addresses involved in the swaps, transaction hashes, and block information. The model categorizes the data by blockchain type (zksync), project (syncswap), version (2), and provides insights into monthly and daily activity within the specified timeframe starting from February 12, 2024.

SECTOR: tigris

toggle to see all model updates

MODEL: tigris_arbitrum_events_add_margin.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_arbitrum_events_close_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_arbitrum_events_fees_distributed.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_arbitrum_events_limit_cancel.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced the condition in the WHERE clause with this new incremental predicate.

MODEL: tigris_arbitrum_events_limit_order.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' and changed the condition in the WHERE clause to use this incremental predicate instead of a fixed date range.

MODEL: tigris_arbitrum_events_liquidate_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a condition with the incremental predicate in the WHERE clause.

MODEL: tigris_arbitrum_events_modify_margin.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added incremental predicates for 'evt_block_time', 'call_block_time' to filter data based on these columns when the model is run incrementally.

MODEL: tigris_arbitrum_events_open_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' and replaced a hardcoded date filter with the incremental predicate function in the WHERE clause. The model now uses this dynamic approach to filter data based on 'evt_block_time'.

MODEL: tigris_arbitrum_events_options_close_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'DBT_INTERNAL_DEST.evt_block_time' and replaced the date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_arbitrum_events_options_fees_distributed.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate function for 'evt_block_time'.

MODEL: tigris_arbitrum_events_options_limit_cancel.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'DBT_INTERNAL_DEST.evt_block_time' and replaced the condition in the WHERE clause with this new incremental predicate.

MODEL: tigris_arbitrum_events_options_limit_order.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on the 'evt_block_time' column to the dbt model. Changed the WHERE clause in a SQL query to use this incremental predicate instead of a fixed date range condition for filtering data.

MODEL: tigris_arbitrum_events_options_open_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' to the model. Changed the WHERE clause condition to use this incremental predicate instead of a fixed date range for filtering data in an incremental manner.

MODEL: tigris_arbitrum_options_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced date_trunc conditions with incremental_predicate calls in the open_position, limit_order, close_position, and limit_cancel CTEs.

MODEL: tigris_arbitrum_perpetual_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added logic to use the incremental_predicate macro for filtering rows based on a specific timestamp column. This change replaces the hardcoded date filter with a dynamic one that is determined by the incremental predicate function.

MODEL: tigris_arbitrum_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added incremental predicates for various columns to support incremental processing. Replaced date_trunc conditions with the newly added incremental_predicate function for evt_block_time and other relevant columns in multiple CTEs.

MODEL: tigris_polygon_events_add_margin.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate function using 'evt_block_time'.

MODEL: tigris_polygon_events_close_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_polygon_events_contracts_positions.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: A hardcoded position contract was updated from version 'v2.5' to 'v2.6'.

MODEL: tigris_polygon_events_fees_distributed.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_polygon_events_limit_cancel.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a condition with the incremental predicate in the WHERE clause.

MODEL: tigris_polygon_events_limit_order.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' and replaced a condition with the incremental predicate function in the WHERE clause. The model now uses an incremental strategy with specific predicates for efficient data processing.

MODEL: tigris_polygon_events_liquidate_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a condition with the incremental predicate in the WHERE clause.

MODEL: tigris_polygon_events_modify_margin.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added incremental predicates for 'evt_block_time' in the dbt model. Replaced date_trunc filter with incremental_predicate for 'evt_block_time' in modify_margin_events_v2, add_margin_calls_v2, and remove_margin_calls_v2 SQL queries.

MODEL: tigris_polygon_events_open_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause. The model now uses this new logic for filtering data based on time intervals.

MODEL: tigris_polygon_events_options_close_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on the 'evt_block_time' column to the model. Changed the condition in the SQL query from filtering based on a specific date range to using this incremental predicate for filtering data.

MODEL: tigris_polygon_events_options_fees_distributed.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced a hardcoded date filter with the incremental predicate in the WHERE clause.

MODEL: tigris_polygon_events_options_limit_cancel.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'DBT_INTERNAL_DEST.evt_block_time' and replaced the condition in the WHERE clause with this new incremental predicate.

MODEL: tigris_polygon_events_options_limit_order.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on the 'evt_block_time' column to the model. Changed the condition in the WHERE clause of a query to use this incremental predicate instead of a fixed date range condition for filtering data based on 'evt_block_time'.

MODEL: tigris_polygon_events_options_open_position.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate on 'evt_block_time' to the model's configuration for incremental materialization. Removed a hardcoded date filter condition and replaced it with the newly added incremental predicate using dbt's function.

MODEL: tigris_polygon_options_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added an incremental predicate for 'DBT_INTERNAL_DEST.evt_block_time' and replaced date_trunc logic with the incremental predicate in multiple sections of the model.

MODEL: tigris_polygon_perpetual_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added logic to use the incremental_predicate macro for filtering rows based on the block time column.

MODEL: tigris_polygon_trades.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: Added incremental predicates for various columns to support incremental processing in the dbt model. Removed specific date filtering conditions and replaced them with generic incremental predicate functions using the respective column names.

MODEL: tigris_trades_pnl.sql

🟠 Modified by:

🔧 PR: #5748, Tigris fix plus incremental update - ready for review
🧙 Author: @henrystats on 2024-04-05
📝 Summary: In the close_liquidate model, a condition using an incremental predicate was added for filtering based on event block time. In the close_liquidate_pnl model, a similar incremental predicate condition was added for filtering based on minute. The final query selects data from the updated close_liquidate_pnl model.

SECTOR: balancer

toggle to see all model updates

MODEL: balancer_v2_arbitrum_protocol_fee.sql

🟠 Modified by:

🔧 PR: #5709, [READY FOR REVIEW] round of improvements to balancer spells
🧙 Author: @viniabussafi on 2024-04-07
📝 Summary: The changes involve setting the model to be materialized as a table and specifying the file format as 'delta'.

MODEL: balancer_token_whitelist.sql

🟠 Modified by:

🔧 PR: #5709, [READY FOR REVIEW] round of improvements to balancer spells
🧙 Author: @viniabussafi on 2024-04-07
📝 Summary: A whitelist token for 'WSTETH' with the corresponding address and platform was added to the existing list of whitelist tokens in this SQL model.

SECTOR: zeroex

toggle to see all model updates

MODEL: zeroex_ethereum_api_fills.sql

🟠 Modified by:

🔧 PR: #5740, zeroex - ethereum model
🧙 Author: @RantumBits on 2024-04-07
📝 Summary: Added conditions to the LEFT OUTER JOIN statements to filter by blockchain type 'ethereum'. Updated the join conditions for tables ts and ms in order to include filtering based on the blockchain column being equal to 'ethereum'.

SECTOR: lido

toggle to see all model updates

MODEL: lido_liquidity_ethereum_uniswap_v3_pools.sql

🟠 Modified by:

🔧 PR: #5750, uniswap v3 pools on mainnet
🧙 Author: @ppclunghe on 2024-04-07
📝 Summary: Added a UNION ALL clause to include mETH prices before 2023-12-31. The query selects the time truncated by day, token address '0xd5f7838f5c461feff7fe49ea5ebaf7728bb0adfa' representing mETH, decimals, currency as 'mETH', and average price from the source table 'prices' filtered for dates between December 1st and December 30th in the year 2023 where blockchain is Ethereum and symbol is WETH. Grouped by time truncation, token address, decimals, and currency.

SECTOR: addresses_events

toggle to see all model updates

MODEL: addresses_events_bitcoin_first_funded_by.sql

🟢 Added by:

🔧 PR: #5632, Create addresses_events_bitcoin.first_funded_by
🧙 Author: @hildobby on 2024-04-05
📝 Summary: This model creates a table that identifies the first appearance of Bitcoin addresses in transactions. It enables data analysts to track when and where specific addresses were first funded, including details such as block time, block height, and transaction ID. This information can be valuable for analyzing the flow of funds within the Bitcoin blockchain.

SECTOR: odos

toggle to see all model updates

MODEL: odos_v2_base_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: Added a CAST function to convert an array of integers to an array of bigints for the 'trace_address' column in the 'event_data' CTE.

MODEL: odos_v2_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: Added a cast operation to convert an array of integers to an array of bigints for the 'trace_address' field in the SQL model.

MODEL: odos_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: Added a reference to 'odos_base_trades' in the set of models. Added 'block_month' to the SELECT statement. Removed a note about an unmigrated spell due to duplicate issues and unresolved problems. Adjusted the field 'trace_address' by removing a comment specifying its explicit casting as an array in base models.

MODEL: odos_v1_optimism_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: Added a cast operation to convert an array containing a single element of type integer to an array of type bigint.

MODEL: odos_v2_optimism_trades.sql

🟠 Modified by:

🔧 PR: #5718, Adding Odos Ethereum and Base trades
🧙 Author: @amalashkevich on 2024-04-05
📝 Summary: Added a cast operation to convert an array containing -1 into an array of type bigint.