📰 2024-01-12: Weekly Prophet! #5155
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 44 PRs merged from 15 wizards. Great job everyone! 🎉
We had 98 added models 🟢 and 85 modified models 🟠 for 21 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_info.sql
🟠 Modified by:
🔧 PR: #5064, Celo ImmortalX - add to
perpetual_trades🧙 Author: @tomfutago on 2024-01-05
📝 Summary: The line that was removed specified a marketplace type of 'Direct' for the project 'immortalx'. The line that was added changed the marketplace type to 'Perpetual' for the same project.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_gauges_ethereum.sql
🟠 Modified by:
🔧 PR: #5066, creates beethoven x fantom liquidity spell
🧙 Author: @viniabussafi on 2024-01-10
📝 Summary: In this SQL model, a join condition was added to the existing query. The left join now includes a reference to 'labels_balancer_v2_pools_ethereum' table and checks for a match between the address column in that table and the pool column in the call table.
MODEL: labels_beethoven_x_pools_fantom.sql
🟢 Added by:
🔧 PR: #5066, creates beethoven x fantom liquidity spell
🧙 Author: @viniabussafi on 2024-01-10
📝 Summary: This SQL model creates a view called 'pools' that combines data from multiple tables related to different types of pools in the Beethoven X Fantom blockchain. It retrieves information such as pool ID, token address, normalized weight, symbol, and pool type for each pool. The model also includes a view called 'settings' that joins additional information about the pools using reference data from the 'tokens_erc20' table. The final query selects specific columns from these views and organizes them into a result set with additional metadata like blockchain name and creation/update timestamps.
MODEL: labels_balancer_v2_pools_arbitrum.sql
🟠 Modified by:
🔧 PR: #5030, Add Gyro ECLPs labels to balancer pool labels
🧙 Author: @viniabussafi on 2024-01-09
📝 Summary: In this SQL model, a new section is added that selects data from two different sources and performs a UNION ALL operation. It retrieves the pool ID, token address, normalized weight (set to 0), symbol, and pool type ('ECLP') from the 'balancer_v2_arbitrum' source table joined with the 'gyroscope_arbitrum' source table. The CROSS JOIN UNNEST clause is used to unnest an array of tokens. Additionally, in the settings section of the model, 'ECLP' is included as one of the possible values for pool_type in a CASE statement.
MODEL: labels_balancer_v2_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #5030, Add Gyro ECLPs labels to balancer pool labels
🧙 Author: @viniabussafi on 2024-01-09
📝 Summary: In this SQL model, a new section called 'pools' was added. It includes a UNION ALL statement that selects data from two different sources and performs some joins and cross joins. The logic filters the data based on certain conditions related to block time. Additionally, in the 'settings' section, an additional condition was added to include 'ECLP' as one of the pool types when generating values for the blockchain address column.
MODEL: labels_balancer_v2_pools_optimism.sql
🟠 Modified by:
🔧 PR: #5030, Add Gyro ECLPs labels to balancer pool labels
🧙 Author: @viniabussafi on 2024-01-09
📝 Summary: In this SQL model, a new section was added that selects data from two different sources and performs a UNION ALL operation. It retrieves the pool ID, token address, normalized weight (set to 0), symbol, and pool type ('ECLP') from the 'balancer_v2_optimism' source table joined with the 'gyroscope_optimism' source table. The CROSS JOIN UNNEST clause is used to unnest an array of tokens. Additionally, in the settings section of the model, 'ECLP' was included as one of the possible values for pool_type in a CASE statement.
MODEL: labels_balancer_v2_pools_polygon.sql
🟠 Modified by:
🔧 PR: #5030, Add Gyro ECLPs labels to balancer pool labels
🧙 Author: @viniabussafi on 2024-01-09
📝 Summary: In this SQL model, a new section is added that selects data from two different sources and performs a UNION ALL operation. It retrieves the pool ID, token address, normalized weight (set to 0), symbol, and pool type ('ECLP') from the 'balancer_v2_polygon' source table joined with the 'gyroscope_polygon' source table. The CROSS JOIN UNNEST clause is used to unnest an array of tokens. Additionally, in the settings section of the model, 'ECLP' is included as one of the possible values for pool_type in a CASE statement.
MODEL: labels_balancer_v2_gauges.sql
🟠 Modified by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: In this SQL model, several references to different gauges models are added. These include gauges for Ethereum, Polygon, Arbitrum, Optimism, Avalanche C-Chain, Base Chain and Gnosis. The UNION ALL statement is also removed from the model.
MODEL: labels_balancer_v2_gauges_arbitrum.sql
🟠 Modified by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: The added logic in this SQL model includes the creation of two CTEs: 'reward_gauges' and 'child_gauges'. The 'reward_gauges' CTE selects distinct addresses from different sources and joins them based on certain conditions. The resulting dataset is filtered to exclude null values in the name column. Similarly, the 'child_gauges' CTE selects distinct addresses from specific sources, performs additional joins, and adds various columns with predefined values. Finally, a SELECT statement combines the results of both CTEs while filtering out null values in the name column for each subset of data.
MODEL: labels_balancer_v2_gauges_avalanche_c.sql
🟢 Added by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: This SQL model creates a view that retrieves distinct data from multiple sources and joins them together. It generates information related to the Avalanche blockchain, including addresses, names, categories, contributors, source details, creation and update timestamps. The model is named 'balancer_v2_gauges_avalanche_c' and uses an identifier as the label type. This enables data analysts to analyze and track various metrics related to Balancer V2 gauges on the Avalanche blockchain.
MODEL: labels_balancer_v2_gauges_base.sql
🟢 Added by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: This SQL model creates a view that retrieves distinct data from multiple sources and joins them together. It includes information about blockchain, address, name, category, contributor, source, created_at timestamp, updated_at timestamp,model_name,and label_type. The data is sourced from the 'balancer_ethereum' and 'balancer_base' tables and joined with the 'labels_balancer_v2_pools_base' reference table. This model enables data analysts to analyze and query Balancer V2 gauges based on specific criteria such as blockchain type or pool address.
MODEL: labels_balancer_v2_gauges_gnosis.sql
🟢 Added by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: This SQL model creates a dataset that enables data analysts to retrieve information about Gnosis pools in the Balancer V2 protocol. It includes details such as the blockchain, pool address, pool name, category, contributor, source of data query, creation and update timestamps. The model also specifies the label type for identification purposes.
MODEL: labels_balancer_v2_gauges_optimism.sql
🟠 Modified by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: The added logic in the SQL model includes creating two CTEs: 'reward_gauges' and 'child_gauges'. The 'reward_gauges' CTE combines data from multiple sources using JOIN operations. The 'child_gauges' CTE also combines data from different sources and adds additional columns to the result set. Finally, the SELECT statement at the end of the model uses UNION ALL to combine results from both CTEs, filtering out rows where name is NULL.
MODEL: labels_balancer_v2_gauges_polygon.sql
🟠 Modified by:
🔧 PR: #5039, Adds child gauges to balancer gauge labels
🧙 Author: @viniabussafi on 2024-01-06
📝 Summary: The added logic in this SQL model includes the creation of two CTEs: 'reward_gauges' and 'child_gauges'. The 'reward_gauges' CTE combines data from multiple sources using JOIN operations. The 'child_gauges' CTE also combines data from different sources and adds additional columns to the result set. Finally, a SELECT statement is used to combine the results of both CTEs using UNION ALL, with filters applied to exclude rows where the name column is NULL.
SECTOR: prices
toggle to see all model updates
MODEL: prices_solana_tokens.sql
🟠 Modified by:
🔧 PR: #5115, Add Solana tokens: HNT, JTO, GUAC
🧙 Author: @vidorge on 2024-01-09
📝 Summary: The added token symbols are HNT, JTO, GUAC. The removed token symbol is PYTH.
SECTOR: platypus_finance
toggle to see all model updates
MODEL: platypus_finance_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #5148, Fix incorrect value for block_month for platypus finance
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: In this SQL model, the main logic that was added includes:
The main logic that was removed includes:
SECTOR: _sector
toggle to see all model updates
MODEL: tokens_arbitrum_balances.sql
🟢 Added by:
🔧 PR: #5132, Add more chains
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: This SQL model creates a new table called 'balances_enrich' by merging data from the 'balances_arbitrum_0001' table in the 'tokens_arbitrum' source. It enables data analysts to analyze enriched balance information related to the Arbitrum blockchain.
MODEL: tokens_base_balances.sql
🟢 Added by:
🔧 PR: #5132, Add more chains
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: This SQL model creates a table called 'balances_enrich' by merging data from the 'tokens_base' and 'balances_base_0001' tables. It enables data analysts to analyze enriched balance information related to the base blockchain.
MODEL: tokens_bnb_balances.sql
🟢 Added by:
🔧 PR: #5132, Add more chains
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: This SQL model creates a new table called 'balances_enrich' by merging data from the 'tokens_bnb' and 'balances_bnb_0001' tables. It enables data analysts to analyze enriched balance information related to the Binance blockchain.
MODEL: tokens_optimism_balances.sql
🟢 Added by:
🔧 PR: #5132, Add more chains
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: This SQL model creates a new table called 'balances_enrich' by merging data from the 'balances_base' table in the 'tokens_optimism' source database with additional information from the 'blockchain'. It enables data analysts to analyze enriched balance information related to the Optimism blockchain.
MODEL: tokens_polygon_balances.sql
🟢 Added by:
🔧 PR: #5132, Add more chains
🧙 Author: @aalan3 on 2024-01-11
📝 Summary: This SQL model creates a table called 'balances_enrich' by merging data from the 'balances_base' table in the 'tokens_polygon' source database with additional information from the Polygon blockchain. It enables data analysts to analyze enriched balance information for tokens on the Polygon network.
MODEL: nft_base_base_trades.sql
🟢 Added by:
🔧 PR: #5055, Added spell for Alienswap base nft marketplace
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: This SQL model creates a union of multiple NFT trade tables, allowing data analysts to query and analyze data from different blockchain projects and versions. It provides information on various trade details such as buyer, seller, token ID, price, fees, addresses involved in the transaction, and more. The resulting table can be used for further analysis or reporting purposes.
MODEL: alienswap_base_base_trades.sql
🟢 Added by:
🔧 PR: #5055, Added spell for Alienswap base nft marketplace
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: This SQL model creates a base trades table that captures trade data from the Alienswap project. It includes information such as blockchain, project version, block time and date, block number, NFT contract address and token ID, seller and buyer details, trade category and type, price in raw format with currency contract information. It also calculates platform fee amount (hardcoded as 0%), royalty fee amount based on the minimum of two consideration amounts, royalty fee address based on recipient comparison. Additionally it adds transaction data to the base trades table until tx_from and tx_to are available in the base event tables.
MODEL: nft_base_trades.sql
🟠 Modified by:
🔧 PR: #5055, Added spell for Alienswap base nft marketplace
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: In this diff, a new reference to 'nft_base_base_trades' was added to the SQL model. This means that the model now includes a union with this new table in the 'base_union' common table expression.
MODEL: dex_base_base_trades.sql
🟠 Modified by:
🔧 PR: #5103, Added BaseSwap and Scale dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: In this diff, two references to SQL models ('baseswap_base_base_trades' and 'scale_base_base_trades') were added to the existing list of references. These new models are then used in a common table expression called 'base_union'.
MODEL: baseswap_base_base_trades.sql
🟢 Added by:
🔧 PR: #5103, Added BaseSwap and Scale dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Uniswap V2 protocol. It pulls data from two sources, 'PancakePair_evt_Swap' and 'PancakeFactory_evt_PairCreated', in the 'baseswap_base' project of the 'base' blockchain.
MODEL: scale_base_base_trades.sql
🟢 Added by:
🔧 PR: #5103, Added BaseSwap and Scale dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-10
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query Uniswap V2 trades. It pulls data from two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', in the 'scale_base' project of the blockchain database.
MODEL: nft_old_base_trades.sql
🟠 Modified by:
🔧 PR: #4879, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: The diff of the SQL model shows that several references to different events have been removed. Specifically, the references to 'quix_v1_optimism_events', 'quix_v2_optimism_events', 'quix_v3_optimism_events', 'quix_v4_optimism_events', 'quix_v5_optimism_events', 'tofu_optimism_events' and
🔧 PR: #4879, Arbitrum base trades
🧙 Author: @0xRobin on 2024-01-05
📝 Summary: In this SQL model, the references to 'stealcam_arbitrum_events', 'tofu_arbitrum_events', 'trove_ethereum_events', 'trove_v1_arbitrum_events' and 'trove_v2_arbitrum_events' have been removed. The references to 'quix_v3_optimism_events', 'quix_v4_optimism_event's, 'quix_v5_optimism_event's, 'tofu_bnb_event's and 'tofu_optimism_event's remain unchanged. Additionally, a new reference to the table named 'zonic_optimism_ events' has been added.
MODEL: quix_optimism_schema.yml
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: [changes too large] The model quix_optimism_schema.yml was modified.
MODEL: quix_v4_optimism_events.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: [changes too large] The model quix_v4_optimism_events.sql was removed.
MODEL: nft_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: This SQL model creates a base union table that combines data from multiple NFT models. It enables data analysts to query and analyze various attributes of NFT trades, such as blockchain, project details, trade category and type, buyer and seller information, token details (contract address and ID), price information (raw value), currency contract details, platform fee amount/address, royalty fee amount/address,and transaction details. The resulting table can be used for further analysis on NFT trading activities across different projects.
MODEL: quix_v1_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: This SQL model creates a base trades table that enables data analysts to analyze trade events on the Quix platform. It includes information such as block number, token ID, project contract address, transaction hash, block time, buyer and seller details, NFT contract address and amount of the trade. It also calculates platform fees and royalty fees associated with each trade.
MODEL: quix_v2_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: In this SQL model, several changes were made. The 'evt_index' column was added to the 'events_raw' CTE for three different source tables. In the 'base_trades' CTE, some columns were removed and new columns were added such as 'block_date', 'block_month', and 'sub_tx_trade_id'. Additionally, a function call to add NFT transaction data was included at the end of the model.
MODEL: quix_v3_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: In this SQL model, the diff shows that several new columns were added to the 'events_raw' CTE. These columns include 'evt_index'. Additionally, in the 'base_trades' CTE, there are changes made to column names and calculations. Some columns were removed or renamed, such as changing 'version' to 'project_version'. There are also changes related to date truncation and casting of certain values. Finally, a new function call is added at the end of the model for adding NFT transaction data in base trades.
MODEL: quix_v4_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: This SQL model creates a base trades table that combines data from multiple event tables. It includes information such as block number, token ID, contract addresses, transaction hash, buyer and seller details, price amount in raw format, trade category, and more. The model also joins with other tables to add additional data like currency contracts and royalty fees. Once the necessary columns are available in the base event tables (tx_from and tx_to), the last part of this model will be removed.
MODEL: quix_v5_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: In this SQL model, the logic for calculating trade details from raw events has been modified. The changes include renaming columns, adding new columns for date and month truncation of block time, changing the project version column name, modifying trade type and amount columns, removing some join conditions and tables related to ERC721 and ERC1155 transfers, filtering out royalty payments in the ERC20 transfer join condition,and adding a comment indicating that a function call will be removed once additional data is available.
MODEL: tofu_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: In the given SQL model, the table 'tofu_v1_events' was removed and replaced with a new table called 'tofu_v1_base_trades'. The source for 'raw_transactions' was also removed. Additionally, some parameters like blockchain, MarketNG_call_run, MarketNG_evt_EvInventoryUpdate were modified or added. The project_start_date parameter was set to '2021-12-23', and two new parameters NATIVE_ERC20_REPLACEMENT and NATIVE_SYMBOL_REPLACEMENT were added with their respective values.
MODEL: zonic_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5134, Optimism NFT base trades
🧙 Author: @0xRobin on 2024-01-10
📝 Summary: In this SQL model, the logic that was added includes:
platform_fee_percentage, royalty_fee_percentage
royalty_fee_address (from tr.to), and adding a new column platform_fee_address with null values.
The last part is a comment indicating that once tx_from and tx_to are available in base event tables,
the code will be removed.
MODEL: contracts_bnb_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5128, Contract Mapping - Add BNB
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze contract creators in the Binance Smart Chain (BSC) ecosystem. It includes contracts with the standard name 'bep' and considers data from 183 days forward.
MODEL: contracts_bnb_base_starting_level.sql
🟢 Added by:
🔧 PR: #5128, Contract Mapping - Add BNB
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' that enables data analysts to analyze contracts on the Binance chain. The table includes data for a period of 183 days in the future, allowing analysts to track and analyze contract activity over time.
MODEL: contracts_bnb_contract_mapping_dynamic.sql
🟢 Added by:
🔧 PR: #5128, Contract Mapping - Add BNB
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a contract mapping table that enables data analysts to map contracts from the Binance Smart Chain (BSC) with their corresponding standard names in the BEP format. This mapping allows for easier analysis and comparison of different contracts on the BSC network.
MODEL: contracts_bnb_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #5128, Contract Mapping - Add BNB
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Binance chain. The query takes parameters such as the blockchain (bnb) and the number of days forward (183) to look for these specific types of contracts.
MODEL: contracts_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5046, Contract Mapping - Add BNB
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: In this SQL model, a reference to the
contracts_bnb_contract_mapping_dynamictable was added. This change is part of a todo task to add chains for all EVMs in Dune.🔧 PR: #5046, Contracts - Test Incremental Initial Build & Add Polygon PoS
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: In this diff, a reference to the 'contracts_polygon_contract_mapping' model was added. This means that the SQL model now includes a dependency on the 'contracts_polygon_contract_mapping' model in addition to other existing dependencies.
🔧 PR: #5046, [Contracts] Materialize Chain-Level Tables
🧙 Author: @jeff-dude on 2024-01-09
📝 Summary: In this SQL model, a reference to the
contracts_celo_contract_mappingtable was added. The comment suggests that chains for all EVMs in Dune should be added as well.MODEL: contracts_polygon_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #4986, Contracts - Test Incremental Initial Build & Add Polygon PoS
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze contract creators on the Polygon chain for a period of 183 days in the future.
MODEL: contracts_polygon_base_starting_level.sql
🟢 Added by:
🔧 PR: #4986, Contracts - Test Incremental Initial Build & Add Polygon PoS
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' that enables data analysts to analyze contract information on the Polygon chain. It includes data for a period of 183 days in the future.
MODEL: contracts_polygon_contract_mapping.sql
🟢 Added by:
🔧 PR: #4986, Contracts - Test Incremental Initial Build & Add Polygon PoS
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a contract mapping table for the Polygon chain. It enables data analysts to easily access and analyze information related to contracts on the Polygon blockchain.
MODEL: contracts_polygon_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #4986, Contracts - Test Incremental Initial Build & Add Polygon PoS
🧙 Author: @MSilb7 on 2024-01-10
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Polygon chain. It takes parameters such as the chain name and number of days forward to look for these contracts.
MODEL: tokens_ethereum_balances.sql
🟠 Modified by:
🔧 PR: #5101, Balances view for raw data
🧙 Author: @aalan3 on 2024-01-10
📝 Summary: The main logic added in this diff is the inclusion of a new source table called 'balances_ethereum_0002' from the 'tokens_ethereum' schema. This new source table is used as the base for calculating enriched balances in the model. Additionally, a parameter called 'blockchain' with a value of 'ethereum' has been added to specify which blockchain network to use for calculations.
MODEL: contracts_contract_creator_address_list.sql
🟠 Modified by:
🔧 PR: #5088, OP Static Metadata Adds
🧙 Author: @MSilb7 on 2024-01-09
📝 Summary: [changes too large] The model contracts_contract_creator_address_list.sql was modified.
MODEL: contracts_contract_overrides.sql
🟠 Modified by:
🔧 PR: #5088, OP Static Metadata Adds
🧙 Author: @MSilb7 on 2024-01-09
📝 Summary: In this SQL model, two lines were added. The first line adds a contract with the address 0x74de5d4FCbf63E00296fd95d33236B9794016631 and labels it as 'Metamask Swaps' under Ethereum L1. The second line adds another contract with the address 0x881d40237659c251811cec9c364ef91dc08d300c and also labels it as 'Metamask Swaps' under Ethereum L1.
MODEL: contracts_deterministic_contract_creators.sql
🟠 Modified by:
🔧 PR: #5088, OP Static Metadata Adds
🧙 Author: @MSilb7 on 2024-01-09
📝 Summary: In the given SQL model, a line was removed that specified the 'Create3 Factory' address and its corresponding description. Additionally, a line was added that specifies the 'Create2Deployer' address and its corresponding description.
MODEL: contracts_system_predeploys.sql
🟠 Modified by:
🔧 PR: #5088, OP Static Metadata Adds
🧙 Author: @MSilb7 on 2024-01-09
📝 Summary: In this diff, the line that adds ('WETH', 'WETH9', 0x42000000000000000000000000...) and removes ('OVM', 'WETH9', 0x420...), indicates a change in the ownership of the WETH9 contract. The ownership is being transferred from OVM to WETH.
MODEL: dex_arbitrum_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, add ramses to
dex.trades_beta🧙 Author: @echovl on 2024-01-09
📝 Summary: In this diff, a reference to the model 'ramses_arbitrum_base_trades' was added. This model is now included in the list of models being referenced. Additionally, within the WITH statement, a condition was added where blockchain is equal to 'arbitrum' and columns include ['from', 'to', 'index'].
🔧 PR: #5062, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'xchange_arbitrum_base_trades' was added. This reference is included in a list of other models that are being referenced.
🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: The line
ref('kyberswap_arbitrum_base_trades')was added to the SQL model.MODEL: ramses_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5092, add ramses to
dex.trades_beta🧙 Author: @echovl on 2024-01-09
📝 Summary: This SQL model creates a view that combines data from two different sources,
dexs_legacyanddexs_cl, which represent trades on different versions of the Uniswap protocol. The view includes various columns related to the traded tokens, participants, transaction details, and event indices. This enables data analysts to analyze and compare trade data across different versions of Uniswap on the Arbitrum blockchain for the project 'ramses'.MODEL: dex_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, Add opx_finance to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-09
📝 Summary: The model added a reference to the table 'opx_finance_optimism_base_trades'.
🔧 PR: #5062, Add velodrome to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The model added a reference to the table 'velodrome_optimism_base_trades'.
🔧 PR: #5062, Add synthetix to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The model added a reference to 'synthetix_optimism_base_trades' in the list of referenced models.
🔧 PR: #5062, Add openxswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The line
ref('openxswap_optimism_base_trades')was added to the SQL model.🔧 PR: #5062, Add openocean to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The model added a reference to the 'openocean_optimism_base_trades' table.
🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: In this diff, a reference to the SQL model 'kyberswap_optimism_base_trades' was added. This means that the logic of this model is now included in the codebase.
MODEL: opx_finance_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5106, Add opx_finance to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-09
📝 Summary: This SQL model creates a table called 'generic_spot_compatible_trades' that is compatible with the Optimism blockchain and specifically for the project 'opx_finance'. It has a version number of 1 and it sources data from the table 'Router_evt_Swap' in the schema 'opx_finance_optimism'. This model enables data analysts to analyze spot trades on the Optimism blockchain for the specified project.
MODEL: foundation_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #5054, Add drop market trades to Foundation
🧙 Author: @fuJiin on 2024-01-09
📝 Summary: [changes too large] The model foundation_ethereum_base_trades.sql was modified.
MODEL: soundxyz_v2_base_rewards.sql
🟢 Added by:
🔧 PR: #5102, Add soundxyz v2 rewards to the referral.rewards spell
🧙 Author: @datadanne on 2024-01-09
📝 Summary: This SQL model creates a table called 'soundxyz_v2_referral_rewards' that is based on the 'SuperMinterV2_evt_Minted' table from the 'sound_xyz_base' database. It enables data analysts to analyze and track referral rewards in the SoundXYZ platform using blockchain technology.
MODEL: soundxyz_v2_ethereum_rewards.sql
🟢 Added by:
🔧 PR: #5102, Add soundxyz v2 rewards to the referral.rewards spell
🧙 Author: @datadanne on 2024-01-09
📝 Summary: This SQL model creates a table called 'soundxyz_v2_referral_rewards' that enables data analysts to track and analyze referral rewards on the Ethereum blockchain. The data for this analysis is sourced from the 'SuperMinterV2_evt_Minted' table in the 'sound_xyz_ethereum' database.
MODEL: soundxyz_v2_optimism_rewards.sql
🟢 Added by:
🔧 PR: #5102, Add soundxyz v2 rewards to the referral.rewards spell
🧙 Author: @datadanne on 2024-01-09
📝 Summary: This SQL model creates a table called 'soundxyz_v2_referral_rewards' that enables data analysts to track and analyze referral rewards on the Sound XYZ platform using data from the 'SuperMinterV2_evt_Minted' event in the Optimism blockchain.
MODEL: referral_staging_rewards.sql
🟠 Modified by:
🔧 PR: #5097, Add soundxyz v2 rewards to the referral.rewards spell
🧙 Author: @datadanne on 2024-01-09
📝 Summary: In this diff, the models 'soundxyz_ethereum_rewards' and 'soundxyz_optimism_rewards' were removed. In their place, new models 'soundxyz_v1_ethereum_rewards', 'soundxyz_v1_optimism_rewards', 'soundxyz_v2_ethereum_rewards', and so on were added. Additionally, a new model called 'soundxyz_v2_base_rewards' was also added.
🔧 PR: #5097, Add paragraph.xyz to the referral.rewards spell
🧙 Author: @datadanne on 2024-01-05
📝 Summary: The model added references to 'mirror_base_rewards', 'paragraph_optimism_rewards', 'paragraph_base_rewards', 'paragraph_zora_rewards', and 'paragraph_polygon_rewards'. The reference to the table 'mirror_optimism_rewards' was removed.
MODEL: xchange_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5111, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Uniswap decentralized exchange. The table is specific to the Arbitrum blockchain and the Xchange project, version 1. It sources data from two tables: 'XchangePair_evt_Swap' and 'XchangeFactory_evt_PairCreated'.
MODEL: dex_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'xchange_bnb_base_trades' was added.
🔧 PR: #5062, Add thena to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'thena_bnb_base_trades' was added.
🔧 PR: #5062, Add ellipsis_finance to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'ellipsis_finance_bnb_base_trades' was added.
🔧 PR: #5062, Add onepunchswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a new reference to the model 'onepunchswap_bnb_base_trades' was added. This reference is included in a list of other models ('maverick_bnb_base_trades', 'nomiswap_bnb_base_trades', and 'kyberswap_bnb_base_trades') within the curly braces.
🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: The model added a reference to 'kyberswap_bnb_base_trades' in addition to the existing references to 'iziswap_bnb_base_trades', 'maverick_bnb_base_trades', and 'nomiswap_bnb_base_trades'.
MODEL: xchange_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5111, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Uniswap decentralized exchange. It specifically focuses on trades in the Binance Smart Chain (bnb) for the project 'xchange'. The model sources data from two tables: 'XchangePair_evt_Swap' and 'XchangeFactory_evt_PairCreated'.
MODEL: dex_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'xchange_ethereum_base_trades' was added. This reference is included in a list of other models that are being referenced.
🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: In the given diff, a reference to a new table called 'kyberswap_ethereum_base_trades' was added to the SQL model.
MODEL: xchange_ethereum_base_trades.sql
🟢 Added by:
🔧 PR: #5111, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the Uniswap decentralized exchange on the Ethereum blockchain. It sources data from two tables: 'XchangePair_evt_Swap' and 'XchangeFactory_evt_PairCreated'.
MODEL: dex_polygon_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The model added a reference to 'xchange_polygon_base_trades' in addition to the existing references to 'dodo_polygon_base_trades', 'kyberswap_polygon_base_trades', and 'clipper_polygon_base_trades'.
🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: In this diff, the model is being updated to include a reference to 'kyberswap_polygon_base_trades'. This means that the SQL model will now include data from the 'kyberswap_polygon_base_trades' table in addition to the other referenced tables.
MODEL: xchange_polygon_base_trades.sql
🟢 Added by:
🔧 PR: #5111, Add xchange to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Polygon blockchain for the Xchange project. It pulls data from two sources: 'XchangePair_evt_Swap' and 'XchangeFactory_evt_PairCreated'.
MODEL: velodrome_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5112, Add velodrome to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a view that combines data from two different versions of the Velodrome project on the Optimism blockchain. It retrieves information about trades made on these versions, including details such as blockchain, project, version, block date and time, token amounts bought and sold, addresses involved in the trade (buying and selling), taker/maker information, project contract address used for the trade transaction hash and event index. This enables data analysts to analyze trading activity across different versions of Velodrome on Optimism.
MODEL: thena_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5113, Add thena to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a view that combines data from two different sources,
uniswap_compatible_v2_tradesanduniswap_compatible_v3_trades, into a single result set. It enables data analysts to query information about blockchain trades, including details such as the blockchain type, project name, version, block date and time, token amounts bought and sold, addresses involved in the trade (buyer/seller), project contract address used for the trade transaction hash,and event index.MODEL: synthetix_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5117, Add synthetix to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table that combines data from the 'SNX_evt_SynthExchange' table in the 'synthetix_optimism' database with data from the 'tokens_erc20' reference table. It includes information such as block number, block time, token amounts bought and sold, addresses of tokens bought and sold, taker and maker addresses, project contract address, transaction hash, and event index. This model enables data analysts to analyze SynthExchange events on the Optimism blockchain for the Synthetix project.
MODEL: dex_avalanche_c_base_trades.sql
🟠 Modified by:
🔧 PR: #5062, Add platypus_finance to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In the given diff of the dbt SQL model, a reference to 'platypus_finance_avalanche_c_base_trades' was added. This means that this particular table is now being included in the model's list of references.
🔧 PR: #5062, Add openocean to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: The line
ref('openocean_avalanche_c_base_trades')was added to the SQL model.🔧 PR: #5062, Add kyberswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-05
📝 Summary: In this diff, a new reference to the model 'kyberswap_avalanche_c_base_trades' was added. This reference is included in a list of other models that are being referenced.
MODEL: openxswap_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5120, Add openxswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table that extracts data from the 'Aggregator_evt_Swap' table in the 'openxswap_optimism' source. It includes information such as block number, block time, token amounts, addresses of tokens bought and sold, sender and receiver details, project contract address, transaction hash and event index. This model enables data analysts to analyze swap events on the OpenXSwap platform on the Optimism blockchain.
MODEL: ellipsis_finance_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5125, Add ellipsis_finance to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a view called 'dexs' that combines data from two different tables, 'StableSwap_evt_TokenExchange' and 'StableSwap_evt_TokenExchangeUnderlying', in the database. It joins these tables with another table called 'ellipsis_finance_bnb_pool_tokens'. The resulting view includes information about token exchanges such as block number, block time, token amounts bought and sold, addresses of the tokens involved, taker and maker addresses, project contract address, transaction hash, and event index. This enables data analysts to analyze token exchange activity on the Ellipsis Finance platform.
MODEL: onepunchswap_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5126, Add onepunchswap to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a query that retrieves data from the 'dexs' table. It selects various columns related to transactions on the 'onepunchswap' project in the 'bnb' blockchain. The query includes information such as block time, block number, token amounts bought and sold, addresses involved in the transaction, taker and maker details, project contract address, transaction hash, and event index. This model enables data analysts to analyze and gain insights into transactions on this specific decentralized exchange platform.
MODEL: openocean_avalanche_c_base_trades.sql
🟢 Added by:
🔧 PR: #5127, Add openocean to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table that extracts data from the 'OpenOceanExchange_evt_Swapped' event in the 'openocean_v2_avalanche_c' database. It retrieves information such as block number, block time, token amounts bought and sold, token addresses, taker and maker addresses, project contract address, transaction hash, and event index. This enables data analysts to analyze trading activity on the OpenOcean platform in Avalanche blockchain.
MODEL: dex_fantom_base_trades.sql
🟠 Modified by:
🔧 PR: #5127, Add openocean to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: In this diff, a reference to the model 'openocean_fantom_base_trades' was added. This reference is included in a list of other models that are being referenced. The rest of the code remains unchanged.
MODEL: openocean_fantom_base_trades.sql
🟢 Added by:
🔧 PR: #5127, Add openocean to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-08
📝 Summary: This SQL model creates a table that extracts data from the 'OpenOceanExchange_evt_Swapped' table in the 'open_ocean_fantom' database. It selects various columns related to token swaps, such as block number, block time, token amounts bought and sold, addresses of tokens involved in the swap, taker and maker addresses, project contract address, transaction hash and event index. This model enables data analysts to analyze token swap activity on the Fantom blockchain using OpenOcean exchange data.
MODEL: [openocean_optimism_base_tra
Beta Was this translation helpful? Give feedback.
All reactions