📰 2023-12-08: Weekly Prophet! #4967
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 39 PRs merged from 22 wizards. Great job everyone! 🎉
We had 95 added models 🟢 and 85 modified models 🟠 for 18 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_aggregator_trades.sql
🟠 Modified by:
🔧 PR: #4959, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: The reference models that were added or removed in the given diff are: Removed: oneinch_ethereum_trades
Added: oneinch_ar_trades
MODEL: dex_aggregator_seed.csv
🟠 Modified by:
🔧 PR: #4959, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: [changes too large] The model dex_aggregator_seed.csv was modified.
MODEL: dex_raw_pool_creations.sql
🟢 Added by:
🔧 PR: #4913, dex.raw_pools upgrade + delete DOBE, RAM and NPXS from prices
🧙 Author: @grkhr on 2023-12-06
📝 Summary: This SQL model creates a dataset that combines information from various blockchains and pools. It includes details such as blockchain type, pool version, pool address, token addresses, creation block time and number, and contract address. The model also handles some specific cases for the 'optimism' blockchain. This dataset enables data analysts to analyze and compare pools across different blockchains for further analysis or reporting purposes.
MODEL: dex_raw_pool_initializations.sql
🟢 Added by:
🔧 PR: #4913, dex.raw_pools upgrade + delete DOBE, RAM and NPXS from prices
🧙 Author: @grkhr on 2023-12-06
📝 Summary: This SQL model creates a view that combines data from multiple blockchains (including Ethereum, Polygon, BNB, and others) to extract information about Uniswap-compatible transactions. It includes details such as the blockchain name, transaction type (v2), version number, block time, pool address ('to'), token0 and token1 addresses extracted from the input field of each transaction. The view is restricted to v2 transactions only and can be used for analysis by data analysts.
MODEL: dex_raw_pools.sql
🟠 Modified by:
🔧 PR: #4913, dex.raw_pools upgrade + delete DOBE, RAM and NPXS from prices
🧙 Author: @grkhr on 2023-12-06
📝 Summary: The main logic added in this diff is a query to get rid of 'degen-pools' that have changed tokens after creation. It selects from the
dex_raw_pool_creationstable and filters out pools that are present in thedex_raw_pool_initializationstable with more than one occurrence.MODEL: dex_arbitrum_sandwiches.sql
🟠 Modified by:
🔧 PR: #4936,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' to specify the blockchain platform. The 'dex_sandwiches' macro is called with parameters including the 'blockchain' variable and a source named 'transactions'. The source for transactions is now dynamically determined based on the value of the 'blockchain' variable.
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: The unique key for the dbt SQL model was changed from ['blockchain','tx_hash', 'project_contract_address', 'evt_index'] to ['blockchain', 'tx_hash', 'project_contract_address', 'evt_index'].
MODEL: dex_avalanche_c_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: In this diff, the main logic that was added is the use of a variable called 'blockchain' to set the value for the parameter 'transactions'. The previous hardcoded value 'avalanche_c' has been replaced with this variable. This change allows for more flexibility in selecting different blockchains when querying transactions data.
MODEL: dex_base_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' to specify the source for transactions. The previous code had a hardcoded value of 'base' for the blockchain, but now it uses the value stored in the 'blockchain' variable. This allows flexibility to change or customize the blockchain source without modifying multiple places in the code.
MODEL: dex_bnb_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' to set the value 'bnb'. This variable is then used as an argument in the dex_sandwiches macro, along with another argument 'transactions'. The source function is modified to use the blockchain variable as its first argument.
MODEL: dex_ethereum_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' to specify the blockchain type. The value of this variable is set as 'ethereum'. The source function is then used to retrieve transactions from the specified blockchain using the 'blockchain' variable.
MODEL: dex_fantom_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' to dynamically set the value for the blockchain parameter in the dex_sandwiches macro. The previous hardcoded value 'fantom' has been replaced with this variable, allowing flexibility to change it easily. Additionally, instead of hardcoding 'fantom' as a source for transactions, now it uses the blockchain variable to determine which source table should be used.
MODEL: dex_gnosis_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: In this diff, the main logic that was added is the use of a variable called 'blockchain' to set the value of a parameter in a dbt SQL model. The previous hardcoded value for 'blockchain' was replaced with this variable, allowing for more flexibility and reusability. Additionally, the source function now uses this variable as an argument to retrieve data from different sources based on its value.
MODEL: dex_optimism_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: In this SQL model, the variable
blockchainis set to 'optimism'. Thedex_sandwichesmacro is called with the following parameters:blockchainparameter is set to the value of theblockchainvariable.transactionsparameter is sourced from a table named 'transactions' in the specified blockchain.MODEL: dex_polygon_sandwiches.sql
🟠 Modified by:
🔧 PR: #4943,
dex.sandwichesoptimisations & updates🧙 Author: @hildobby on 2023-12-05
📝 Summary: The main logic added in this SQL model is the use of a variable called 'blockchain' which is set to 'polygon'. The dex_sandwiches function is then called with the parameters blockchain and transactions. The value of blockchain parameter is set using the variable, while the transactions parameter uses another source function with the same blockchain variable as an argument.
MODEL: dex_schema.yml
🟠 Modified by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: [changes too large] The model dex_schema.yml was modified.
MODEL: dex_arbitrum_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a table called 'dex_atomic_arbitrages' that enables data analysts to analyze and track atomic arbitrage transactions on the specified blockchain (in this case, Arbitrum). The model takes in transaction data from the source table and processes it to provide insights into arbitrage opportunities.
MODEL: dex_avalanche_c_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a table called 'dex_atomic_arbitrages' that enables data analysts to analyze atomic arbitrage transactions on the Avalanche blockchain. The model takes in a parameter for the blockchain and uses a source table called 'transactions' as input.
MODEL: dex_base_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables the analysis of atomic arbitrage transactions in a blockchain. It uses the 'dex_atomic_arbitrages' function to extract data from the 'transactions' table in the specified blockchain. This allows data analysts to analyze and understand arbitrage opportunities within the blockchain network.
MODEL: dex_bnb_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables the analysis of atomic arbitrage transactions in a specific blockchain (bnb). It uses the
dex_atomic_arbitragesfunction to extract data from thetransactionstable in that blockchain.MODEL: dex_celo_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a table called 'dex_atomic_arbitrages' that enables data analysts to analyze atomic arbitrage transactions on the Celo blockchain. It takes in transaction data from the 'transactions' table and filters it based on the specified blockchain (in this case, Celo).
MODEL: dex_ethereum_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a table called 'dex_atomic_arbitrages' that enables data analysts to analyze atomic arbitrage transactions on the Ethereum blockchain. The model takes in transaction data from the source table and processes it to provide insights into arbitrage opportunities within decentralized exchanges.
MODEL: dex_fantom_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables the analysis of atomic arbitrage transactions in a specific blockchain (in this case, Fantom). It retrieves transaction data from the specified source and processes it to identify potential arbitrage opportunities. This allows data analysts to analyze and understand the dynamics of atomic arbitrage within the given blockchain.
MODEL: dex_gnosis_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to analyze atomic arbitrage transactions on the Gnosis blockchain. It uses the 'dex_atomic_arbitrages' function with parameters for the specified blockchain ('gnosis') and a source of transactions from that blockchain.
MODEL: dex_optimism_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to analyze atomic arbitrage transactions on the specified blockchain (in this case, 'optimism'). It retrieves transaction data from the source table and performs calculations or analysis on it.
MODEL: dex_polygon_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables the analysis of atomic arbitrage transactions on the Polygon blockchain. It uses a source table called 'transactions' from the specified blockchain to extract relevant data for further analysis by data analysts.
MODEL: dex_zksync_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a table called 'dex_atomic_arbitrages' that enables data analysts to analyze atomic arbitrage transactions on the specified blockchain (in this case, zksync). The table is populated with data from the 'transactions' source table.
MODEL: dex_atomic_arbitrages.sql
🟢 Added by:
🔧 PR: #4638, Create
dex.atomic_arbitrages🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a union of multiple tables that contain data on arbitrage transactions across different blockchains. It retrieves various attributes related to each transaction, such as block time, transaction hash, token symbols and addresses, amounts traded, USD value, and involved parties. This model enables data analysts to analyze and compare arbitrage activity across different blockchain networks.
MODEL: dex_arbitrum_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to analyze transactions in a specific blockchain (arbitrum) by sandwiching them with relevant data from a decentralized exchange (DEX). It leverages the 'dex_sandwiched' function to combine transaction and sandwich data for analysis.
MODEL: dex_avalanche_c_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables a sandwiched DEX table for the specified blockchain. It uses the transactions data from the source table to populate the sandwiches table, which can be used by data analysts for analysis and reporting purposes.
MODEL: dex_base_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables a sandwiched view of transactions in the blockchain. It takes the transactions data from the specified blockchain and combines it with a reference to a pre-existing sandwiched table, creating an updated view for data analysts to work with.
MODEL: dex_bnb_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables a sandwiched view for a specified blockchain (in this case, 'bnb'). It uses the transactions data from the source table and combines it with the sandwiches data from another reference table ('dex_bnb_sandwiches') to create a new view. This allows data analysts to analyze and work with sandwiched transaction data specific to the chosen blockchain.
MODEL: dex_ethereum_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to analyze transactions in the Ethereum blockchain. It uses a function called 'dex_sandwiched' to process the transactions and generate sandwich data, which can be further analyzed for insights.
MODEL: dex_fantom_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables a sandwiched view for the specified blockchain (in this case, 'fantom'). It uses the transactions data from that blockchain and combines it with an existing reference table called 'dex_fantom_sandwiches'. This allows data analysts to easily analyze and work with sandwiched data in their analysis.
MODEL: dex_gnosis_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to analyze transactions in the Gnosis blockchain. It uses a function called 'dex_sandwiched' that takes the Gnosis blockchain as input, along with transaction data from that blockchain, and references a table called 'dex_gnosis_sandwiches'. The purpose of this model is to provide insights into sandwich attacks or manipulations happening within the Gnosis decentralized exchange.
MODEL: dex_optimism_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to generate sandwiched DEX transactions for the specified blockchain (in this case, 'optimism'). It uses a source table for transaction data and references another table ('dex_optimism_sandwiches') to produce the desired output.
MODEL: dex_polygon_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates and enables data analysts to generate sandwiched transaction data for a specific blockchain (in this case, Polygon). It takes in transaction data from the specified blockchain and uses it to create sandwiched transactions, which are then stored in a reference table. This allows analysts to analyze and study the patterns of these sandwiched transactions on the specified blockchain.
MODEL: dex_sandwiched.sql
🟢 Added by:
🔧 PR: #4936, Create
dex_sandwiched🧙 Author: @hildobby on 2023-12-05
📝 Summary: This SQL model creates a union of multiple sandwiched models, allowing data analysts to query and analyze data from various blockchain projects. The resulting dataset includes information such as blockchain, project, version, block time and number, token addresses and symbols, transaction details (hashes, sender/receiver), contract addresses, token pairs traded in transactions,and amounts in different currencies. This enables analysts to gain insights into decentralized exchanges across different blockchains.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_pools_gnosis.sql
🟠 Modified by:
🔧 PR: #4908, [EASY] Adds missing contract to labels_balancer_v2_pools_gnosis.sql
🧙 Author: @viniabussafi on 2023-12-07
📝 Summary: The added logic in this SQL model includes selecting specific columns from two different sources and performing calculations on them. It also involves joining the sources based on certain conditions and using cross joins to unnest arrays. Additionally, there is a conditional statement that filters the data based on a date range if it is an incremental update. The result of this logic is then unioned with another select statement from a different source.
MODEL: labels_bridges_bnb.sql
🟢 Added by:
🔧 PR: #4846, bnb bridges [FOR REVIEW]
🧙 Author: @RantumBits on 2023-12-07
📝 Summary: This SQL model creates a table that includes information about various bridges in the blockchain. It provides details such as the blockchain name, address, bridge name, category, contributor, source of data, creation and update dates of the bridge record. The model_name and label_type columns are also included in this table. This enables data analysts to analyze and query information related to bridges on different blockchains.
MODEL: labels_bridges.sql
🟠 Modified by:
🔧 PR: #4846, bnb bridges [FOR REVIEW]
🧙 Author: @RantumBits on 2023-12-07
📝 Summary: In this SQL model, a new bridge model called 'labels_bridges_bnb' was added to the list of existing bridge models. The '-' symbol indicates that something was removed, but it is not clear what exactly was removed as there is an empty line after the '-' symbol. The SELECT statement at the end selects all columns from these bridge models.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: Sorry, but I can't assist with summarizing a SQL model without the actual code. Could you please provide the complete SQL model?
MODEL: tokens_arbitrum_nft_curated.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: [changes too large] The model tokens_arbitrum_nft_curated.sql was modified.
MODEL: tokens_avalanche_c_nft_curated.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: [changes too large] The model tokens_avalanche_c_nft_curated.sql was modified.
MODEL: tokens_bnb_bep20.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: In the given SQL model, a SELECT statement is used to retrieve data from the columns 'contract_address', 'symbol', and 'decimals'. The data is selected from a temporary table created using the VALUES clause.
MODEL: tokens_celo_erc20.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: I'm sorry, but I cannot summarize the SQL model without having access to the actual code. Please provide me with the diff of the dbt SQL model so that I can assist you in creating a comma-separated list of added or removed token symbols.
MODEL: tokens_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #4870, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: The token symbols that were added or removed in the diff are: ROCK, SHIBA6900
🔧 PR: #4870, add GYD to tokens.erc20
🧙 Author: @fmarrr on 2023-12-05
📝 Summary: The token symbols that were added or removed in the diff of the SQL model are: GYD
🔧 PR: #4870, [EASY] Add missing mainnet tokens
🧙 Author: @harisang on 2023-12-01
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
MODEL: tokens_fantom_erc20.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: Sorry, but I can't assist with summarizing a SQL model without the actual code. Could you please provide the complete SQL model?
MODEL: tokens_fantom_nft_curated.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: [changes too large] The model tokens_fantom_nft_curated.sql was modified.
MODEL: tokens_polygon_erc20.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: Sorry, but I can't assist with summarizing a SQL model without the actual code.
MODEL: tokens_polygon_nft_curated.sql
🟠 Modified by:
🔧 PR: #4762, erc20 & nft token additions
🧙 Author: @tomfutago on 2023-12-07
📝 Summary: [changes too large] The model tokens_polygon_nft_curated.sql was modified.
MODEL: tokens_ethereum_erc20_stablecoins.sql
🟠 Modified by:
🔧 PR: #4948, add GYD to tokens.erc20
🧙 Author: @fmarrr on 2023-12-05
📝 Summary: In this SQL model, a new row has been added to the existing table. The new row includes information about a contract address, symbol, decimals, and name for a currency called 'GYD' (Gyro Dollar).
MODEL: tokens_solana_fungible.sql
🟠 Modified by:
🔧 PR: #4919, Fixing orca whirlpool fees
🧙 Author: @andrewhong5297 on 2023-12-05
📝 Summary: The tokens symbols that were added or removed in the diff of the SQL model are:
SECTOR: prices
toggle to see all model updates
MODEL: prices_avalanche_c_tokens.sql
🟠 Modified by:
🔧 PR: #4965, fix tokens prices
🧙 Author: @grkhr on 2023-12-07
📝 Summary: The token symbols that were added or removed are: USDT, USDC
MODEL: prices_polygon_tokens.sql
🟠 Modified by:
🔧 PR: #4947, fix tokens prices
🧙 Author: @grkhr on 2023-12-07
📝 Summary: The token symbols that were added or removed are: WMATIC, TEL, MANA
🔧 PR: #4947, Update prices_polygon_tokens.sql
🧙 Author: @peterrliem on 2023-12-06
📝 Summary: The token symbols that were added or removed are: COMP, VOXEL, GTC
🔧 PR: #4947, Update prices_polygon_tokens.sql
🧙 Author: @peterrliem on 2023-12-05
📝 Summary: The added token symbols are: GMT
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #4955, Update GMT Token information
🧙 Author: @sepivip on 2023-12-07
📝 Summary: The token symbols that were added or removed are: 'GMT'
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #4945, Update GMT Token information
🧙 Author: @sepivip on 2023-12-07
📝 Summary: The token symbols that were added or removed are: GMT, GMT
🔧 PR: #4945, dex.raw_pools upgrade + delete DOBE, RAM and NPXS from prices
🧙 Author: @grkhr on 2023-12-06
📝 Summary: The token symbols that were added or removed are: NPXS, DOBE, RAM
🔧 PR: #4945, Update prices_ethereum_tokens.sql
🧙 Author: @pdotall on 2023-12-05
📝 Summary: The token symbols that were added or removed are: GEAR
MODEL: prices_solana_tokens.sql
🟠 Modified by:
🔧 PR: #4955, Update GMT Token information
🧙 Author: @sepivip on 2023-12-07
📝 Summary: The token symbols that were added or removed are: FTT, FORGE, STEPN-GMT
SECTOR: oneinch
toggle to see all model updates
MODEL: oneinch_ethereum_schema.yml
🟠 Modified by:
🔧 PR: #4959, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: [changes too large] The model oneinch_ethereum_schema.yml was modified.
MODEL: oneinch_uniswap_v3_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4959, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: [changes too large] The model oneinch_uniswap_v3_ethereum_trades.sql was removed.
MODEL: oneinch_ar_trades.sql
🟢 Added by:
🔧 PR: #4944, 1inch: 1inch AR Trades view
🧙 Author: @max-morrow on 2023-12-06
📝 Summary: This SQL model creates a dataset that provides information on trades made using the 1inch protocol. It includes details such as the blockchain, project version, block date and time, token symbols and amounts bought/sold, USD value of the trade, addresses of tokens involved in the trade, user/taker information, contract address used for the trade transaction,and trace address.
🟠 Modified by:
🔧 PR: #4944, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: In this diff, the following changes were made to the SQL model: - The 'calls' CTE was removed.
MODEL: oneinch_swaps.sql
🟢 Added by:
🔧 PR: #4900, 1inch: 1inch swaps view
🧙 Author: @max-morrow on 2023-12-04
📝 Summary: This SQL model creates a dataset that combines data from multiple tables to provide information on trades made using the Oneinch protocol. It includes details such as blockchain, transaction hash, call trace address, block time, minute of trade occurrence, user and receiver addresses involved in the trade, token addresses and symbols for source and destination tokens used in the trade. Additionally, it calculates USD amounts for trades based on token prices and provides information on transfers associated with each trade.
🟠 Modified by:
🔧 PR: #4900, 1inch: dex_aggregator.trades cleanup
🧙 Author: @grkhr on 2023-12-07
📝 Summary: [changes too large] The model oneinch_swaps.sql was modified.
🔧 PR: #4900, 1inch: 1inch AR Trades view
🧙 Author: @max-morrow on 2023-12-06
📝 Summary: In this SQL model, the following changes were made:
MODEL: oneinch_lop.sql
🟠 Modified by:
🔧 PR: #4900, 1inch: 1inch swaps view
🧙 Author: @max-morrow on 2023-12-04
📝 Summary: The added logic includes selecting multiple columns from a table named 'oneinch_' + blockchain + '_lop' for each blockchain in the loop. The selected columns include information related to block time, transaction hash, sender and receiver addresses, contract details, protocol version, method details, maker and taker information with their respective assets and amounts traded. Additional information such as order hash, call success status, gas used during the call execution is also included. Finally minute and block month are selected as well.
SECTOR: bridges
toggle to see all model updates
MODEL: bridges_ethereum_addresses.sql
🟠 Modified by:
🔧 PR: #4920, Add OP SNX - Update bridges_ethereum_addresses.sql
🧙 Author: @MSilb7 on 2023-12-07
📝 Summary: In this SQL model, a few lines were added and removed. The line that was removed is commented out and it seems to be a duplicate entry that was renamed. The lines that were added include new values for the blockchain, address, bridge_name, and description columns. These new values represent different bridges such as SynthetixBridgeToOptimism, ERC20 Bridge on Polygon network, zkSync Lite Bridge on zkSync network etc.
MODEL: bridges_bnb_addresses.sql
🟢 Added by:
🔧 PR: #4846, bnb bridges [FOR REVIEW]
🧙 Author: @RantumBits on 2023-12-07
📝 Summary: This SQL model creates a table that includes information about various blockchain bridges. It provides data analysts with the ability to query and analyze details such as the blockchain, address, bridge name, and description of each bridge.
SECTOR: evms
toggle to see all model updates
MODEL: evms_info.sql
🟠 Modified by:
🔧 PR: #4934, Add known op stack mainnets to evms.info
🧙 Author: @MSilb7 on 2023-12-07
📝 Summary: The diff of the SQL model shows that several rows were added to the existing table. These new rows include information about different Layer 2 solutions such as Mode, Orderly Network, Lyra, Manta Pacific, opBNB, Kroma, DeBank and Rollux. Each row includes details like chain ID, blockchain name, chain type (Layer 2), rollup type (Optimistic Rollup), native token symbol (ETH), explorer link and timestamp for when it was added.
SECTOR: curvefi
toggle to see all model updates
MODEL: curvefi_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4963, add stableswap curvefi
🧙 Author: @andrewhong5297 on 2023-12-07
📝 Summary: The main logic that was added in this diff is the inclusion of two additional versions ('Factory V1 Stableswap Plain' and 'Factory V1 Stableswap Meta') in the join condition. This means that the model will now include data from these two versions along with the existing ones ('Factory V1 Meta', 'Factory V1 Plain', and 'Regular').
MODEL: curvefi_ethereum_view_pools.sql
🟠 Modified by:
🔧 PR: #4963, add stableswap curvefi
🧙 Author: @andrewhong5297 on 2023-12-07
📝 Summary: In this SQL model, the main logic that was added includes:
SECTOR: balancer
toggle to see all model updates
MODEL: balancer_v1_ethereum_liquidity.sql
🟠 Modified by:
🔧 PR: #4880, Fix for balancer_v1_ethereum_liquidity.sql
🧙 Author: @viniabussafi on 2023-12-07
📝 Summary: The logic that was removed from the SQL model includes:
MODEL: balancer_v2_arbitrum_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a Balancer protocol fee macro for the specified blockchain (Arbitrum) and version (2). It allows data analysts to calculate fees associated with the Balancer protocol on the given blockchain.
MODEL: balancer_v2_avalanche_c_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This dbt SQL model creates and enables a macro called 'balancer_protocol_fee_macro'. It takes in parameters for the blockchain and version, allowing data analysts to calculate protocol fees for the Balancer protocol on the specified blockchain.
MODEL: balancer_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates a view that combines data from multiple Balancer V2 protocol fee tables. It includes information such as the day, pool ID, pool address, token address and symbol, token amount in raw and formatted values, protocol fee collected in USD, treasury share percentage, and treasury revenue in USD. This enables data analysts to easily access and analyze aggregated protocol fee data across different blockchain networks supported by Balancer V2.
MODEL: balancer_v2_base_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a macro called 'balancer_protocol_fee_macro' that calculates the protocol fee for the Balancer blockchain. It takes in parameters such as the blockchain version and returns the calculated fee.
MODEL: balancer_v2_ethereum_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a macro called 'balancer_protocol_fee_macro' that calculates the protocol fee for the specified blockchain (in this case, Ethereum) using version 2 of the protocol. This macro can be used by data analysts to analyze and calculate fees related to Balancer Protocol transactions on Ethereum.
MODEL: balancer_v2_gnosis_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a macro called 'balancer_protocol_fee_macro' that calculates the protocol fee for the specified blockchain (in this case, 'gnosis') and version ('2'). This macro can be used by data analysts to calculate protocol fees in their analysis.
MODEL: balancer_v2_optimism_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a macro called 'balancer_protocol_fee_macro' that calculates the protocol fee for the specified blockchain (in this case, 'optimism') and version ('2'). This macro can be used by data analysts to easily calculate the protocol fee in their analysis.
MODEL: balancer_v2_polygon_protocol_fee.sql
🟢 Added by:
🔧 PR: #4797, Balancer Protocol Fees Spell
🧙 Author: @viniabussafi on 2023-12-04
📝 Summary: This SQL model creates and enables a Balancer protocol fee macro for data analysts. It allows them to calculate the fees associated with the Balancer protocol on the Polygon blockchain version 2.
MODEL: balancer_v1_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4942, Balancer Spell Explorer Clean Up
🧙 Author: @thetroyharris on 2023-12-04
📝 Summary: The diff shows that a LEFT JOIN condition was removed from the model. The condition checked if the contract address in the 'prices' table matched with the 'token_sold_address' column in the 'trades' table.
SECTOR: rollup_economics
toggle to see all model updates
MODEL: l1_data_fees.sql
🟠 Modified by:
🔧 PR: #4857, Add scroll and linea to rollup_economics
🧙 Author: @lorenz234 on 2023-12-07
📝 Summary: In this SQL model, two new sections have been added. The first section retrieves data from the 'ethereum.transactions' table for a specific address and filters based on certain conditions such as block time and data content. It also joins with the 'prices.usd' table to calculate gas spent in USD. The second section is similar to the first but retrieves data for a different address and different data content. These additions are part of a larger query that includes other sections not shown here.
🔧 PR: #4857, Update Rollup Economics
🧙 Author: @Jam516 on 2023-12-04
📝 Summary: In the given SQL model, the following changes were made: 1. A new column 'gas_used' was added to the CTE 'tx_batch_appends'.
2. The WHERE clause in another CTE 'op' was modified to include additional protocol names.
3. The alias of a column was changed from 'input_length' to 'data_length'.
4. The SELECT statement at the end of the model now includes an additional column for gas_used. These changes involve adding and modifying columns related to gas usage and data length in transactions, as well as updating protocol name filters and aliases for clarity.
MODEL: l1_verification_fees.sql
🟠 Modified by:
🔧 PR: #4847, Add scroll and linea to rollup_economics
🧙 Author: @lorenz234 on 2023-12-07
📝 Summary: The added logic in this SQL model includes a UNION ALL statement that selects data from two tables, 'ethereum.transactions' and 'prices.usd'. It joins these tables on specific conditions such as matching timestamps and addresses. Additionally, it calculates values based on the selected columns using mathematical operations. The final result is stored in the 'verify_txns' CTE (Common Table Expression).
MODEL: l2_revenue.sql
🟠 Modified by:
🔧 PR: #4857, Update Rollup Economics
🧙 Author: @Jam516 on 2023-12-04
📝 Summary: The added logic includes grouping the results by two columns, 'day' and 'name', and performing a UNION ALL operation. It also calculates the values for 'l2_rev' and 'l2_rev_usd' based on certain conditions using CASE statements. The model joins two sources, 'zora' and 'prices', on specific conditions related to block time and symbol. There are additional conditional statements that filter the data based on incremental predicates or a specific date when Zora network launched. Finally, it groups the results again by two columns before returning them.
SECTOR: tokenlon
toggle to see all model updates
MODEL: tokenlon_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #4862, add tokenlon rfqv2 trades
🧙 Author: @0xkeen on 2023-12-07
📝 Summary: The line
ref('tokenlon_v5_ethereum_rfq_v2_trades'),was added to the model.MODEL: tokenlon_v5_ethereum_rfq_v2_trades.sql
🟢 Added by:
🔧 PR: #4862, add tokenlon rfqv2 trades
🧙 Author: @0xkeen on 2023-12-07
📝 Summary: This SQL model creates a dataset that enables data analysts to analyze decentralized exchange (DEX) transactions. It includes information such as the blockchain, project, version, block date and time, token symbols and amounts bought/sold in various currencies. It also provides details about the taker, maker, project contract address, transaction hash and trace address. The model joins multiple tables to retrieve additional information about tokens and prices for analysis purposes.
SECTOR: _sector
toggle to see all model updates
MODEL: contracts_predeploys.sql
🟠 Modified by:
🔧 PR: #4878, Simplify Predeploys For OP Chains in Contracts Mapping
🧙 Author: @MSilb7 on 2023-12-07
📝 Summary: The main logic added in this SQL model is the retrieval of contracts from the
contracts_system_predeploystable. The retrieved contracts are then assigned values for various columns such as blockchain, contract address, contract project, contract name, created time, and source. These contracts are ranked based on their partitioned blockchain and contract address using theROW_NUMBER()function.MODEL: contracts_system_predeploys.sql
🟠 Modified by:
🔧 PR: #4878, Simplify Predeploys For OP Chains in Contracts Mapping
🧙 Author: @MSilb7 on 2023-12-07
📝 Summary: The added logic in this SQL model includes the following:
MODEL: dex_polygon_base_trades.sql
🟠 Modified by:
🔧 PR: #4895, Added quickswap to Base trades
🧙 Author: @nyssarex on 2023-12-06
📝 Summary: In this diff, two references to SQL models were added: 'quickswap_v2_polygon_base_trades' and 'quickswap_v3_polygon_base_trades'. These models are now included in the base_union common table expression.
MODEL: quickswap_v2_polygon_base_trades.sql
🟢 Added by:
🔧 PR: #4895, Added quickswap to Base trades
🧙 Author: @nyssarex on 2023-12-06
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the QuickSwap platform, which is compatible with Uniswap V2. The table includes information about swaps and pair creations on the Polygon blockchain.
MODEL: quickswap_v3_polygon_base_trades.sql
🟢 Added by:
🔧 PR: #4895, Added quickswap to Base trades
🧙 Author: @nyssarex on 2023-12-06
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the QuickSwap decentralized exchange on the Polygon blockchain. It pulls data from two sources, 'quickswap_v3_polygon' for swap events and pool creation events. The model does not include any optional columns.
MODEL: dex_arbitrum_base_trades.sql
🟠 Modified by:
🔧 PR: #4867, Add Trader Joe v2.1 on Avalanche to dex.trades and dex.trades_beta
🧙 Author: @chef-seaweed on 2023-12-06
📝 Summary: In this diff, two references to SQL models were added: 'trader_joe_v2_arbitrum_base_trades' and 'trader_joe_v2_1_arbitrum_base_trades'. These references are included in a list of other model references.
🔧 PR: #4867, Add camelot to
dex.trades_beta🧙 Author: @tomfutago on 2023-12-01
📝 Summary: In this diff, three new base models were added: 'camelot_v2_arbitrum_base_trades', 'camelot_v3_arbitrum_base_trades', and 'uniswap_v3_arbitrum_base_trades'. These models are being referenced along with the existing base models in the set variable called 'base_models'.
MODEL: trader_joe_v2_1_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4859, Add Trader Joe v2.1 on Avalanche to dex.trades and dex.trades_beta
🧙 Author: @chef-seaweed on 2023-12-06
📝 Summary: This SQL model creates a table called 'trader_joe_compatible_v2_1_trades' that enables data analysts to analyze trades on the Trader Joe platform. The table includes information from two sources: 'Pair_evt_Swap' and 'Factory_evt_PoolCreated'. It specifies that the blockchain is 'arbitrum', the project is 'trader_joe', and the version is '2.1'.
MODEL: trader_joe_v2_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4859, Add Trader Joe v2.1 on Avalanche to dex.trades and dex.trades_beta
🧙 Author: @chef-seaweed on 2023-12-06
📝 Summary: This SQL model creates a table called 'trader_joe_compatible_v2_trades' that enables data analysts to analyze trades on the Trader Joe platform. The table is populated with data from two sources: 'Pair_evt_Swap' and 'Factory_evt_PoolCreated'. The trades are specific to the Arbitrum blockchain and version 2 of the Trader Joe project.
MODEL: dex_avalanche_c_base_trades.sql
🟠 Modified by:
🔧 PR:
Beta Was this translation helpful? Give feedback.
All reactions