📰 2024-03-22: Weekly Prophet! #5648
andrewhong5297
announced in
Prophet (Weekly Updates)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is your weekly summary of 24 PRs merged from 15 wizards. Great job everyone! 🎉
We had 52 added models 🟢 and 83 modified models 🟠 for 17 Sectors.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_pools_arbitrum.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to change pool types from abbreviations to descriptive terms like 'weighted', 'investment', 'stable, and linear'.Updated the settings section to reflect these changes by replacing the previous pool type abbreviations with their corresponding descriptive terms.
MODEL: labels_balancer_v2_pools_avalanche_c.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to update the pool_type values in different scenarios. 'WP' was changed to 'weighted', 'SP' was changed to 'stable', and both instances of 'LP' were updated to be 'linear'. Additionally, a CASE statement was modified within the settings section, changing the conditions for lowercasing pool_symbol based on specific pool_type values ('stable', 'linear', or LBP).
MODEL: labels_balancer_v2_pools_base.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to assign different pool types based on the factory used for creating pools. Changed pool_type values from 'WP', 'SP', and 'LP' to 'weighted', 'stable', and 'linear' respectively. Updated conditions in a CASE statement to check for these new pool types when generating settings data, adjusting the corresponding output accordingly.
MODEL: labels_balancer_v2_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to update pool types from abbreviations to descriptive terms like 'weighted', 'investment', 'stable, and linear'. Additionally, the settings were adjusted to consider the new pool type descriptions for specific cases.
MODEL: labels_balancer_v2_pools_gnosis.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to change pool_type values from abbreviations to descriptive terms like 'weighted', 'stable', and 'linear'. Updated the conditions in a CASE statement to reflect these changes, replacing previous abbreviations with corresponding descriptive terms.
MODEL: labels_balancer_v2_pools_optimism.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to update pool types from abbreviations to descriptive terms like 'weighted', 'stable', and 'linear. Updated the pool type conditions in the settings section accordingly.
MODEL: labels_balancer_v2_pools_polygon.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic to update pool types from abbreviations to descriptive terms like 'weighted', 'investment', 'stable', and 'linear'. Updated the settings section to reflect these changes by replacing the previous pool type abbreviations with their corresponding descriptive terms.
MODEL: labels_beethoven_x_pools_fantom.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added logic:
SECTOR: prices
toggle to see all model updates
MODEL: prices_base_tokens.sql
🟠 Modified by:
🔧 PR: #5617, Add coinpaprika tokens to base and fantom
🧙 Author: @tiagofilipenunes on 2024-03-21
📝 Summary: GMR, USD+, BSWAP, BRETT
🔧 PR: #5617, Add coinpaprika tokens
🧙 Author: @tiagofilipenunes on 2024-03-18
📝 Summary: BSWAP, UNIDX
MODEL: prices_fantom_tokens.sql
🟠 Modified by:
🔧 PR: #5613, Add coinpaprika tokens to base and fantom
🧙 Author: @tiagofilipenunes on 2024-03-21
📝 Summary: The tokens that were added or removed are: BAY, USDC
🔧 PR: #5613, Add coinpaprika tokens
🧙 Author: @tiagofilipenunes on 2024-03-18
📝 Summary: The tokens that were added or removed are:
UNIDX
🔧 PR: #5613, add missing tokens
🧙 Author: @clizzard7 on 2024-03-18
📝 Summary: The tokens that were added or removed are: WOO, CEKKE
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #5613, adding bifi-beefy to ethereum prices
🧙 Author: @EPETE-EPETE on 2024-03-18
📝 Summary: The token symbols that were added are: BIFI
🔧 PR: #5613, add missing tokens
🧙 Author: @clizzard7 on 2024-03-18
📝 Summary: KOMPETE, SST, NERD, CRIMINGO, LINQ, XD, SCARCE,
PALAI,MAGA ,ROOT,DUEL,LILA ,UNDX ,TOAD,ZAT ,
FRIC,WBRGE PAAL,AIX AIMBOT,AIT
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #5613, add missing tokens
🧙 Author: @clizzard7 on 2024-03-18
📝 Summary: The tokens that were added are: 'YOU', 'BETS', 'JOE', and 'NOLA'.
MODEL: prices_avalanche_c_tokens.sql
🟠 Modified by:
🔧 PR: #5613, add missing tokens
🧙 Author: @clizzard7 on 2024-03-18
📝 Summary: MEAT, LOONG, MICRO, WILLY, NOCHILL, BEAR, TECH,
ALOT, MAJIN , MONK , MAN , BOBS , ROCO
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #5613, add missing tokens
🧙 Author: @clizzard7 on 2024-03-18
📝 Summary: AI, WAM, GQ, SquidGrow, STRX, TOKEN, HDV,DCK,CZGOAT,GZONE,Wefin,LAR,CPO,
REALM,AIPADWSI,BATTLEINFINITYNAZARSPINTOPTRUSTFI,FUSEAVA,KALMXAISIS
SECTOR: opensea
toggle to see all model updates
MODEL: opensea_v4_ethereum_events.sql
🟠 Modified by:
🔧 PR: #5642, deduplicate opensea_v4_ethereum
🧙 Author: @0xRobin on 2024-03-22
📝 Summary: A temporary fix was added to exclude duplicates by filtering out
tx_hashvalues that appear more than once in thetradestable based on specific columns.🔧 PR: #5642,
opensea_v4_ethereum_eventsexclude dupes🧙 Author: @jeff-dude on 2024-03-22
📝 Summary: Added tags for production exclusion, set materialization to incremental with a file format of delta, and specified an incremental strategy of merge.
SECTOR: lido
toggle to see all model updates
MODEL: lido_liquidity.sql
🟠 Modified by:
🔧 PR: #5636, lido liquidity zksync pools
🧙 Author: @ppclunghe on 2024-03-21
📝 Summary: A reference to a pool related to Uniswap v3 was removed, while references to pools related to Uniswap v3 and ZkSync Syncswap were added. The project start date was set as December 15, 2020.
MODEL: lido_liquidity_zksync_syncswap_pools.sql
🟢 Added by:
🔧 PR: #5636, lido liquidity zksync pools
🧙 Author: @ppclunghe on 2024-03-21
📝 Summary: This SQL model creates a comprehensive dataset for data analysts, enabling them to analyze liquidity pool metrics such as reserves, token prices, trading volumes, and more. It combines data from various sources to provide insights into pool activities like minting, burning tokens, and swapping. The model also calculates USD prices for tokens and includes information on project details like blockchain type.
SECTOR: beethoven_x
toggle to see all model updates
MODEL: beethoven_x_fantom_liquidity.sql
🟠 Modified by:
🔧 PR: #5637, update balancer and beethoven X labels
🧙 Author: @viniabussafi on 2024-03-21
📝 Summary: Added a condition to filter for pool types 'weighted' instead of 'WP' and 'WP2T'.
SECTOR: staking
toggle to see all model updates
MODEL: staking_ethereum_entities_chorusone.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: [changes too large] The model staking_ethereum_entities_chorusone.sql was modified.
MODEL: staking_ethereum_entities_coinbase.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: A condition was added to filter out a specific value in the 'from' column.
MODEL: staking_ethereum_entities_batch_contracts_tx_from.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: One row was added to the CTE 'tagged_entities' with information about a new entity related to Bitpanda in the category of Centralized Exchanges (CEX).
MODEL: staking_ethereum_entities_depositor_addresses.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: Added new entries for different entities with their corresponding details like name, type, and category. Some existing entries were updated to reflect a change in the category from 'Liquid Staking' to 'Liquid Restaking'. New entries include various entities such as Renzo, Bitstamp 3, Cumberland, Galaxy Digital, Hord and Everstake 3-5.
MODEL: staking_ethereum_deposits.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: A column for withdrawal_credentials_type was added to the SELECT statement. Additionally, a condition involving etes.sub_entity IS NOT NULL was both removed and then re-added in the LEFT JOIN clause.
MODEL: staking_ethereum_entities.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: Added references to three different tables for the column 'depositor_address' in the main model.
MODEL: staking_ethereum_flows.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: Added logic to calculate the amount of full and partial withdrawals based on specific conditions. Also, a join was added between the 'withdrawals' table and 'indexes' table using the validator index column. Additionally, withdrawal_credentials_type column was removed from both SELECT statements while withdrawal_credentials were retained in both SELECT statements.
MODEL: staking_ethereum_info.sql
🟠 Modified by:
🔧 PR: #5239, Labelling more stakers
🧙 Author: @hildobby on 2024-03-20
📝 Summary: Three new entries were added to the table: 'Renzo' with username 'RenzoProtocol', 'Cumberland' with username 'CumberlandSays', and 'Galaxy Digital' with username 'GalaxyHQ'.
SECTOR: jupiter
toggle to see all model updates
MODEL: jupiter_solana_perp_events.sql
🟢 Added by:
🔧 PR: #5630, add jupiter perps solana events
🧙 Author: @andrewhong5297 on 2024-03-20
📝 Summary: This model creates a dataset that tracks position changes in a financial system. It enables data analysts to analyze events such as increasing or decreasing positions, liquidations, and associated metrics like size changes, collateral transfers, fees, profits/losses. The model captures key information including position keys, side (long/short), owner details tied to token mints for long/short tokens and collaterals. Analysts can use this data to monitor trading activities and assess the performance of positions over time.
SECTOR: boost
toggle to see all model updates
MODEL: boost_arbitrum_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a SQL query that extracts data related to boost rewards and claims from the 'boost_arbitrum' table. It includes information such as reward network, boost address, boost ID and name, claimer address, reward amount in raw form and token address. Additionally, it provides details on claim transaction hash, block time, claim fee in ETH, action type and action transaction hash. The model also maps specific chain IDs to their corresponding networks for further analysis by data analysts working with Ethereum-based networks like Arbitrum.
MODEL: boost_arbitrum_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that provides information on boosts created in the Arbitrum network. It includes details such as boost address, ID, name, action type, network it belongs to (mapped based on chain ID), project name, boost type, start and end times, reward amount and token details,maximum participants allowed,time of creation,and creator. This dataset enables data analysts to analyze boosts specifically within the Arbitrum network with relevant contextual information for further analysis and insights.
MODEL: boost_base_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a SQL query that extracts data related to boosted rewards claimed on different networks. It maps network IDs to their corresponding names and retrieves information such as boost ID, name, reward amount, token address, claimer address, transaction details, fees in ETH, action type and associated network for each claim. This enables data analysts to analyze and track boosted rewards across multiple networks efficiently.
MODEL: boost_base_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that maps different network IDs to their corresponding names. It then selects various fields related to boost rewards and actions, including the network name based on the mapped IDs. This enables data analysts to analyze boost activities across different networks with details such as addresses, names, types, times, rewards, participants, and creators. The model also includes conditions for incremental data loading based on block time.
MODEL: boost_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model combines data from various boost claimed tables and enriches it with additional information. It creates a unified view of claims, including details such as reward amounts, transaction hashes, and network actions. The model also calculates the USD value of rewards based on token prices at specific block times. This enables data analysts to analyze and track boost-related activities across different networks efficiently while considering the financial implications in USD terms.
MODEL: boost_claimed_legacy.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a unified view of different types of claims (receipt mints, ERC20 claims, and ERC1155 claims) across various networks. It includes details such as reward amounts, addresses, transaction hashes, block times, and claim fees for each type of claim. This enables data analysts to analyze and compare claim data from multiple networks in a single query result set.
MODEL: boost_completors.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model calculates and enables data analysts to track various transaction fees and counts for different networks like Arbitrum, Ethereum, Optimism, and Polygon. It also provides insights into boost completions including the first time on boost, total boosts completed, and total rewards earned in USD.
MODEL: boost_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model combines data from multiple Boost deployed models to provide information on rewards, actions, and participants across different networks like Arbitrum, Ethereum, Optimism, and Polygon. It includes details such as reward amounts, project names, start/end times of boosts/actions,and creator addresses. By filtering out specific creators and timeframes,it enables analysts to analyze participation in boost campaigns based on various criteria for improved insights into network activity.
MODEL: boost_ethereum_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that includes information about rewards claimed on different networks such as Ethereum, Optimism, Polygon, and others. It extracts details like boost ID, name, reward amount in raw form and token address. Additionally, it provides data on the claimer's address and transaction hash along with block time. The model also categorizes the action network based on chain IDs mapped to specific networks provided in the set at the beginning of the script.
MODEL: boost_ethereum_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that maps specific chain IDs to their corresponding network names. It then selects various fields related to boost rewards and quests, including addresses, IDs, names, types, start/end times, reward amounts/tokens, participants count and creation details. The model enables data analysts to analyze boost activities across different networks by providing information on the reward network associated with each action type.
MODEL: boost_optimism_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that includes information about boost rewards claimed on the Optimism network. It extracts data such as boost ID, name, reward amount, token address, claimer address, transaction details, fees in ETH and action type. Additionally, it maps the corresponding network for each action based on the chain ID provided in the data. This enables analysts to track and analyze boost activities on Optimism with associated network information for further insights.
MODEL: boost_optimism_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that provides information on boosts created in various networks such as Ethereum, Optimism, Polygon, and others. It includes details like boost address, ID, name, action type, network it belongs to (based on chain ID), project name, boost type and timing details. This enables data analysts to analyze boosts across different networks and track their performance over time.
MODEL: boost_polygon_claimed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that enables data analysts to track and analyze rewards claimed on the Polygon network. It includes information such as boost ID, boost name, reward amount, token address, claimer address, transaction details, block time, claim fee in ETH calculated based on average prices of MATIC and WETH tokens over a specific period. Additionally it identifies the action network associated with each transaction by mapping chain IDs to their respective networks like Ethereum or Arbitrum.
MODEL: boost_polygon_deployed.sql
🟢 Added by:
🔧 PR: #5313, Added boost_deployed, boost_claimed and boost_completors model
🧙 Author: @pntemi on 2024-03-20
📝 Summary: This model creates a dataset that maps different network IDs to their corresponding names. It then selects various fields related to boost rewards from the 'boost_polygon' table, translating the chain ID into its respective network name using the mapping created. This enables data analysts to easily identify and analyze boost rewards across different networks based on specific criteria such as address, ID, type, timeframes, and reward amounts.
SECTOR: balancer
toggle to see all model updates
MODEL: balancer_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was added to the SQL model, specifically referencing the 'balancer_v2_arbitrum_trades' table.
MODEL: balancer_v2_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added to select specific columns from a reference model. The main logic of the changes involves joining this new CTE with an existing one ('dexs') based on certain conditions and filtering the results by blockchain, project, and version values. Additionally, some columns were renamed or modified in the final SELECT statement to reflect these changes.
MODEL: balancer_v2_arbitrum_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to track and analyze swap fees, token pairs, amounts traded, USD values, and other relevant information for transactions happening on the Balancer protocol version 2 on the Arbitrum blockchain. It combines data from multiple sources including swap events, token details, prices in USD, and block dates to provide a comprehensive view of decentralized exchange activities for reporting and analysis purposes.
MODEL: balancer_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was added to the SQL model.
MODEL: balancer_v2_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added to select specific columns from a reference table. Another CTE called 'dexs' was modified to include additional columns and filter conditions based on blockchain, project, and version values. The final SELECT statement was updated to include the newly added columns from the 'dexs' CTE and adjust column references accordingly. Join conditions were also updated in the final SELECT statement for consistency with these changes.
MODEL: balancer_v2_avalanche_c_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to analyze and track swap fees, token pairs, amounts bought and sold in a Balancer project on Avalanche blockchain. It calculates USD values for tokens exchanged, identifies takers and makers of transactions, fetches token symbols from ERC20 contracts, retrieves historical prices in USD for tokens involved in swaps at specific block times. The model also links transaction details with relevant pool information to provide comprehensive insights into decentralized exchange activities within the specified timeframe.
MODEL: balancer_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A list of balancer models was added to the SQL model.
MODEL: balancer_base_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set variable named 'balancer_models' was added, containing a reference to the model 'balancer_v2_base_trades'.
MODEL: balancer_v2_base_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added, which selects specific columns from a reference model. The existing logic in the 'dexs' CTE was modified to include additional columns and filters based on blockchain, project, and version values. The final SELECT statement now includes these new columns along with some modifications to existing column calculations and joins with other tables based on block numbers instead of event block numbers. Some unnecessary conditions related to incremental loading were removed from the JOIN clauses in the final SELECT statement.
MODEL: balancer_v2_base_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model creates a dataset that enables data analysts to analyze swap fees, token pairs, amounts traded, USD values of tokens bought and sold in Balancer V2. It also provides information on blockchain transactions related to these swaps including addresses involved and timestamps. The model allows for historical analysis as well as incremental updates based on specified project start dates or the last 7 days from the current date.
MODEL: balancer_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was added to the SQL model.
MODEL: balancer_v2_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added to select specific columns from a reference model. Another CTE called 'dexs' was modified to include additional columns and filter conditions based on blockchain, project, and version values. The final SELECT statement was updated to include these new columns in the output along with adjustments in column references and join conditions within the query. Some unnecessary calculations were removed or refactored for clarity.
MODEL: balancer_v2_ethereum_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to analyze Ethereum blockchain data related to Balancer version 2. It creates a dataset with information on token swaps, fees, prices, and transaction details. Analysts can explore token pairs traded, amounts exchanged in tokens and USD value, swap fees applied, involved addresses (taker/maker), pool IDs, and more for further insights into decentralized exchange activities within the specified timeframe.
MODEL: balancer_gnosis_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was added to the SQL model.
MODEL: balancer_v2_gnosis_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added to select specific columns from a reference model. The main logic involves joining this new CTE with an existing CTE 'dexs' based on certain conditions and filtering the results based on blockchain, project, and version criteria. Additionally, some columns were renamed or modified in the final SELECT statement to reflect changes made in previous steps.
MODEL: balancer_v2_gnosis_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to analyze swap fees, token transactions, and prices within the Balancer protocol on the Gnosis blockchain. It provides insights into token pairs traded, amounts exchanged in raw and standardized forms, USD values of transactions, involved addresses (taker/maker), pool IDs, swap fees applied, transaction details like hash and indices. Additionally,it allows for tracking block dates,tokens symbols,and their decimals.It also facilitates comparisons between different tokens' prices at specific times through various joins with price tables based on timestamps.
MODEL: balancer_optimism_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was defined, including a reference to 'balancer_v2_optimism_trades'.
MODEL: balancer_v2_optimism_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added to select specific columns from a reference table. The existing logic in the model was modified to include additional columns and conditions for filtering data based on blockchain, project, and version. Some column names were changed or removed, and the final SELECT statement now includes these new columns along with updated calculations for 'amount_usd'. Joins were adjusted accordingly based on these changes.
MODEL: balancer_v2_optimism_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to analyze and track swap fees, token transactions, prices, and other relevant information on the Balancer protocol version 2 deployed on the Optimism blockchain. It provides insights into token pairs traded, amounts bought/sold in raw and standardized forms (in USD), associated fees, transaction details like taker/maker addresses, pool IDs involved in swaps along with blockchain metadata. The model also incorporates incremental loading logic based on specified start dates for historical analysis or real-time updates within a given timeframe.
MODEL: balancer_polygon_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A set of balancer models was added to the SQL model.
MODEL: balancer_v2_polygon_trades.sql
🟠 Modified by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: A new CTE called 'dexs_base' was added, which selects specific columns from a reference table. The main logic involves joining this new CTE with an existing CTE 'dexs' based on matching transaction hashes and event indexes. Additionally, the final SELECT statement has been modified to include additional columns from the 'dexs' CTE and remove some calculations related to token prices that were present in the previous version of the model.
MODEL: balancer_v2_polygon_trades_legacy.sql
🟢 Added by:
🔧 PR: #5625, Rename balancer_v2_*_trades_beta to *_trades and resolve conflicts
🧙 Author: @Hosuke on 2024-03-20
📝 Summary: This model enables data analysts to analyze swap fees, token transactions, and prices on the Balancer protocol for Polygon blockchain. It provides insights into token pairs traded, amounts bought/sold in tokens and USD, transaction details like taker/maker addresses, pool IDs, swap fees percentages. The model also includes historical price data for tokens involved in swaps allowing for deeper analysis of trading activities on the platform.
MODEL: balancer_v2_arbitrum_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the model.
MODEL: balancer_v2_avalanche_c_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
MODEL: balancer_v2_base_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
MODEL: balancer_v2_ethereum_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
MODEL: balancer_v2_gnosis_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
MODEL: balancer_v2_optimism_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
MODEL: balancer_v2_polygon_trades_beta.sql
🟠 Modified by:
🔧 PR: #5501, SPE-345 finalize and migrate dex.trades to new structure
🧙 Author: @Hosuke on 2024-03-18
📝 Summary: Changed the reference from 'dex_trades_beta' to 'dex_trades' in the SQL model.
SECTOR: models
toggle to see all model updates
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_arbitrum_erc20.sql was modified.
MODEL: tokens_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_avalanche_c_erc20.sql was modified.
MODEL: tokens_base_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_base_erc20.sql was modified.
MODEL: tokens_bnb_bep20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_bnb_bep20.sql was modified.
MODEL: tokens_celo_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_celo_erc20.sql was modified.
MODEL: tokens_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
MODEL: tokens_fantom_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_fantom_erc20.sql was modified.
MODEL: tokens_gnosis_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_gnosis_erc20.sql was modified.
MODEL: tokens_polygon_erc20.sql
🟠 Modified by:
🔧 PR: #5595, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_polygon_erc20.sql was modified.
MODEL: tokens_zksync_erc20.sql
🟠 Modified by:
🔧 PR: #5623, SPE-350 introduce automated source for
tokens.erc20& revamp the entire lineage🧙 Author: @jeff-dude on 2024-03-20
📝 Summary: [changes too large] The model tokens_zksync_erc20.sql was modified.
🔧 PR: #5623, Add more ERC-20 tokens for zkSync
🧙 Author: @lgingerich on 2024-03-19
📝 Summary: [changes too large] The model tokens_zksync_erc20.sql was modified.
SECTOR: gyroscope
toggle to see all model updates
MODEL: gyroscope_gyro_tokens.sql
🟢 Added by:
🔧 PR: #5620, Init gyro_tokens
🧙 Author: @viniabussafi on 2024-03-19
📝 Summary: This model creates a table with information about different tokens, including their blockchain, address, symbol, decimals, and a fixed price of 1 USD. This enables data analysts to track and analyze these specific tokens within the given blockchains for various purposes such as monitoring token performance or conducting financial analysis.
SECTOR: cex
toggle to see all model updates
MODEL: cex_base_addresses.sql
🟢 Added by:
🔧 PR: #5588, Add cex.addresses for Base, Scroll & Gnosis
🧙 Author: @hildobby on 2024-03-18
📝 Summary: This model creates a base table that combines blockchain data with addresses from a specific source. It enables data analysts to analyze and track addresses associated with different entities across various blockchains in one consolidated view.
MODEL: cex_gnosis_addresses.sql
🟢 Added by:
🔧 PR: #5588, Add cex.addresses for Base, Scroll & Gnosis
🧙 Author: @hildobby on 2024-03-18
📝 Summary: This SQL model creates a dataset that combines information from the 'cex_evms_addresses' table, including blockchain, address, CEX name, distinct name, user who added the data and date it was added. This enables data analysts to analyze and track addresses associated with different blockchains on centralized exchanges (CEX).
MODEL: cex_scroll_addresses.sql
🟢 Added by:
🔧 PR: #5588, Add cex.addresses for Base, Scroll & Gnosis
🧙 Author: @hildobby on 2024-03-18
📝 Summary: This SQL model creates a dataset that combines blockchain addresses from a centralized exchange with additional information such as the exchange name, distinct name, user who added the data, and date it was added. This enables data analysts to analyze and track blockchain addresses associated with specific exchanges for further insights or investigations.
MODEL: cex_evms_addresses.sql
🟠 Modified by:
🔧 PR: #5161, add cex addresses
🧙 Author: @hildobby on 2024-03-18
📝 Summary: [changes too large] The model cex_evms_addresses.sql was modified.
MODEL: cex_info.sql
🟠 Modified by:
🔧 PR: #5161, add cex addresses
🧙 Author: @hildobby on 2024-03-18
📝 Summary: [changes too large] The model cex_info.sql was modified.
SECTOR: paraswap
toggle to see all model updates
MODEL: paraswap_optimism_trades.sql
🟠 Modified by:
🔧 PR: #5597, paraswap optimism: update version number in cross-version spell
🧙 Author: @jeff-dude on 2024-03-18
📝 Summary: Changed the reference from 'paraswap_v5_optimism_trades' to 'paraswap_v6_optimism_trades' in the list of dbt models.
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: Two references to the model
paraswap_v5_optimism_tradeswere added to the listparaswap_models.MODEL: paraswap_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: A new reference to a dbt model named 'paraswap_v6_arbitrum_trades' was added to the list of references in the dbt SQL model.
MODEL: paraswap_v6_arbitrum_trades.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This model creates a dataset that enables data analysts to analyze trades on the Paraswap project version 6 in the Arbitrum blockchain. It includes information such as token symbols, amounts bought and sold, USD values, addresses involved in transactions, contract details, and transaction hashes. The model also joins with other sources to provide additional details like token information and prices for further analysis.
MODEL: paraswap_v6_arbitrum_trades_decoded.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This model creates a table that likely tracks trades on the Paraswap platform for the AugustusV6 version specifically on the Arbitrum network. It enables data analysts to analyze and gain insights into trading activities, volumes, trends, and other relevant metrics related to Paraswap trades executed on Arbitrum using the AugustusV6 protocol.
MODEL: paraswap_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: A reference to a dbt model named 'paraswap_v6_avalanche_c_trades' was added to the list of models in the variable 'paraswap_models'.
MODEL: paraswap_v6_avalanche_c_trades.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This model enables data analysts to analyze and track trades on the Avalanche blockchain for the Paraswap project version 6. It includes information such as block time, token addresses, trade amounts in raw and converted USD values, transaction details like hash and addresses involved, as well as token symbols. Additionally, it incorporates price data for tokens traded (USDC.e and USDT.e) before specific dates to provide a comprehensive view of swap transactions with historical pricing context.
MODEL: paraswap_v6_avalanche_c_trades_decoded.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This dbt SQL model creates and enables data analysts to access and analyze information related to Paraswap trades on the Avalanche network using the AugustusV6 version.
MODEL: paraswap_base_trades.sql
🟠 Modified by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: A new reference to 'paraswap_v6_base_trades' was added to the list of models. The SELECT statement within a loop for each model was updated with UNION ALL logic between queries, ensuring that data from all specified models is combined in the final result set.
MODEL: paraswap_v6_base_trades.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This model creates a dataset that provides detailed information on trades made on the Paraswap platform. It includes data such as token amounts bought and sold, USD equivalent values, transaction details, token symbols, addresses, and project contract information. The model enables data analysts to analyze trading activities within a specified time frame and gain insights into the cryptocurrency market trends related to Paraswap transactions.
MODEL: paraswap_v6_base_trades_decoded.sql
🟢 Added by:
🔧 PR: #5597, Paraswap v6
🧙 Author: @alexshchur on 2024-03-18
📝 Summary: This dbt SQL model creates and enables data analysts to access and analyze Paraswap
Beta Was this translation helpful? Give feedback.
All reactions