📰 2024-01-26: Weekly Prophet! #5243
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 41 PRs merged from 20 wizards. Great job everyone! 🎉
We had 89 added models 🟢 and 126 modified models 🟠 for 19 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_aggregator_trades.sql
🟠 Modified by:
🔧 PR: #5170, Added odos trades & contract creator address for the base
🧙 Author: @ARDev097 on 2024-01-22
📝 Summary: The reference models that were added or removed in the given diff are:
MODEL: dex_info.sql
🟠 Modified by:
🔧 PR: #5197, Added odos trades & contract creator address for the base
🧙 Author: @ARDev097 on 2024-01-22
📝 Summary: In the given SQL model, a new row has been added to the existing list of values. The new row represents an entity named 'Odos' with additional attributes such as 'Aggregator' and 'odosprotocol'.
🔧 PR: #5197, Added Creator Address for protocols deployed on Base & new dexes
🧙 Author: @chain-l on 2024-01-22
📝 Summary: Two new values, 'DackieSwap' and 'SmarDex', were added to the list of values in the SQL model.
🔧 PR: #5197, Add dooar to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-22
📝 Summary: In the given SQL model, a new row has been added to the temporary table. The row represents a project named 'dooar' with corresponding values for name, marketplace_type, and x_username columns.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_pools_arbitrum.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The main logic that was removed in this SQL model is a conditional statement that checks if the query is incremental. If it is, then additional conditions are added to filter the data based on block time. These conditions are removed from multiple parts of the model where they were originally present.
MODEL: labels_balancer_v2_pools_avalanche_c.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The logic that was removed from the SQL model is a conditional statement that filters the data based on the block time. The condition checks if the
is_incremental()function returns true and then applies additional filtering to only include data within a specific time range (7 days). This logic is no longer present in the updated model.MODEL: labels_balancer_v2_pools_base.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The logic that was removed from the SQL model is a conditional statement that filters the data based on the block time. The condition checks if the
is_incremental()function returns true and then applies additional filtering to only include data within a specific time range (7 days). This logic is no longer present in the updated model.MODEL: labels_balancer_v2_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: In this SQL model, several blocks of code were removed. These blocks contained conditional statements that checked if the model was incremental and filtered data based on block time. The removed code included conditions for
evt_block_timeandcall_block_timebeing greater than or equal to a specific date range (now() - interval '7' day). Additionally, there was a cross join with an array of tokens in one block that was also removed.MODEL: labels_balancer_v2_pools_gnosis.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The code removed some conditional statements that checked if the model was incremental and filtered data based on block time. The logic of the model remains unchanged.
MODEL: labels_balancer_v2_pools_optimism.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The main logic that was removed in this SQL model is a conditional statement that checks if the query is incremental. If it is, then additional conditions are added to filter the data based on block time. These conditions are removed from multiple parts of the model where they were originally present.
MODEL: labels_balancer_v2_pools_polygon.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The main logic that was removed in this SQL model is a conditional statement that checks if the query is incremental. If it is, then additional conditions are added to filter the data based on block time. These conditions are removed from multiple parts of the model where they were originally present.
MODEL: labels_beethoven_x_pools_fantom.sql
🟠 Modified by:
🔧 PR: #5221, Remove incremental settings from Balancer Pools Labels
🧙 Author: @viniabussafi on 2024-01-24
📝 Summary: The logic that was removed from the SQL model includes conditions related to incremental processing. These conditions checked if certain block times were greater than or equal to a specific date range. The removed code also included several WHERE clauses that filtered data based on block times.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_native.sql
🟠 Modified by:
🔧 PR: #5211, Add zkSync to
tokens_native🧙 Author: @lgingerich on 2024-01-23
📝 Summary: The added logic in the SQL model includes selecting columns 'chain', 'symbol', 'price_symbol', 'price_address', and 'decimals' from a temporary table. The temporary table is created using the VALUES clause, where rows are inserted with values for each column. One row was added to include information about the chain, symbol, price symbol, price address, and decimals for ZkSync.
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #5154, Update Tigris Arbitrum ETH Trades - Ready for review
🧙 Author: @henrystats on 2024-01-23
📝 Summary: The token symbols that were added or removed in the diff of the SQL model are: Added: tigETH Removed: None
SECTOR: prices
toggle to see all model updates
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #5222, Add SUB to prices_bnb_tokens.sql
🧙 Author: @0xfraan on 2024-01-25
📝 Summary: The token symbols that were added or removed are: SUB
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #5209, Added RBX to prices_ethereum_tokens.sql
🧙 Author: @0xVeto on 2024-01-23
📝 Summary: The token symbols that were added or removed are: JBOT, RBX
🔧 PR: #5209, Add BANANA to prices_ethereum_tokens.sql
🧙 Author: @0xVeto on 2024-01-23
📝 Summary: The token symbols that were added or removed in the diff are: BANANA, BANANA-GUN-V2
SECTOR: rollup_economics
toggle to see all model updates
MODEL: l1_data_fees.sql
🟠 Modified by:
🔧 PR: #5226, add mantle and fix timestamp issues
🧙 Author: @lorenz234 on 2024-01-25
📝 Summary: In the given SQL model, the following logic was added: 1. A new query was added to select data from two tables and perform calculations on them.
2. The selected columns include chain, block_number, hash, gas_spent (calculated using gas_used and gas_price), gas_spent_usd (calculated using price), input_length (length of data), and calldata_gas_used.
3. Joins were made with other tables based on specific conditions.
4. Additional conditions were added for filtering rows based on certain values in the 'to' column and 'data' column of a table.
5. The time range for selecting rows from a table was modified. Note: Some lines have been omitted due to exceeding the word limit or being repetitive code blocks
MODEL: l1_verification_fees.sql
🟠 Modified by:
🔧 PR: #5226, add mantle and fix timestamp issues
🧙 Author: @lorenz234 on 2024-01-25
📝 Summary: The main logic added in this diff is a change in the timestamp filter for two different tables. In the first table, the block_time condition was changed from '2021-03-24' to '2021-10-23'. In the second table, the time condition was also changed from '2022-01-01' to '2021-10-23'. These changes modify which records are included based on their respective timestamps.
SECTOR: _sector
toggle to see all model updates
MODEL: lending_gnosis_base_borrow.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a union of data from the 'agave_gnosis_base_borrow' table. It selects various columns related to blockchain transactions, including blockchain type, project details, transaction type, loan type, token address, borrower and repayer information. The model also includes details such as liquidator information and transaction amounts. This enables data analysts to analyze and query aggregated borrowing data across different projects in the Agave Gnosis platform.
MODEL: agave_gnosis_base_borrow.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_borrow' that is compatible with the Aave v2 lending protocol. It enables data analysts to analyze borrowing activity on the Gnosis blockchain for the Agave project, version 1.
MODEL: lending_base_borrow.sql
🟠 Modified by:
🔧 PR: #5213, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the model is being modified to include a new reference to 'lending_gnosis_base_borrow' while removing the reference to 'lending_fantom_base_borrow'.
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, a new reference to the model 'lending_bnb_base_borrow' was added.
MODEL: lending_gnosis_base_flashloans.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a union of data from the 'agave_gnosis_base_flashloans' table. It selects various columns such as blockchain, project, version, recipient, amount, fee, token_address and more. This model enables data analysts to retrieve and analyze information related to flash loans in different blockchains and projects.
MODEL: agave_gnosis_base_flashloans.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_flashloans' that is compatible with Aave v2 flashloan data from the Gnosis blockchain. It enables data analysts to analyze and query flashloan information specific to the Agave project, version 1.
MODEL: lending_base_flashloans.sql
🟢 Added by:
🔧 PR: #4873, Consolidate lending sector - flashloans macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of multiple lending base flashloan tables from different blockchains. It enables data analysts to query and analyze flashloan transactions across various blockchain platforms, including Arbitrum, Celo, Ethereum, Optimism, Polygon (formerly Matic), Avalanche C-Chain, and Fantom. The resulting dataset includes information such as blockchain type, project details, transaction amounts and fees paid for each flashloan transaction.
🟠 Modified by:
🔧 PR: #4873, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the model is being modified to include a new reference to 'lending_gnosis_base_flashloans' while removing the reference to 'lending_fantom_base_flashloans'.
🔧 PR: #4873, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In the given diff of the dbt SQL model, a new reference to 'lending_bnb_base_flashloans' has been added.
MODEL: lending_gnosis_base_supply.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a union of data from the 'agave_gnosis_base_supply' table. It selects various columns related to blockchain transactions such as blockchain, project, version, transaction type, token address, depositor/withdrawn_to/liquidator details, amount transferred and block information. This model enables data analysts to analyze and query aggregated transaction data across multiple sources in a unified manner.
MODEL: agave_gnosis_base_supply.sql
🟢 Added by:
🔧 PR: #5227, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_supply' that is compatible with Aave v2 lending protocol. It enables data analysts to analyze and track the supply of assets on the Gnosis blockchain for the Agave project, version 1.
MODEL: lending_base_supply.sql
🟢 Added by:
🔧 PR: #4853, Consolidate lending sector - supply macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of multiple lending base supply tables from different blockchains. It enables data analysts to query and analyze lending activity across various blockchain platforms, including Arbitrum, Celo, Ethereum, Optimism, Polygon (formerly Matic), Avalanche C-Chain, and Fantom. The resulting dataset includes information such as blockchain type, project name/version/type/transaction details/token address/depositor/withdrawal destination/liquidator amount/block month/time/number/hash/event index.
🟠 Modified by:
🔧 PR: #4853, Add agave to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the model is updated to include a reference to 'lending_gnosis_base_supply' while removing the reference to 'lending_fantom_base_supply'.
🔧 PR: #4853, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, a new reference to the model 'lending_bnb_base_supply' was added.
MODEL: lending_ethereum_base_borrow.sql
🟠 Modified by:
🔧 PR: #5213, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the
spark_ethereum_base_borrowmodel was added to the list of referenced models. Theuwulend_ethereum_base_borrowmodel was also removed from the list.🔧 PR: #5213, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, the model 'radiant_ethereum_base_borrow' was added and the model 'uwulend_ethereum_base_borrow' was also added. The models 'aave_v3_ethereum_base_borrow', 'compound_v2_ethereum_base_borrow', and 'compound_v3_ethereum_base_borrow' were not changed.
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, the model is updated to include a new reference to 'radiant_ethereum_base_borrow' while removing the reference to 'compound_v3_ethereum_base_borrow'.
MODEL: spark_ethereum_base_borrow.sql
🟢 Added by:
🔧 PR: #5228, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_borrow' that is compatible with Aave v3 lending protocol on the Ethereum blockchain. It enables data analysts to analyze borrowing activity and trends within the Aave ecosystem using Spark.
MODEL: lending_ethereum_base_flashloans.sql
🟢 Added by:
🔧 PR: #4873, Consolidate lending sector - flashloans macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of three different tables (
aave_v1_ethereum_base_flashloans,aave_v2_ethereum_base_flashloans, andaave_v3_ethereum_base_flashloans). It selects various columns from these tables, including blockchain, project, version, recipient, amount, fee, token address and more. This enables data analysts to analyze flashloan transactions across different versions of the AAVE protocol on the Ethereum blockchain.🟠 Modified by:
🔧 PR: #4873, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this SQL model, a reference to the 'uwulend_ethereum_base_flashloans' table was removed and a new reference to the 'spark_ethereum_base_flashloans' table was added.
🔧 PR: #4873, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, the model is being updated to include a new reference to 'uwulend_ethereum_base_flashloans' while removing the reference to 'radiant_ethereum_base_flashloans'.
🔧 PR: #4873, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this SQL model, a reference to the 'aave_v3_ethereum_base_flashloans' table was added and a reference to the 'radiant_ethereum_base_flashloans' table was also added. The previous reference to the 'aave_v3_ethereum_base_flashloans' table was removed.
MODEL: spark_ethereum_base_flashloans.sql
🟢 Added by:
🔧 PR: #5228, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_flashloans' that is compatible with Aave v3 flash loans on the Ethereum blockchain. It enables data analysts to analyze and query flash loan data using Spark Protocol version 1.
MODEL: lending_ethereum_base_supply.sql
🟢 Added by:
🔧 PR: #4853, Consolidate lending sector - supply macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of three different tables (
aave_v1_ethereum_base_supply,aave_v2_ethereum_base_supply, andaave_v3_ethereum_base_supply). It selects various columns related to blockchain transactions, such as the blockchain type, project, version, transaction type, token address, depositor/withdrawn_to/liquidator addresses or entities involved in the transaction), amount transferred/received in the transaction), block details (month/time/number), and other identifiers like transaction hash and event index. This model enables data analysts to analyze and compare data from multiple versions of AAVE Ethereum base supply tables.🟠 Modified by:
🔧 PR: #4853, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the model is updated to include a new reference to 'spark_ethereum_base_supply' while removing the reference to 'uwulend_ethereum_base_supply'.
🔧 PR: #4853, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, the model is updated to include a new reference to 'uwulend_ethereum_base_supply' while removing the reference to 'radiant_ethereum_base_supply'.
🔧 PR: #4853, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, the model is updated to include a new reference to 'radiant_ethereum_base_supply' while removing the reference to 'compound_v3_ethereum_base_supply'.
🔧 PR: #4853, Add compound to
lending.supply🧙 Author: @tomfutago on 2024-01-22
📝 Summary: In this diff, the model 'aave_v3_ethereum_base_supply' was removed from the list of models. Additionally, two new models 'compound_v2_ethereum_base_supply' and 'compound_v3_ethereum_base_supply' were added to the list.
MODEL: spark_ethereum_base_supply.sql
🟢 Added by:
🔧 PR: #5228, Add spark protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_supply' that is compatible with Aave v3 lending protocol. It enables data analysts to analyze and query supply data related to the Ethereum blockchain using Spark.
MODEL: aave_v3_arbitrum_base_borrow.sql
🟠 Modified by:
🔧 PR: #5229, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, a new column called 'decoded_contract_name' was added to the dbt SQL model 'lending_aave_v3_compatible_borrow'. The value of this column is set to 'L2Pool'.
MODEL: lending_base_base_borrow.sql
🟠 Modified by:
🔧 PR: #5229, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this SQL model, a reference to the
aave_v3_base_base_borrowmodel is removed and references to thecompound_v3_base_base_borrowandseamlessprotocol_base_base_borrowmodels are added.MODEL: seamlessprotocol_base_base_borrow.sql
🟢 Added by:
🔧 PR: #5229, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This dbt SQL model creates a table called 'lending_aave_v3_compatible_borrow' that is compatible with the Aave v3 lending protocol. It enables data analysts to analyze borrowing activity on the blockchain, specifically for the Seamless Protocol project and its L2Pool contract.
MODEL: aave_v3_arbitrum_base_flashloans.sql
🟢 Added by:
🔧 PR: #4873, Consolidate lending sector - flashloans macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_flashloans' that is compatible with Aave version 3 on the Arbitrum blockchain. It enables data analysts to analyze flashloan activity on the Aave platform using data from the specified blockchain and version.
🟠 Modified by:
🔧 PR: #4873, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, a new column called 'decoded_contract_name' with the value 'L2Pool' was added to the dbt SQL model 'lending_aave_v3_compatible_flashloans'. This change is specific to the 'arbitrum' blockchain and 'aave' project. The version of this model remains as '3'.
MODEL: lending_base_base_flashloans.sql
🟢 Added by:
🔧 PR: #4873, Consolidate lending sector - flashloans macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of data from the 'aave_v3_base_base_flashloans' table. It selects various columns related to blockchain transactions such as blockchain, project, version, recipient, amount, fee, token address and more. This model enables data analysts to analyze and query transactional data for Aave V3 flash loans across different projects and versions.
🟠 Modified by:
🔧 PR: #4873, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, a new reference to the model 'seamlessprotocol_base_base_flashloans' was added alongside the existing reference to 'aave_v3_base_base_flashloans'.
MODEL: seamlessprotocol_base_base_flashloans.sql
🟢 Added by:
🔧 PR: #5229, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_flashloans' that enables data analysts to analyze flashloan transactions on the base blockchain for the Seamless Protocol project. The table includes information about the version, project, and contract name associated with each transaction.
MODEL: aave_v3_arbitrum_base_supply.sql
🟢 Added by:
🔧 PR: #4853, Consolidate lending sector - supply macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_supply' that enables data analysts to analyze lending supply data from the Aave project on the Arbitrum blockchain. The version of Aave being used is version 3.
🟠 Modified by:
🔧 PR: #4853, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this diff, the main logic that was added is the inclusion of a new filter condition for
decoded_contract_name. The previous version did not have this filter, but now it has been added with the value'L2Pool'. This change allows for more specific filtering based on the decoded contract name in addition to other existing filters like blockchain, project, and version.MODEL: lending_base_base_supply.sql
🟢 Added by:
🔧 PR: #4853, Consolidate lending sector - supply macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of data from the 'aave_v3_base_base_supply' table. It selects various columns related to blockchain transactions such as blockchain, project, version, transaction type, token address, depositor/withdrawn_to/liquidator details, amount transferred and block information. This model enables data analysts to analyze and query aggregated transaction data across different projects and versions in the Aave v3 base supply dataset.
🟠 Modified by:
🔧 PR: #4853, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: In this SQL model, a reference to the
aave_v3_base_base_supplymodel is removed and references to thecompound_v3_base_base_supplyandseamlessprotocol_base_base_supplymodels are added.🔧 PR: #4853, Add compound to
lending.supply🧙 Author: @tomfutago on 2024-01-22
📝 Summary: In this diff, a new reference to the model 'compound_v3_base_base_supply' was added alongside the existing reference to 'aave_v3_base_base_supply'.
MODEL: seamlessprotocol_base_base_supply.sql
🟢 Added by:
🔧 PR: #5229, Add seamless protocol to lending
🧙 Author: @tomfutago on 2024-01-25
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_supply' that enables data analysts to analyze and query lending supply data from the Aave protocol. The table includes information related to the blockchain, project, version, project decoding, and decoded contract name for seamlessprotocol's L2Pool.
MODEL: tokens_base_transfers_view.sql
🟠 Modified by:
🔧 PR: #5236, Token transfers: prepare cross chain
🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: [changes too large] The model tokens_base_transfers_view.sql was renamed.
MODEL: tokens_base_transfers.sql
🟢 Added by:
🔧 PR: #5236, Token transfers: prepare cross chain
🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: This SQL model creates a union of multiple base transfer tables for different blockchains. It selects various columns from each table and combines them into a single result set. This enables data analysts to easily query and analyze transfer data across multiple blockchains in one consolidated view.
MODEL: tokens_bnb_base_transfers.sql
🟠 Modified by:
🔧 PR: #5233, Revert 'break out wrapped into own model (#5234)'
🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: The diff shows that a new SQL query was added to the model. The query performs a UNION ALL operation on two SELECT statements. The first SELECT statement retrieves all columns from the source table 'erc20_bnb' and 'evt_transfer'. The second SELECT statement is wrapped within a macro call named 'transfers_base_wrapped_token', which takes multiple sources as arguments and performs some logic related to blockchain transactions, wrapped token deposits, and withdrawals.
🔧 PR: #5233, bnb transfers: break out wrapped into own model
🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: The removed logic includes a UNION ALL statement and a SELECT statement that retrieves data from multiple sources. The added logic includes a new source called 'erc20_bnb' with an event type of 'evt_transfer', as well as the definition of a null value for the variable native_contract_address. Additionally, there is now another SELECT statement that retrieves data from different sources related to wrapped token deposits and withdrawals in the BNB blockchain.
🔧 PR: #5233, update & enhance
tokens_<blockchain>.base_transfersspells🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: In this SQL model, a UNION ALL operation is performed. The SELECT statement selects all columns from a subquery that calls the
transfers_base_wrapped_tokenmacro with specific parameters for the blockchain, transactions source, wrapped token deposit source, and wrapped token withdrawal source.MODEL: tokens_bnb_base_wrapped_transfers.sql
🟢 Added by:
🔧 PR: #5234, bnb transfers: break out wrapped into own model
🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: This SQL model creates a view that combines data from multiple sources to track transfers of wrapped tokens on the Binance blockchain. It enables data analysts to easily query and analyze these transfer transactions for further analysis.
MODEL: tokens_ethereum_base_transfers.sql
🟠 Modified by:
🔧 PR: #5212, update & enhance
tokens_<blockchain>.base_transfersspells🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: The diff shows that a SQL model called 'transfers_base' was modified. The changes include removing unnecessary line breaks and adding parentheses around the existing code block. There are no significant logic changes or additions made in this diff.
🔧 PR: #5212, Revert 'Fix token standard in
transfers_base(#5212)'🧙 Author: @jeff-dude on 2024-01-24
📝 Summary: The main logic added in the SQL model is a new table called 'transfers_base'. It includes columns for transfer ID, source account ID, destination account ID, amount transferred, and transfer date. The primary key is set on the transfer ID column.
🔧 PR: #5212, Fix token standard in
transfers_base🧙 Author: @lgingerich on 2024-01-24
📝 Summary: The main logic added in the SQL model is a new table called 'transfers_base'. It includes columns for transfer ID, source account ID, destination account ID, amount transferred, and transfer date. The primary key is set on the transfer ID column.
MODEL: tokens_polygon_base_transfers.sql
🟠 Modified by:
🔧 PR: #5233, update & enhance
tokens_<blockchain>.base_transfersspells🧙 Author: @jeff-dude on 2024-01-25
📝 Summary: The main logic added in this SQL model is a UNION ALL statement. It selects all columns from a subquery that calls the
transfers_base_wrapped_tokenfunction with specific parameters for different sources and blockchains. The subquery is wrapped within another SELECT statement, which then uses the UNION ALL operator to combine the results of multiple queries into a single result set.MODEL: uwulend_ethereum_base_borrow.sql
🟢 Added by:
🔧 PR: #5220, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_borrow' that is compatible with the Aave v2 lending protocol on the Ethereum blockchain. It is associated with the project 'uwulend' and version 1, and it enables data analysts to analyze borrowing activities within this lending protocol.
MODEL: uwulend_ethereum_base_flashloans.sql
🟢 Added by:
🔧 PR: #5220, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_flashloans' that is compatible with Aave v2 flash loans on the Ethereum blockchain. It enables data analysts to analyze and track flash loan activity for the project 'uwulend'.
MODEL: uwulend_ethereum_base_supply.sql
🟢 Added by:
🔧 PR: #5220, Add uwulend to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_supply' that is compatible with Aave v2 lending protocol. It enables data analysts to analyze and track the supply of assets on the Ethereum blockchain for the project 'uwulend'. The version of this model is 1, and it is associated with the project name 'uwulend'.
MODEL: lending_arbitrum_base_borrow.sql
🟠 Modified by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, a new reference to the model 'radiant_arbitrum_base_borrow' was added.
MODEL: radiant_arbitrum_base_borrow.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_borrow' that is compatible with the Aave v2 lending protocol on the Arbitrum blockchain. It enables data analysts to analyze borrowing activity for the project named 'radiant_capital' in version 1 of the project.
MODEL: lending_bnb_base_borrow.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This dbt SQL model creates a union of data from the 'radiant_bnb_base_borrow' table. It selects various columns related to blockchain transactions, including blockchain type, project details, transaction type, loan type, token address, borrower and repayer information. The model also includes details about liquidators involved in the transactions as well as amounts transferred. Additionally, it captures information about block timing and numbering along with transaction hashes and event indices. This model enables data analysts to analyze and report on borrowing activities within the specified blockchain context.
MODEL: radiant_bnb_base_borrow.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_borrow' that is compatible with the Aave v2 lending protocol. It enables data analysts to analyze borrowing activity on the Binance blockchain for the Radiant project, version 1.
MODEL: radiant_ethereum_base_borrow.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_borrow' that is compatible with the Aave v2 lending protocol on the Ethereum blockchain. It enables data analysts to analyze borrowing activity related to the Radiant Capital project.
MODEL: lending_borrow.sql
🟠 Modified by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: The given SQL model is incomplete and does not contain any code or logic to summarize. Please provide the complete diff of the dbt SQL model in order for me to generate a summary.
MODEL: lending_arbitrum_base_flashloans.sql
🟢 Added by:
🔧 PR: #4873, Consolidate lending sector - flashloans macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of data from the 'aave_v3_arbitrum_base_flashloans' table. It selects various columns related to blockchain transactions such as blockchain, project, version, recipient, amount, fee, token address and more. This model enables data analysts to analyze and query information about flash loans on the Aave v3 Arbitrum base platform.
🟠 Modified by:
🔧 PR: #4873, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, a new reference to the model 'radiant_arbitrum_base_flashloans' was added alongside the existing reference to 'aave_v3_arbitrum_base_flashloans'.
MODEL: radiant_arbitrum_base_flashloans.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_flashloans' that is compatible with Aave v2 flash loans on the Arbitrum blockchain. It enables data analysts to analyze and query flash loan data specifically for the Radiant Capital project in version 1.
MODEL: lending_bnb_base_flashloans.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a union of data from the 'radiant_bnb_base_flashloans' table. It selects various columns related to blockchain transactions such as blockchain, project, version, recipient, amount, fee, token address and more. This model enables data analysts to analyze and query information about flashloan transactions in the specified table.
MODEL: radiant_bnb_base_flashloans.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_flashloans' that is compatible with Aave v2 flash loans on the Binance Smart Chain. It enables data analysts to analyze and query flash loan data specific to the Radiant project version 1 on the Binance Smart Chain.
MODEL: radiant_ethereum_base_flashloans.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_flashloans' that is compatible with Aave v2 flashloan data on the Ethereum blockchain. It enables data analysts to analyze and query flashloan information specifically for the Radiant Capital project.
MODEL: lending_arbitrum_base_supply.sql
🟢 Added by:
🔧 PR: #4853, Consolidate lending sector - supply macro
🧙 Author: @tomfutago on 2024-01-19
📝 Summary: This SQL model creates a union of data from the 'aave_v3_arbitrum_base_supply' table. It selects various columns related to blockchain transactions such as blockchain, project, version, transaction type, token address, depositor/withdrawn_to/liquidator details, amount transferred and block information. This model enables data analysts to analyze and query aggregated transaction data across different projects and versions in the Aave v3 Arbitrum ecosystem.
🟠 Modified by:
🔧 PR: #4853, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: In this diff, a new reference to the model 'radiant_arbitrum_base_supply' was added.
🔧 PR: #4853, Add compound to
lending.supply🧙 Author: @tomfutago on 2024-01-22
📝 Summary: In this diff, a new reference to the model 'compound_v3_arbitrum_base_supply' was added. The existing reference to the model 'aave_v3_arbitrum_base_supply' remains unchanged.
MODEL: radiant_arbitrum_base_supply.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_supply' that is compatible with Aave v2 lending protocol. It is specifically designed for the Arbitrum blockchain and belongs to the Radiant project (also known as Radiant Capital). This table enables data analysts to analyze and track supply-related information within the Aave v2 lending protocol on Arbitrum for the Radiant project.
MODEL: lending_bnb_base_supply.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a union of data from the 'radiant_bnb_base_supply' table. It selects various columns related to blockchain transactions, including blockchain type, project details, transaction type, token address, depositor and recipient information, amount transferred, block details (month/time/number), transaction hash and event index. This model enables data analysts to analyze and query this combined dataset for insights into BNB base supply transactions across different projects on the blockchain.
MODEL: radiant_bnb_base_supply.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_supply' that is compatible with the Aave V2 lending protocol. It enables data analysts to analyze and query supply data specific to the Binance blockchain for the Radiant project. The version of this model is 1, and it has been decoded as 'radiant'.
MODEL: radiant_ethereum_base_supply.sql
🟢 Added by:
🔧 PR: #5213, Add radiant to lending
🧙 Author: @tomfutago on 2024-01-24
📝 Summary: This SQL model creates a table called 'lending_aave_v2_compatible_supply' that is compatible with Aave v2 lending protocol. It enables data analysts to analyze and track the supply of assets on the Ethereum blockchain for the Radiant Capital project.
MODEL: contracts_contract_creator_address_list.sql
🟠 Modified by:
🔧 PR: #5169, Next set of ten contract creator addresses on Base
🧙 Author: @chain-l on 2024-01-24
📝 Summary: The diff of the SQL model shows that several new entries were added to the 'curated_list' CTE. These entries include addresses and corresponding names of various entities such as 'Bryan On Base', 'DerpDEX', 'Xbased', and others. The comment indicates that these additions are related to MEV (Miner Extractable Value) and provides a link for more information about it.
🔧 PR: #5169, Added creator addresses for protocols on Base
🧙 Author: @chain-l on 2024-01-23
📝 Summary: The diff of the SQL model shows that several new entries were added to the 'curated_list' CTE. These entries include various addresses and corresponding names, such as 'Iceswap', 'BasinDAO', 'Torus', and others. The MEV entry for 'Jump Trading' was also included in this update.
🔧 PR: #5169, Added odos trades & contract creator address for the base
🧙 Author: @ARDev097 on 2024-01-22
📝 Summary: In this SQL model, several addresses and corresponding names were added to the 'curated_list' CTE. These addresses represent different entities such as finance platforms, protocols, and trading entities. The additions include Sobal Base, Autoearn Finance, ZebraDao, Toupee.tech, EDEBASE Mountain Protocol Sharesgram Sweep Energon Dex BAS3D Boobs.finance.
🔧 PR: #5169, Added Creator Address for protocols deployed on Base & new dexes
🧙 Author: @chain-l on 2024-01-22
📝 Summary: The diff of the SQL model shows that several addresses and corresponding names were added to the 'curated_list' CTE. These addresses and names represent different finance platforms such as Xena Finance, SmarDEX, CitadelSwap, SharkSwap, MeridianSwap, KokonutSwap, APXFinance, BaseMax,DIP Exchange,Voodoo Trade Base,and Detto Finance. Additionally,a new address for Jump Trading was also added with its corresponding name.
MODEL: magiceden_v2_solana_trades.sql
🟠 Modified by:
🔧 PR: #5200, magiceden fix usdc
🧙 Author: @andrewhong5297 on 2024-01-23
📝 Summary: Another addition is in the 'trades' CTE, where new columns are added to determine trade category, trade token symbol, and trade token mint based on certain conditions. There are also left joins with other tables like 'royalty_logs' and 'priced_tokens'. In the subsequent CTEs ('raw_nft_trades'), calculations are made for amount_original, amount_usd, taker_fee_amount_raw/usd/percentage etc., using values from trades table as well as another source table called 'prices' with some additional conditions. Overall, these additions involve joining tables and performing calculations based on specific conditions.
MODEL: paragraph_base_rewards.sql
🟠 Modified by:
🔧 PR: #5150, Update referral.rewards spell to Include paragraph mints without a referrer
🧙 Author: @datadanne on 2024-01-23
📝 Summary: In this diff, the following changes were made to the SQL model: - A new source called 'ERC721_call_mintWithReferrer' was added from the 'paragraph_base' model.
MODEL: paragraph_optimism_rewards.sql
🟠 Modified by:
🔧 PR: #5150, Update referral.rewards spell to Include paragraph mints without a referrer
🧙 Author: @datadanne on 2024-01-23
📝 Summary: In this SQL model, two sources are added: 'ERC721_call_mintWithReferrer' and 'ERC721_factory_contract'. The first source is used to retrieve data from the 'paragraph_optimism' table with the same name. The second source is a hardcoded value representing the ERC721 factory contract address. These additions are made to support referral rewards on the Optimism blockchain in a paragraph called 'paragraph_referral_rewards'.
MODEL: paragraph_polygon_rewards.sql
🟠 Modified by:
🔧 PR: #5150, Update referral.rewards spell to Include paragraph mints without a referrer
🧙 Author: @datadanne on 2024-01-23
📝 Summary: In the given SQL model, two new sources were added: 'ERC721_call_mintWithReferrer' and 'ERC721_factory_contract'. The existing source 'FeeManager_evt_FeeDistributed' was also included. The model is referring to a blockchain called 'polygon' and two contract addresses: '0x9e65211e0C29ad7B19FEb5D3D347134629be25Be' for ERC721_factory_contract and '0x00000000000000000000000
MODEL: paragraph_zora_rewards.sql
🟠 Modified by:
🔧 PR: #5150, Update referral.rewards spell to Include paragraph mints without a referrer
🧙 Author: @datadanne on 2024-01-23
📝 Summary: In this diff, the following changes were made to the SQL model: - A new source called 'ERC721_call_mintWithReferrer' was added from 'paragraph_zora'.
MODEL: contracts_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5180, Add zkSync to Contracts Mapping
🧙 Author: @MSilb7 on 2024-01-22
📝 Summary: In this diff, a reference to the SQL model 'contracts_zksync_contract_mapping' was added. The comment suggests that chains for all EVMs in Dune still need to be added.
MODEL: contracts_zksync_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5180, Add zkSync to Contracts Mapping
🧙 Author: @MSilb7 on 2024-01-22
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze contract creato
Beta Was this translation helpful? Give feedback.
All reactions