📰 2023-10-20: Weekly Prophet! #4644
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 38 PRs merged from 23 wizards. Great job everyone! 🎉
We had 115 added models 🟢 and 229 modified models 🟠 for 47 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_trades.sql
🟠 Modified by:
🔧 PR: #4579, Add WardenSwap DEX
🧙 Author: @chain-l on 2023-10-17
📝 Summary: The reference models that were added or removed in the diff are: wardenswap_optimism_trades
MODEL: dex_trades_seed.csv
🟠 Modified by:
🔧 PR: #4561, [REVIEWING] Add kyberswap elastic pool v2
🧙 Author: @nhd98z on 2023-10-16
📝 Summary: [changes too large] The model dex_trades_seed.csv was modified.
SECTOR: nft
toggle to see all model updates
MODEL: nft_ethereum_top_erc1155_holders.sql
🟠 Modified by:
🔧 PR: #4619, SPE-209 finalize migration to dunesql: convert leftover spark spells to spark views to persist
🧙 Author: @jeff-dude on 2023-10-17
📝 Summary: A note was added to the SQL model indicating that a spell has not been migrated to dunesql and is only a view on spark. The rest of the changes involve adding a common table expression (CTE) named 'erc1155_balances'.
MODEL: nft_ethereum_top_erc721_holders.sql
🟠 Modified by:
🔧 PR: #4619, SPE-209 finalize migration to dunesql: convert leftover spark spells to spark views to persist
🧙 Author: @jeff-dude on 2023-10-17
📝 Summary: A note was added to the SQL model indicating that a spell has not been migrated to dunesql and is only a view on spark. The rest of the changes involve adding a common table expression (CTE) named 'erc721_balances'.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_pools_arbitrum.sql
🟠 Modified by:
🔧 PR: #4598, Balancer Pool Labels fix
🧙 Author: @viniabussafi on 2023-10-17
📝 Summary: The added logic in this SQL model includes selecting specific columns from two different sources and joining them based on certain conditions. It also includes some calculations and transformations of the selected data. Additionally, there is a conditional statement that filters the data based on a date range if it is an incremental update. The main purpose seems to be retrieving information about pools, their token addresses, normalized weights, symbols, and pool types from the given sources.
MODEL: labels_balancer_v2_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #4598, Balancer Pool Labels fix
🧙 Author: @viniabussafi on 2023-10-17
📝 Summary: The added logic in this SQL model includes selecting various columns from two different sources and joining them based on specific conditions. It also includes cross-joining and unnesting operations to extract values from arrays. Additionally, there is a conditional statement that filters the data based on block time if the query is incremental. The main goal of this logic seems to be retrieving information about pools, their token addresses, normalized weights, symbols, and pool types from the given sources.
MODEL: labels_balancer_v2_pools_polygon.sql
🟠 Modified by:
🔧 PR: #4598, Balancer Pool Labels fix
🧙 Author: @viniabussafi on 2023-10-17
📝 Summary: The added logic in this SQL model includes selecting various columns from two different sources and joining them based on specific conditions. It also includes some calculations and transformations of the selected data. Additionally, there is a conditional statement that filters the data based on certain criteria if it is an incremental update. The main purpose seems to be retrieving information about pools, their token addresses, normalized weights, symbols, and pool types from the given sources.
MODEL: labels_eth_stakers.sql
🟠 Modified by:
🔧 PR: #4614, prod hotfix: fix incorrect column dependency on eth staking
🧙 Author: @jeff-dude on 2023-10-16
📝 Summary: The main logic added in this SQL model is the renaming of the column 'depositor_address' to 'address' in the identified_stakers CTE. This change was made for the blockchain 'ethereum' and includes additional columns such as name, category, and contributor.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_polygon_erc20.sql
🟠 Modified by:
🔧 PR: #4609, [tokens_polygon_erc20.sql] add USDR & wUSDR
🧙 Author: @zilayo on 2023-10-17
📝 Summary: The added token symbols are 'USDR' and 'wUSDR'.
MODEL: tokens_solana_fungible.sql
🟠 Modified by:
🔧 PR: #4567, small fixes to solana nft and dex
🧙 Author: @andrewhong5297 on 2023-10-16
📝 Summary: The token symbols that were added or removed in the given diff are: Added: SOL Removed: None
MODEL: tokens_solana_nft.sql
🟠 Modified by:
🔧 PR: #4567, small fixes to solana nft and dex
🧙 Author: @andrewhong5297 on 2023-10-16
📝 Summary: The token symbols that were added or removed in the diff are: Added: cNFT
Removed: None
SECTOR: op
toggle to see all model updates
MODEL: op_governance_optimism_delegates.sql
🟢 Added by:
🔧 PR: #4558, added optimism delegates spell
🧙 Author: @kaiblade on 2023-10-20
📝 Summary: This SQL model creates a table called 'OP_delegates_table' that provides data on voting power and delegation for delegates in the 'op_governance_optimism_voting_power' and 'op_governance_optimism_delegators' tables. It includes information such as current voting power, previous voting power, voting power change, total voting power share, number of delegators per delegate, total number of delegators across all delegates, and the percentage share of each delegate's delegators out of the total. This model enables data analysts to analyze and track changes in delegation patterns and overall governance dynamics.
MODEL: op_governance_optimism_delegates_addresses.sql
🟢 Added by:
🔧 PR: #4558, added optimism delegates spell
🧙 Author: @kaiblade on 2023-10-20
📝 Summary: [changes too large] The model op_governance_optimism_delegates_addresses.sql was added.
MODEL: op_governance_optimism_delegators.sql
🟢 Added by:
🔧 PR: #4558, added optimism delegates spell
🧙 Author: @kaiblade on 2023-10-20
📝 Summary: This dbt SQL model creates a table that extracts data from the 'GovernanceToken_evt_DelegateChanged' event in the 'op_optimism' source. It selects specific columns such as tx_hash, block_time, block_number, evt_index, fromDelegate and toDelegate. If incremental mode is enabled, it applies a filter based on the incremental predicate for evt_block_time. This model enables data analysts to analyze delegate changes in governance token events with relevant information like transaction hash and delegate addresses.
MODEL: op_governance_optimism_voting_power.sql
🟢 Added by:
🔧 PR: #4558, added optimism delegates spell
🧙 Author: @kaiblade on 2023-10-20
📝 Summary: This dbt SQL model creates a table that extracts specific columns from the 'GovernanceToken_evt_DelegateVotesChanged' table in the 'op_optimism' source. It includes columns such as transaction hash, block time, block number, delegate address, new balance and previous balance. The model also calculates the difference between new and previous balances as 'power_diff'. The data is filtered to include only records with a block time on or after May 26th, 2022. If running incrementally, it applies an incremental predicate based on the event block time column.
SECTOR: _sector
toggle to see all model updates
MODEL: nft_zksync_transfers.sql
🟢 Added by:
🔧 PR: #4529, Add zkSync to
nft.transfers🧙 Author: @hildobby on 2023-10-19
📝 Summary: This SQL model creates a table called 'nft_transfers' that enables data analysts to analyze and track NFT transfers on the Zksync blockchain. It combines data from multiple sources including base transactions, ERC721 transfers, ERC1155 single transfers, and ERC1155 batch transfers.
MODEL: nft_transfers.sql
🟠 Modified by:
🔧 PR: #4606, Add zkSync to
nft.transfers🧙 Author: @hildobby on 2023-10-19
📝 Summary: In this diff, a reference to the 'nft_zksync_transfers' table was added to the SQL model.
🔧 PR: #4606, Celo nft sector additions
🧙 Author: @tomfutago on 2023-10-18
📝 Summary: In this diff, a reference to the 'nft_celo_transfers' table was added to the SQL model. The SELECT statement remains unchanged and still selects all columns from the referenced tables.
MODEL: nft_zksync_approvals.sql
🟢 Added by:
🔧 PR: #4552, Add zkSync to
sectors.nft.approvals🧙 Author: @lgingerich on 2023-10-18
📝 Summary: This SQL model creates a table called 'nft_approvals' that enables data analysts to track and analyze NFT (non-fungible token) approvals on the ZkSync blockchain. It sources data from three different tables related to ERC721 and ERC1155 approval events.
MODEL: nft_approvals_legacy.sql
🟠 Modified by:
🔧 PR: #4552, Add zkSync to
sectors.nft.approvals🧙 Author: @lgingerich on 2023-10-18
📝 Summary: In this SQL model, the references to 'nft_zksync_approvals_legacy' were added. The SELECT statement remains unchanged and selects all columns from the referenced tables.
MODEL: nft_zksync_approvals_legacy.sql
🟢 Added by:
🔧 PR: #4552, Add zkSync to
sectors.nft.approvals🧙 Author: @lgingerich on 2023-10-18
📝 Summary: This SQL model creates a dummy table that will be removed in the near future. It does not provide any specific functionality or enable any analysis for data analysts.
MODEL: nft_approvals.sql
🟠 Modified by:
🔧 PR: #4552, Add zkSync to
sectors.nft.approvals🧙 Author: @lgingerich on 2023-10-18
📝 Summary: The diff of the SQL model shows that a reference to 'nft_zksync_approvals' was added. The SELECT statement remains unchanged.
MODEL: nft_celo_wash_trades.sql
🟢 Added by:
🔧 PR: #4606, Celo nft sector additions
🧙 Author: @tomfutago on 2023-10-18
📝 Summary: This SQL model creates a table called 'nft_wash_trades' that is specific to the blockchain 'celo'. It enables data analysts to analyze wash trades for non-fungible tokens (NFTs) on the Celo blockchain. The table includes information about addresses and events related to first funding of these trades.
MODEL: nft_celo_wash_trades_legacy.sql
🟢 Added by:
🔧 PR: #4606, Celo nft sector additions
🧙 Author: @tomfutago on 2023-10-18
📝 Summary: This SQL model does not create or enable anything for data analysts. It simply includes a single line of code that selects the value 1.
MODEL: nft_wash_trades.sql
🟠 Modified by:
🔧 PR: #4606, Celo nft sector additions
🧙 Author: @tomfutago on 2023-10-18
📝 Summary: In this diff, a reference to the 'nft_celo_wash_trades' table was added to the SQL model. The SELECT statement remains unchanged.
MODEL: opensea_events.sql
🟠 Modified by:
🔧 PR: #4569, SPE-209 finalize migration to dunesql: convert leftover spark spells to spark views to persist
🧙 Author: @jeff-dude on 2023-10-17
📝 Summary: A note was added to the SQL model indicating that the spell has not been migrated to dunesql and is only a view on spark. The SELECT statement remains unchanged.
🔧 PR: #4569, More misc models
🧙 Author: @couralex6 on 2023-10-16
📝 Summary: The main logic added in this diff is the inclusion of two tables, 'royalty_fee_currency_symbol' and 'unique_trade_id', in the FROM clause. These tables are sourced from a reference called 'opensea_polygon_events'.
MODEL: magiceden_v2_solana_trades.sql
🟠 Modified by:
🔧 PR: #4567, small fixes to solana nft and dex
🧙 Author: @andrewhong5297 on 2023-10-16
📝 Summary: In this SQL model, a few changes were made. The value for the 'project_program_id' column was updated from 'TSWAPaqyCSx2KABk68Shruf4rp7CxcNi8hAsbdwmHbN' to 'M2mx93ekt1fmXSVkTrUL9xVFHkmME8HTUi5Cyc5aF7K'. Additionally, some columns were added: 'account_merkle_tree', 'leaf_id', and 'aggregator_name'. The values for these columns are set as null. Finally, the value for the existing column 'account_mint' was changed to use the alias t.account_tokenMint instead of a hardcoded value.
MODEL: tensorswap_v1_solana_trades.sql
🟠 Modified by:
🔧 PR: #4567, small fixes to solana nft and dex
🧙 Author: @andrewhong5297 on 2023-10-16
📝 Summary: In this SQL model, a few changes were made. The value for the 'project_program_id' column was updated from 'TSWAPaqyCSx2KABk68Shruf4rp7CxcNi8hAsbdwmHbN' to 'TCMPhJdwDryooaGtiocG1u3xcYbRpiJzb283XfCZsDp'. Additionally, some columns were added: 'account_merkle_tree', 'leaf_id', 'aggregator_name', and 'aggregator_address'. The value of the existing column 't.account_mint' remains unchanged. Finally, the alias for the column t.call_tx_id was changed to tx_id.
SECTOR: oneinch
toggle to see all model updates
MODEL: oneinch_clipper_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references in the SQL model have been updated. The
sourcefunction now points to a different location (oneinch_ethereum) instead ofoneinch_v4_ethereum. The specific sources that were changed are'AggregationRouterV4_call_clipperSwap','AggregationRouterV4_call_clipperSwapTo', and'AggregationRouterV4_call_clipperSwapToWithPermit'.MODEL: oneinch_clipper_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references in the SQL model have been updated. The
sourcefunction now points to a different location (oneinch_ethereum) instead ofoneinch_v4_ethereum. The specific sources that were changed are'AggregationRouterV4_call_clipperSwap','AggregationRouterV4_call_clipperSwapTo', and'AggregationRouterV4_call_clipperSwapToWithPermit'.MODEL: oneinch_limit_order_protocol_embedded_rfq_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The diff shows that in the SQL model, the source references for three different calls have been updated from 'oneinch_v4_ethereum' to 'oneinch_ethereum'. The specific calls that were updated are:
MODEL: oneinch_limit_order_protocol_embedded_rfq_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The diff shows that in the SQL model, the source references for three different calls have been updated from 'oneinch_v4_ethereum' to 'oneinch_ethereum'. The specific calls that were updated are:
MODEL: oneinch_limit_order_protocol_rfq_v1_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is a change in the source of data for the
limit_order_protocol_rfq_v1model. The previous source'oneinch_lop_ethereum'and event name'LimitOrderProtocol_call_fillOrderRFQ'were replaced with a new source'oneinch_ethereum'and event name'LimitOrderProtocolV1_call_fillOrderRFQ'. Additionally, there is an inner join with another data source calledtraces, using the transaction hash to link the two sources together.MODEL: oneinch_limit_order_protocol_rfq_v1_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is a change in the source of data for the model. The previous source was 'oneinch_lop_ethereum' and the new source is 'oneinch_ethereum'. Additionally, there is a change in the name of the specific call being referenced from 'LimitOrderProtocol_call_fillOrderRFQ' to 'LimitOrderProtocolV1_call_fillOrderRFQ'. The join with another table remains unchanged.
MODEL: oneinch_limit_order_protocol_v1_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source table from 'oneinch_lop_ethereum' to 'oneinch_ethereum' and the change of the function name from 'LimitOrderProtocol_call_fillOrder' to 'LimitOrderProtocolV1_call_fillOrder'. The condition for call_success remains unchanged.
MODEL: oneinch_limit_order_protocol_v1_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source table from 'oneinch_lop_ethereum' to 'oneinch_ethereum' and the change of the function name from 'LimitOrderProtocol_call_fillOrder' to 'LimitOrderProtocolV1_call_fillOrder'. The condition for call_success remains unchanged.
MODEL: oneinch_v1_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this SQL model, there are multiple changes made to the source names. The source names have been updated from 'exchange_v1_call_aggregate' to 'ExchangeV1_call_aggregate', 'exchange_v2_call_aggregate' to 'ExchangeV2_call_aggregate', and so on. Additionally, one of the source names has been changed from 'OneInchExchange_call_swap' to 'AggregationRouterV1_call_swap'. These changes were made in order to update the sources being used in the model.
MODEL: oneinch_v1_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this SQL model, there are multiple changes made to the source names. The source names have been updated from 'exchange_v1_call_aggregate' to 'ExchangeV1_call_aggregate', 'exchange_v2_call_aggregate' to 'ExchangeV2_call_aggregate', and so on. Additionally, one of the source names has been changed from 'OneInchExchange_call_swap' to 'AggregationRouterV1_call_swap'. These changes were made in order to update the sources being used in the model.
MODEL: oneinch_v2_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this SQL model is a change in the source table. The previous source table was 'oneinch_v2_ethereum' and the new source table is 'oneinch_ethereum'. Additionally, there is a change in the name of the event from 'OneInchExchange_evt_Swapped' to 'AggregationRouterV2_evt_Swapped'. There is also an optional condition added for incremental processing where it filters events based on their block time being within 7 days from now.
MODEL: oneinch_v2_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source table from 'OneInchExchange_evt_Swapped' to 'AggregationRouterV2_evt_Swapped'. Additionally, there is a conditional statement checking if the model is incremental and filtering events based on their block time within the last week.
MODEL: oneinch_v3_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic change in this SQL model is the source of data. The previous source was 'oneinch_v3_ethereum' and it has been changed to 'oneinch_ethereum'. Additionally, there is a condition added to filter the data based on the event block time being within the last 7 days.
MODEL: oneinch_v3_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source name from 'oneinch_v3_ethereum' to 'oneinch_ethereum'. This change affects the table being queried in the model. Additionally, there is a conditional statement that filters events based on their block time if it's an incremental run.
MODEL: oneinch_v4_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source name from 'oneinch_v4_ethereum' to 'oneinch_ethereum'. This change affects the table being queried in the model.
MODEL: oneinch_v4_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic that was added in this diff is the change of the source name from 'oneinch_v4_ethereum' to 'oneinch_ethereum'. This change affects the table being queried in the model.
MODEL: oneinch_uniswap_v3_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references in the SQL model were updated. The previous source was 'oneinch_v4_ethereum' and it was changed to 'oneinch_ethereum'. The specific sources that were updated are 'AggregationRouterV4_call_uniswapV3Swap', 'AggregationRouterV4_call_uniswapV3SwapTo', and 'AggregationRouterV4_call_uniswapV3SwapToWithPermit'.
MODEL: oneinch_uniswap_v3_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references in the SQL model were updated. The previous source was 'oneinch_v4_ethereum' and it was changed to 'oneinch_ethereum'. The specific sources that were updated are 'AggregationRouterV4_call_uniswapV3Swap', 'AggregationRouterV4_call_uniswapV3SwapTo', and 'AggregationRouterV4_call_uniswapV3SwapToWithPermit'.
MODEL: oneinch_unoswap_v3_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references for two tables in the SQL model have been updated. The previous source was 'oneinch_v3_ethereum' and it has been changed to 'oneinch_ethereum'. The table names remain the same ('AggregationRouterV3_call_unoswap' and 'AggregationRouterV3_call_unoswapWithPermit'). Additionally, there is a condition checking if the execution is incremental.
MODEL: oneinch_unoswap_v3_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references for two tables in the SQL model have been updated. The previous source was 'oneinch_v3_ethereum' and it has been changed to 'oneinch_ethereum'. The table names remain the same ('AggregationRouterV3_call_unoswap' and 'AggregationRouterV3_call_unoswapWithPermit'). Additionally, there is a condition checking if the execution is incremental.
MODEL: oneinch_unoswap_v4_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references for two tables in the SQL model have been changed. The previous source was 'oneinch_v4_ethereum' and the new source is 'oneinch_ethereum'. The table names remain the same ('AggregationRouterV4_call_unoswap' and 'AggregationRouterV4_call_unoswapWithPermit'). Additionally, there is a condition to filter rows where call_success is true.
MODEL: oneinch_unoswap_v4_ethereum_trades_legacy.sql
🟠 Modified by:
🔧 PR: #4626, oneinch: cleanup sources naming
🧙 Author: @grkhr on 2023-10-19
📝 Summary: In this diff, the source references for two tables in the SQL model have been changed. The previous source was 'oneinch_v4_ethereum' and the new source is 'oneinch_ethereum'. The table names remain the same ('AggregationRouterV4_call_unoswap' and 'AggregationRouterV4_call_unoswapWithPermit'). Additionally, there is a condition to filter rows where call_success is true.
MODEL: oneinch_ar_calls.sql
🟠 Modified by:
🔧 PR: #4627, Oneinch: optimize top views
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic added in this diff is the use of a dictionary to define the columns and their corresponding aggregation functions. The code then iterates over this dictionary to generate two lists: one for selecting columns and another for grouping columns. These lists are used in the SELECT and GROUP BY clauses respectively when querying a table named 'oneinch_{blockchain}_ar_calls_transfers'.
MODEL: oneinch_calls.sql
🟠 Modified by:
🔧 PR: #4618, Oneinch: optimize top views
🧙 Author: @grkhr on 2023-10-19
📝 Summary: The main logic added in this diff is the use of a dictionary to define the columns and their corresponding aggregation functions. The select_columns and group_columns variables are then populated based on the values in the columns dictionary. Finally, these variables are used to generate the SELECT statement and GROUP BY clause for each blockchain in a loop.
🔧 PR: #4618, Oneinch updates 2
🧙 Author: @max-morrow on 2023-10-18
📝 Summary: In the given diff of the SQL model, a new column 'tx_to' was added. The rest of the columns remain unchanged.
MODEL: oneinch_exchange_contracts.sql
🟠 Modified by:
🔧 PR: #4618, Oneinch updates 2
🧙 Author: @max-morrow on 2023-10-18
📝 Summary: In the given SQL model, several contract names were changed. The word 'exchange' was replaced with 'Exchange' in the contract names for Ethereum blockchain. Similarly, the word 'limitorderprotocol' was replaced with 'LimitOrderProtocol'. Additionally, there were no changes made to AggregationRouter contracts.
MODEL: oneinch_fusion_settlements.sql
🟢 Added by:
🔧 PR: #4618, Oneinch updates 2
🧙 Author: @max-morrow on 2023-10-18
📝 Summary: This SQL model creates a table called 'settlements' with columns for contract address and blockchain. It populates the table with values for different contract addresses and their corresponding blockchains. This model enables data analysts to easily access and analyze settlement information related to various blockchains.
MODEL: oneinch_fusion_settlements_legacy.sql
🟢 Added by:
🔧 PR: #4618, Oneinch updates 2
🧙 Author: @max-morrow on 2023-10-18
📝 Summary: This SQL model creates a dummy table with a single column that contains the value 1. It is likely used as a placeholder or temporary table for testing purposes and will be removed in the near future.
SECTOR: rollup_economics
toggle to see all model updates
MODEL: l2_revenue.sql
🟠 Modified by:
🔧 PR: #4601, enhance l2_revenue spell & temporarily exclude from prod until resolved
🧙 Author: @jeff-dude on 2023-10-19
📝 Summary: The main logic added in this SQL model is the calculation of revenue and revenue in USD for different eras ('zksync era', 'arbitrum', 'op mainnet', 'op mainnet (ovm2)', and 'base'). The calculations involve aggregating gas used, gas price, l1_fee, and price data from different sources. There are also conditions based on incremental updates or full refreshes to determine the date range for each era's revenue calculation. The results are grouped by day and name.
🔧 PR: #4601, Change zkSync Revenue measurement method
🧙 Author: @lgingerich on 2023-10-18
📝 Summary: The main logic added in this SQL model is to calculate the revenue generated by zkSync transactions. The model selects the truncated day and sets the name as 'zksync era'. It calculates l2_rev and l2_rev_usd by summing gas used multiplied by gas price, converted to ETH and USD respectively. It joins with a source table for USD prices based on minute timestamps. The conditions for success, call type, specific 'from' addresses, value greater than 0, and block time are removed or modified.
SECTOR: gitcoin
toggle to see all model updates
MODEL: gitcoin_ethereum_donations.sql
🟠 Modified by:
🔧 PR: #4634, Partition Gitcoin Eth Donations by month
🧙 Author: @couralex6 on 2023-10-19
📝 Summary: The added logic in this SQL model includes selecting the blockchain as 'ethereum', version as 'v1', grant round name, block date truncated to day level, block month truncated to month level, block time, block number and amount raw.
MODEL: gitcoin_donations.sql
🟠 Modified by:
🔧 PR: #4634, Partition Gitcoin Eth Donations by month
🧙 Author: @couralex6 on 2023-10-19
📝 Summary: In this SQL model, a new column called 'block_month' was added. The rest of the columns remain unchanged.
MODEL: gitcoin_polygon_donations.sql
🟠 Modified by:
🔧 PR: #4634, Partition Gitcoin Eth Donations by month
🧙 Author: @couralex6 on 2023-10-19
📝 Summary: The added logic in this SQL model includes selecting the values 'polygon' and 'v1' as blockchain and version respectively. It also selects grd.round_name as grant_round, date_trunc('day', gd.block_time) as block_date, CAST(date_trunc('month', gd.block_time) AS DATE) as block_month, gd.block_time, gd.block_number, and gd.amount_raw.
SECTOR: transfers
toggle to see all model updates
MODEL: transfers_ethereum_eth.sql
🟠 Modified by:
🔧 PR: #4622, Migrate ETH Transfers to DuneSQL
🧙 Author: @MSilb7 on 2023-10-19
📝 Summary: The added logic in this SQL model selects various columns from the 'traces' and 'transactions' tables in the Ethereum source. It joins these two tables on matching transaction hashes and block numbers. There are also conditional filters applied to exclude certain call types, ensure successful transactions, and filter for non-zero values. Additionally, there are incremental predicates applied based on block time for both the 'transactions' table and the 'traces' table if it is an incremental run.
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note indicating that the spell has not been migrated to dunesql and is only a view on spark. The model also includes a CTE named 'eth_transfers' which selects data from the 'from' column in table r.
MODEL: transfers_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. The 'sent_transfers' CTE is also defined, but the details of its logic are not provided in the diff.
MODEL: transfers_ethereum_erc1155.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model is a CTE (Common Table Expression) named 'erc1155_ids_batch'. It selects data from an unspecified table or tables. The purpose of this CTE is not clear, but it seems to be related to the migration of a spell to dunesql and ensuring up-to-date logic and data.
MODEL: transfers_ethereum_erc1155_agg_day.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note indicating that the spell has not been migrated to dunesql and is only a view on spark. It also selects the 'ethereum' blockchain and truncates the event block time to day granularity.
MODEL: transfers_ethereum_erc1155_agg_day_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in the SQL model includes selecting the sum of the 'amount' column and concatenating various columns to create a unique transfer ID. The data is retrieved from a reference table called 'transfers_ethereum_erc1155_legacy'. There is also an optional filter that applies only during incremental runs, which checks if the event block time truncated to day is within 2 days from now. The results are then grouped by truncated event block time, wallet address, token address, token ID, and unique transaction ID.
MODEL: transfers_ethereum_erc1155_agg_hour.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. The select statement includes selecting 'ethereum' as blockchain and using date_trunc function to truncate evt_block_time by hour.
MODEL: transfers_ethereum_erc1155_agg_hour_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model is to calculate the sum of the 'amount' column and concatenate several columns to create a unique transfer ID. The data is selected from a reference table called 'transfers_ethereum_erc1155_legacy'. There is also an optional filter that will only be applied during incremental runs, which checks if the event block time truncated by hour is within the last 2 days. The result set is then grouped by date_trunc('hour', evt_block_time), wallet_address, token_address, tokenId, and unique_tx_id.
MODEL: transfers_ethereum_erc1155_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: A new alias called 'erc1155' with the parameter legacy_model=True was added. There is a note stating that this spell has not been migrated to dunesql and is only a view on spark. A common table expression (CTE) named erc1155_ids_batch was also added.
MODEL: transfers_ethereum_erc1155_rolling_day.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. It also selects 'ethereum' as the blockchain and includes a column for day.
MODEL: transfers_ethereum_erc1155_rolling_day_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The SQL model is not provided. Please provide the diff of the dbt SQL model in order to summarize it.
MODEL: transfers_ethereum_erc1155_rolling_hour.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the SQL model has not been migrated to dunesql and is only a view on spark. It also selects the 'ethereum' blockchain and hour as columns in the query result.
MODEL: transfers_ethereum_erc1155_rolling_hour_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The SQL model contains a select statement.
MODEL: transfers_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. The 'sent_transfers' CTE is also defined, but the details of its implementation are not provided in the diff.
MODEL: transfers_ethereum_erc20_agg_day.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note indicating that the spell has not been migrated to dunesql and is only a view on spark. The select statement includes columns 'blockchain' and 'day', with the latter being derived from truncating the event block time to day precision.
MODEL: transfers_ethereum_erc20_agg_day_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model is a filter that will only be applied on an incremental run. This filter checks if the event block time of transfers from the 'transfers_ethereum_erc20_legacy' table is greater than or equal to one week ago. The result set is then grouped by six columns and calculates the sum of the amount_raw divided by 10 raised to the power of decimals from both 'transfers_ethereum_erc20_legacy' and 'tokens_ethereum_erc20_legacy' tables.
MODEL: transfers_ethereum_erc20_agg_hour.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. It also selects the 'ethereum' blockchain and truncates the event block time to hours.
MODEL: transfers_ethereum_erc20_agg_hour_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model includes selecting the value 'ethereum' as the blockchain and truncating the event block time to hours. It then calculates the sum of transfer amounts divided by 10 raised to the power of token decimals. The transfers table is left joined with tokens table using contract address as a key. There is also an optional filter that applies only during incremental runs, restricting data to events within one week from now(). Finally, grouping is done on multiple columns (1-6).
MODEL: transfers_ethereum_erc20_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: A materialized view called 'sent_transfers' was added to the SQL model. The view is created using a select statement, but the details of the select statement are not provided in the diff.
MODEL: transfers_ethereum_erc20_rolling_day.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model is a select statement that includes the column 'blockchain' with the value 'ethereum', and a column called 'day'. There is also a note indicating that this spell has not been migrated to dunesql and is only a view on spark.
MODEL: transfers_ethereum_erc20_rolling_day_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The SQL model is not provided. Please provide the diff of the dbt SQL model in order to summarize it.
MODEL: transfers_ethereum_erc20_rolling_hour.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model is a select statement that selects the string 'ethereum' as the blockchain and the hour column. There is also a comment indicating that this spell has not been migrated to dunesql and is only a view on spark, suggesting it should be migrated for up-to-date logic and data.
MODEL: transfers_ethereum_erc20_rolling_hour_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The SQL model is not provided. Please provide the diff of the dbt SQL model in order to summarize it.
MODEL: transfers_ethereum_erc721.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: A note is added to the SQL model indicating that it has not been migrated to dunesql and is only a view on spark. The main logic added includes a common table expression (CTE) named 'received_transfers' which selects specific columns from the dataset and concatenates them into a unique transaction ID.
MODEL: transfers_ethereum_erc721_agg_day.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. It also selects the 'ethereum' blockchain and truncates the event block time to day granularity.
MODEL: transfers_ethereum_erc721_agg_day_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in this SQL model includes concatenating several columns to create a unique transfer ID, summing the amount column, and grouping by multiple columns. There is also an optional filter that applies only during incremental runs. The commented out line suggests that there was an issue with using the 'having' clause for filtering based on the sum of amounts.
MODEL: transfers_ethereum_erc721_agg_hour.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic includes a note stating that the spell has not been migrated to dunesql and is only a view on spark. The select statement includes selecting 'ethereum' as blockchain and using date_trunc function to truncate evt_block_time by hour.
MODEL: transfers_ethereum_erc721_agg_hour_legacy.sql
🟠 Modified by:
🔧 PR: #4622, SPE-209 Transfers + GMX models as views
🧙 Author: @couralex6 on 2023-10-17
📝 Summary: The added logic in the SQL model includes concatenating several columns to create
Beta Was this translation helpful? Give feedback.
All reactions