📰 2024-01-19: Weekly Prophet! #5191
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 27 PRs merged from 16 wizards. Great job everyone! 🎉
We had 58 added models 🟢 and 72 modified models 🟠 for 16 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_trades_seed.csv
🟠 Modified by:
🔧 PR: #5129, Update dexs to use
generic_spot_v2_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: [changes too large] The model dex_trades_seed.csv was modified.
MODEL: dex_info.sql
🟠 Modified by:
🔧 PR: #5166, Fix cowswap name & add Solana DEXs to dex.info
🧙 Author: @hildobby on 2024-01-18
📝 Summary: In this SQL model, the following changes were made: - The entry for '0x API' in the first VALUES block was changed to 'zeroex'.
🔧 PR: #5166, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: In the given SQL model, the following values were added to a table: 'chronos', 'zyberswap', and 'solidlizard'. These values represent different projects or entities with corresponding names, types, and identifiers.
🔧 PR: #5166, Update dex info
🧙 Author: @Hosuke on 2024-01-16
📝 Summary: In the given SQL model, several rows were added to a temporary table called 'temp_table'. The added rows include projects named 'pharaoh', 'ramses', 'scale', and 'baseswap' with their corresponding names, marketplace types, and x_usernames.
MODEL: dex_aggregator_trades.sql
🟠 Modified by:
🔧 PR: #5156, Added arbitrum for yield_yak (including to dex aggregator)
🧙 Author: @yy-analytics on 2024-01-16
📝 Summary: The reference models that were added or removed in the given diff are:
SECTOR: labels
toggle to see all model updates
MODEL: labels_system_addresses.sql
🟠 Modified by:
🔧 PR: #5164, Add BNB System Addresses & Handle for OP Chains
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: The main logic added in this SQL model is the creation of a new table called 'curated_addresses' using a WITH statement. This table selects data from another table and adds additional rows based on a loop over all_op_chains(). The final result is obtained by performing a UNION ALL between the 'curated_addresses' table and another query that joins with the 'contracts_system_predeploys' table to add more rows if they don't already exist in the 'curated_addresses' table.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #5140, adding new avalanche c chain tokens to tokens.erc20
🧙 Author: @cryptomachia on 2024-01-19
📝 Summary: The added token symbols are GEC, LIZARD, WOLF, RPG, SUBAVA, ROCKET, BEAR and MICRO.
🔧 PR: #5140, Adding neadPHAR, xPHAR, FRAX, BINGO, DWC, and KRBY to tokens_avalanch…
🧙 Author: @discochuck on 2024-01-12
📝 Summary: The added token symbols are: neadPHAR, BINGO, DWC, KRBY, xPHAR.
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #5185, Adding DEUS to tokens_arbitrum_erc20.sql
🧙 Author: @discochuck on 2024-01-19
📝 Summary: The token symbols that were added or removed in the diff of the SQL model are: Added: DEUS
MODEL: tokens_goerli_erc20.sql
🟢 Added by:
🔧 PR: #5160, Add Goerli Token Tables
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: This SQL model creates a temporary table called 'temp_table' with columns for contract_address, symbol, and decimals. It selects the values from this table and renames the contract_address column as 'contract_address'. This model enables data analysts to retrieve information about a specific contract address, its associated symbol, and decimal places.
MODEL: tokens_goerli_nft.sql
🟢 Added by:
🔧 PR: #5160, Add Goerli Token Tables
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: This SQL model creates a query that retrieves contract addresses, names, symbols, and standards from two tables: 'tokens_goerli_nft_standards' and 'tokens_goerli_nft_curated'. It enables data analysts to analyze and compare different token standards in the Goerli network.
MODEL: tokens_goerli_nft_curated.sql
🟢 Added by:
🔧 PR: #5160, Add Goerli Token Tables
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: This SQL model creates a temporary table called 'temp_table' with columns for contract_address, name, and symbol. It inserts one row of data into the table with specific values for each column. This model enables data analysts to query and analyze information related to wrapped Cryptopunks contracts using the contract address, name, and symbol as key attributes.
MODEL: tokens_goerli_nft_standards.sql
🟢 Added by:
🔧 PR: #5160, Add Goerli Token Tables
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: This dbt SQL model creates a query that selects the contract address and the maximum token standard for each block time from a table called 'nft_goerli_transfers'. It also includes an optional incremental predicate to filter the results based on block time. The model enables data analysts to retrieve information about contract addresses and their corresponding maximum token standards within specific block times.
MODEL: tokens_polygon_erc20.sql
🟠 Modified by:
🔧 PR: #5147, Added circle USDC to tokens_polygon_erc20.sql
🧙 Author: @discochuck on 2024-01-12
📝 Summary: The token symbols that were added or removed are: DAI, MATIC, USDC.e, USDT, WBTC, WETH for the added tokens and USDC for the removed token.
SECTOR: prices
toggle to see all model updates
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #5189, feat: prices - added O3 Swap Token
🧙 Author: @melenxyz on 2024-01-19
📝 Summary: The token symbols that were added or removed in the diff are: O3
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #5165, Update prices_ethereum_tokens.sql
🧙 Author: @peterrliem on 2024-01-16
📝 Summary: GENE, RBC, MAGIC, PREMIA, STFX, FLUX
🔧 PR: #5165, Update prices_ethereum_tokens.sql
🧙 Author: @web3dev-eth on 2024-01-16
📝 Summary: The token symbols that were added or removed are: HILO, PEAR, DINERO, JBOT
MODEL: prices_tokens.sql
🟠 Modified by:
🔧 PR: #5082, Added new spell prices_unsupported_chains_non_native_tokens.sql for P…
🧙 Author: @cryptokoryo on 2024-01-15
📝 Summary: The reference models that were added or removed in the diff are: prices_bitcoin_tokens, prices_cardano_tokens.
SECTOR: _sector
toggle to see all model updates
MODEL: dex_avalanche_c_base_trades.sql
🟠 Modified by:
🔧 PR: #5139, Update dexs to use
generic_spot_v2_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, a reference to the model 'woofi_avalanche_c_base_trades' was added.
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: The model added a reference to 'curvefi_avalanche_c_base_trades' in addition to the existing references.
MODEL: dex_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5166, Update dexs to use
generic_spot_v2_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, a reference to the model 'woofi_bnb_base_trades' was added.
🔧 PR: #5166, Update dex info
🧙 Author: @Hosuke on 2024-01-16
📝 Summary: A reference to a dbt SQL model called 'onepunchswap_bnb_base_trades' was added. Additionally, a common table expression (CTE) named 'base_union' was created, which selects all columns from an unspecified source and assigns it to the CTE.
MODEL: wombat_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5129, Update dexs to use
generic_spot_v2_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: The added logic includes a common table expression (CTE) named 'dexs'. This CTE selects various columns from multiple swap event tables and combines them using the UNION ALL operator. The selected columns include block number, block time, token bought amount, token sold amount, token addresses for buying and selling tokens, transaction hash, event index, taker address (to), maker address (null value), and project contract address. There are also conditional statements to filter the data based on incremental updates.
MODEL: woofi_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5129, Update dexs to use
generic_spot_v2_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: The main logic that was removed from the SQL model is an incremental predicate condition for the first SELECT statement. Additionally, a UNION ALL clause and a second SELECT statement were also removed. The main logic that was added includes selecting specific columns and renaming them in the remaining SELECT statement.
MODEL: lending_arbitrum_base_borrow.sql
🟠 Modified by:
🔧 PR: #4899, Add compound to
lending.borrow🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, a new reference to the model 'compound_v3_arbitrum_base_borrow' was added alongside the existing reference to 'aave_v3_arbitrum_base_borrow'.
MODEL: lending_base_base_borrow.sql
🟠 Modified by:
🔧 PR: #4899, Add compound to
lending.borrow🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, a reference to the model 'compound_v3_base_base_borrow' was added alongside the existing reference to 'aave_v3_base_base_borrow'.
MODEL: lending_ethereum_base_borrow.sql
🟠 Modified by:
🔧 PR: #4899, Add compound to
lending.borrow🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, two references were added to the
modelslist:compound_v2_ethereum_base_borrowandcompound_v3_ethereum_base_borrow. The reference toaave_v3_ethereum_base_borrowwas also added back after being removed in a previous change.MODEL: lending_borrow.sql
🟠 Modified by:
🔧 PR: #4899, Add compound to
lending.borrow🧙 Author: @tomfutago on 2024-01-19
📝 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_polygon_base_borrow.sql
🟠 Modified by:
🔧 PR: #4899, Add compound to
lending.borrow🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this diff, a new reference to the model 'compound_v3_polygon_base_borrow' was added.
MODEL: carbonhood_celo_base_trades.sql
🟠 Modified by:
🔧 PR: #5108, Update 4x
dex.trades_betaspells to usegeneric_spot_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: The added logic includes a select statement that retrieves specific columns from the 'carbonhood_celo' table. The values for blockchain, project, version, and source_evt_swap are hardcoded. The logic also includes a function call to 'generic_spot_compatible_trades' with parameters for blockchain, project, version, and source_evt_swap.
MODEL: mento_v2_celo_base_trades.sql
🟠 Modified by:
🔧 PR: #5108, Update 4x
dex.trades_betaspells to usegeneric_spot_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: The added logic in this SQL model is a call to the
generic_spot_compatible_tradesmacro with specific parameters. This macro generates a select statement that retrieves data from theBroker_evt_Swaptable in themento_celosource. The selected columns include information about blockchain, project, version, block month and date, block time and number, taker trader address, token amounts bought and sold (raw), USD amount (null), token addresses for buying and selling tokens, project contract addresss , transaction hash (tx_hash), and event index.MODEL: mummy_finance_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5108, Update 4x
dex.trades_betaspells to usegeneric_spot_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: The added logic includes a new SQL query that uses the
generic_spot_compatible_tradesmacro. It sets the blockchain, project, and version values and retrieves data from themummy_finance_optimism.Router_evt_Swaptable. The selected columns include block time, block number, token bought/sold amounts and addresses, taker/maker information, project contract address, transaction hash, and event index.MODEL: sushiswap_v1_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5108, Update 4x
dex.trades_betaspells to usegeneric_spot_compatible_tradesmacro🧙 Author: @tomfutago on 2024-01-19
📝 Summary: In this SQL model, a new CTE called 'dexs_constant_product_pool' was added. It uses the 'generic_spot_compatible_trades' function to generate trades for the Constant Product Pool in Sushiswap on the Optimism blockchain. The existing CTE 'dexs_stable_pool' remains unchanged and generates trades for the Stable Pool in Sushiswap on Optimism. The final SELECT statement combines data from both pools using UNION ALL to create a unified result set with information about block time, block number, token amounts, addresses involved, and other relevant details of each trade.
MODEL: cipher_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a view that retrieves trade data from the 'Cipher_evt_Trade' table in the 'cipher_arbitrum' source. It includes information such as blockchain, block time and number, project name, trader details, trade side (buy/sell), original amount in ETH and share amount. It also calculates subject fee amount and protocol fee amount. The view filters data based on incremental or start date conditions.
MODEL: post_tech_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a view that retrieves trade data from the 'PostTechProfile_evt_Trade' table in the 'post_tech_v1_arbitrum' source. It includes information such as blockchain, block time and number, project name, trader details, trade side (buy or sell), amount of ETH traded and fees paid in ETH. The view also includes additional columns for currency contract address and symbol, supply amount, transaction hash, index number,and contract address. The model allows data analysts to analyze trade activity on the Arbitrum blockchain for post-tech projects starting from a specified date.
MODEL: social_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a union of two base trade tables,
cipher_arbitrum_base_tradesandpost_tech_arbitrum_base_trades. It combines the data from these tables into a single result set with columns such as blockchain, block time, project, trader, trade side, amount original etc. Additionally, it adds transaction columns 'from' and 'to' to the resulting table. This model enables data analysts to analyze and query consolidated trade data from multiple sources in the Arbitrum blockchain.MODEL: social_avalanche_c_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a base union table that combines data from the 'stars_arena_avalanche_c_base_trades' table. It includes various columns such as blockchain, block time, project, trader, subject, trade side, amount original and more. Additionally, it adds transaction columns for 'from' and 'to'. This model enables data analysts to analyze and query trade-related information from multiple sources in one consolidated table.
MODEL: stars_arena_avalanche_c_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a table that extracts data from the 'transactions' and 'logs' tables in the 'avalanche_c' database. It retrieves information such as block time, block number, trader, subject, trade side (buy or sell), original amount, share amount, fee amounts, currency contract address and symbol. The model filters the data based on specific conditions including incremental updates and success status of transactions. This enables data analysts to analyze trading activity related to a project called 'stars_arena'.
MODEL: friend_tech_base_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a view that retrieves trade data from the 'FriendtechSharesV1_evt_Trade' table. It includes information such as blockchain, block time and number, project name, trader details, trade side (buy or sell), original amount in ETH and share amount. It also calculates subject fee amount and protocol fee amount. The currency is set to ETH with a contract address of 0x00000000000000000000... The model can be used by data analysts to analyze trading activity on the Friendtech platform starting from a specified date or incrementally based on block time.
MODEL: social_base_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a base union table that combines data from the 'friend_tech_base_base_trades' table. It includes various columns such as blockchain, block time, project, trader, trade side, amount original, and more. The model also adds transaction columns to the base union table for further analysis.
MODEL: friend3_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a dataset that includes information about trades on the blockchain. It provides details such as the blockchain name, block time and number, project name, trader and subject involved in the trade, trade side (buy or sell), original amount in ETH and share amount. It also includes fee amounts for subject and protocol fees, currency contract address (set to 0x00000000000000000000), currency symbol (ETH), supply of shares traded, transaction hash, event index,and contract address. The model can be used by data analysts to analyze trading activity on the Friend3 platform starting from a specified date.
MODEL: social_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a base union table that combines data from the 'friend3_bnb_base_trades' table. It includes various columns such as blockchain, block time, project, trader, trade side, amount original, and more. The model also adds transaction columns for 'from' and 'to'. This model enables data analysts to analyze and query trade data from multiple sources in a unified manner.
MODEL: social_base_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a union of multiple base trade tables from different blockchains. It selects various columns related to trades, such as blockchain, block time, project, trader information, transaction details, trade amounts and fees. The model also includes logic to remove duplicate rows based on the transaction hash and event index. This enables data analysts to analyze and compare trade data across different blockchains in a unified manner.
MODEL: social_info.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates a temporary table called 'temp_table' with columns for project, name, blockchain, share_name, and x_username. It populates the table with values for each column from the provided list of tuples. This model enables data analysts to query and analyze data related to projects, names, blockchains, share names,and usernames in various platforms or technologies.
MODEL: social_trades.sql
🟢 Added by:
🔧 PR: #4588, Create
social.trades🧙 Author: @hildobby on 2024-01-18
📝 Summary: This SQL model creates and enables the enrichment of social trades data. It takes a base table called 'social_base_trades' and enriches it with additional information or calculations to provide analysts with more comprehensive insights into social trading activities.
MODEL: contracts_avalanche_c_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze and query information related to contract creators on the Avalanche C chain.
MODEL: contracts_avalanche_c_base_starting_level.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a base starting level table for contracts on the Avalanche C chain. It enables data analysts to analyze and query contract data at its initial state, providing valuable insights into the behavior and performance of contracts on this specific chain.
MODEL: contracts_avalanche_c_contract_mapping.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a contract mapping table for the Avalanche blockchain. It enables data analysts to map contracts on the Avalanche chain, providing them with information about different contracts and their relationships within the blockchain ecosystem.
MODEL: contracts_avalanche_c_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Avalanche C chain.
MODEL: contracts_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: In this diff, several references to contract mapping models were added. These include contracts_avalanche_c_contract_mapping, contracts_fantom_contract_mapping_dynamic, contracts_gnosis_contract_mapping, and contracts_goerli_contract_mapping. The comment suggests that chains for all EVMs in Dune still need to be added.
MODEL: contracts_fantom_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze and track creators of contracts on the Fantom blockchain.
MODEL: contracts_fantom_base_starting_level.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' that enables data analysts to access information about contracts on the Fantom blockchain.
MODEL: contracts_fantom_contract_mapping_dynamic.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a contract mapping table for the Fantom blockchain. It enables data analysts to easily access and analyze information related to contracts on the Fantom blockchain.
MODEL: contracts_fantom_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Fantom blockchain.
MODEL: contracts_gnosis_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to access information about creators of contracts on the Gnosis blockchain.
MODEL: contracts_gnosis_base_starting_level.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' with data from the 'gnosis' chain. It enables data analysts to analyze and query information related to contracts at their starting level in the specified blockchain network.
MODEL: contracts_gnosis_contract_mapping.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a contract mapping table for the 'gnosis' chain. It enables data analysts to easily access and analyze information related to contracts on the Gnosis blockchain.
MODEL: contracts_gnosis_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Gnosis blockchain.
MODEL: contracts_goerli_base_iterated_creators.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze and query information about creators of contracts on the Goerli chain.
MODEL: contracts_goerli_base_starting_level.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' with data from the Goerli chain. It enables data analysts to analyze and query information related to contracts starting levels on the Goerli chain.
MODEL: contracts_goerli_contract_mapping.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a contract mapping table for the Goerli chain. It enables data analysts to easily access and analyze information related to contracts on the Goerli blockchain.
MODEL: contracts_goerli_find_self_destruct_contracts.sql
🟢 Added by:
🔧 PR: #5159, Contracts - Add Remaining Standard EVM Chains
🧙 Author: @MSilb7 on 2024-01-17
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Goerli chain.
MODEL: dex_arbitrum_base_trades.sql
🟠 Modified by:
🔧 PR: #5133, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: In this diff, several references to different tables are added to the SQL model. The tables being referenced include 'fraxswap_arbitrum_base_trades', 'chronos_arbitrum_base_trades', 'zyberswap_arbitrum_base_trades', and 'solidlizard_arbitrum_base_trades'. These new references are added alongside existing references to other tables like 'clipper_arbitrum_base_trades' and 'ramses_arbitrum_base_trades'.
🔧 PR: #5133, Add rubicon to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-12
📝 Summary: In this diff, a reference to the model 'rubicon_arbitrum_base_trades' was added. This reference is included in a list of other models that are being referenced.
MODEL: chronos_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5144, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Uniswap V2 protocol in the Arbitrum blockchain. It sources data from two tables: 'PoolAMM_evt_Swap' and 'PairFactoryAMM_evt_PairCreated' in the 'chronos_arbitrum' database.
MODEL: fraxswap_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5144, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Fraxswap project in the Arbitrum blockchain. It sources data from two events, 'FraxswapPair_evt_Swap' and 'FraxswapFactory_evt_PairCreated'.
MODEL: solidlizard_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5144, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events on the Arbitrum blockchain for the SolidLizard project. It sources data from two tables: 'LizardPair_evt_Swap' and 'LizardFactory_evt_PairCreated'.
MODEL: zyberswap_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5144, Add fraxswap, chronos, zyberswap and solidlizard dex to dex.trades
🧙 Author: @ARDev097 on 2024-01-17
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the ZyberSwap project on the Arbitrum blockchain. It sources data from two tables: 'ZyberPair_evt_Swap' and 'ZyberFactory_evt_PairCreated'.
MODEL: nft_mints.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: The main logic of the changes in this SQL model is that the reference to the 'nftb_bnb_events' table was removed, and a new reference to the 'opensea_v1_ethereum_events' table was added. The references to 'magiceden_solana_events' remain unchanged.
MODEL: nft_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 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: element_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: This SQL model creates a base_trades table that combines data from different sources related to trades on the BNB blockchain. It enables data analysts to analyze and query trade information, including ERC721 and ERC1155 sell and buy orders. The add_nft_tx_data function is used temporarily until tx_from and tx_to columns are available in the base event tables.
MODEL: liquidifty_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this SQL model, the main logic that was added includes:
base_tradestable to includeblock_number,tx_hash, andsub_tx_trade_id.MODEL: nftb_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: This SQL model creates a table called 'base_trades' that contains information about trades in a blockchain project. It includes details such as the blockchain, project version, block time and number, token ID, price, trade type and category, buyer and seller addresses. It also calculates platform fees and royalty fees for each trade. The model joins multiple source tables to gather the necessary data for analysis purposes.
MODEL: nftrade_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this SQL model, the logic that was added includes:
The logic that was removed includes:
MODEL: pancakeswap_nft_bnb_base_trades.sql
🟢 Added by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: This SQL model creates a table called 'base_trades' that contains information about trades in the PancakeSwap project on the Binance blockchain. It includes details such as the trade type, number of items traded, buyer and seller information, price, fees, contract addresses, transaction hash and block number. This model enables data analysts to analyze and understand trading activity on PancakeSwap for ERC721 tokens.
MODEL: tofu_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this SQL model, the table name was changed from 'tofu_v1_events' to 'tofu_v1_base_trades'. The source for raw_transactions was removed. The project_start_date, NATIVE_ERC20_REPLACEMENT, and NATIVE_SYMBOL_REPLACEMENT values were added with their respective values.
MODEL: nft_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this diff, several references to different dbt SQL models were added and removed. The models that were added include 'collectionswap_ethereum_base_trades', 'cryptopunks_ethereum_base_trades', 'foundation_ethereum_base_trades', 'liquidifty_ethereum_base_trades', and more. On the other hand, the models that were removed include 'superrare_ethereum_base_trades' and others.
MODEL: nft_old_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this SQL model, several marketplace models are being refactored. The models 'element_bnb_events', 'element_avalanche_c_events', 'liquidifty_bnb_events', and 'liquidifty_ethereum_events' were removed from the list of nft_models, while the model 'magiceden_solana_events' was added. Additionally, the models 'nftb_bnb_events', 'nftearth_optimism_event's, and 'nftrade_bnb_event's were also removed from the list. Finally, the models 'mooar_polygon_event's,'oneplanet_polygon_event's,'opensea_v3_arbitrum_even'ts,'opensea_v3_polygon_even'ts,'opensea_v4_polygon_even'ts,and opensea_solana_eve'n'tswere kept in place without any changes made to them.
MODEL: nftb_bnb_events.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: [changes too large] The model nftb_bnb_events.sql was removed.
MODEL: nft_base_trades.sql
🟠 Modified by:
🔧 PR: #5175, BNB NFT base trades refactor
🧙 Author: @0xRobin on 2024-01-16
📝 Summary: In this diff, several references to different dbt SQL models were added and removed. The models 'nft_arbitrum_base_trades', 'nft_bnb_base_trades', and 'nft_optimism_base_trades' were added, while the models 'nft_ethereum_base_trades' and 'nft_polygon_base_trades' were removed. The other model references remained unchanged.
MODEL: curvefi_avalanche_c_base_trades.sql
🟢 Added by:
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: [changes too large] The model curvefi_avalanche_c_base_trades.sql was added.
MODEL: dex_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: In this diff, a reference to the model 'curvefi_ethereum_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: curvefi_ethereum_base_trades.sql
🟢 Added by:
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: This SQL model creates a view called 'dexs' that retrieves data from the Ethereum blockchain related to token exchanges on Curve Finance. It includes information such as the version of the pool, block date and time, token amounts bought and sold, addresses of tokens involved in the exchange, taker and maker addresses, project contract address (pool address), transaction hash, event index. This view enables data analysts to analyze trading activity on Curve Finance for different versions of pools.
MODEL: dex_fantom_base_trades.sql
🟠 Modified by:
🔧 PR: #5047, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: The model added a reference to 'curvefi_fantom_base_trades' in addition to the existing references to 'spartacus_exchange_fantom_base_trades', 'openocean_fantom_base_trades', and 'beethoven_x_fantom_base_trades'.
🔧 PR: #5047, Add beethoven_x to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-15
📝 Summary: In this diff, a reference to the model 'beethoven_x_fantom_base_trades' was added. This reference is included in a list of other models that are being referenced.
MODEL: curvefi_fantom_base_trades.sql
🟢 Added by:
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 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 'curvefi_fantom' database. It joins these tables with another table called 'curvefi_fantom_pool_tokens'. The resulting view includes information about token exchanges on the Fantom blockchain, such as block number, block time, token amounts bought and sold, addresses of tokens involved in the exchange, taker and maker addresses, project contract address, transaction hash, and event index.
MODEL: dex_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5133, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: The line
ref('curvefi_optimism_base_trades')was added to the SQL model.🔧 PR: #5133, Add rubicon to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-12
📝 Summary: The model added a reference to 'rubicon_optimism_base_trades' in addition to the existing references to 'synthetix_optimism_base_trades', 'openxswap_optimism_base_trades', and 'openocean_optimism_base_trades'.
MODEL: curvefi_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5139, Add curvefi to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-16
📝 Summary: This SQL model creates a dataset that includes information about token exchanges on the Curve protocol in the Optimism blockchain. It retrieves data from multiple tables and joins them to get details such as block time, block number, token amounts, addresses involved in the exchange, transaction hash, and event index. The resulting dataset can be used by data analysts to analyze trading activity on Curve in Optimism.
MODEL: thena_bnb_base_trades.sql
🟠 Modified by:
🔧 PR: #5166, Update dex info
🧙 Author: @Hosuke on 2024-01-16
📝 Summary: The main logic change in this SQL model is the update of the
projectparameter from 'then' to 'thena'. This change affects the sources used for retrieving data related to Uniswap trades and pool creation events. The blockchain remains as 'bnb', and other parameters such as version, pair swap event source, and factory pool created event source remain unchanged.MODEL: dex_base_trades.sql
🟠 Modified by:
🔧 PR: #5166, Update dex info
🧙 Author: @Hosuke on 2024-01-16
📝 Summary: A reference to the
dex_zksync_base_tradesmodel was added. A common table expression (CTE) namedbase_unionwas also added, which selects all columns from an unspecified table.MODEL: dex_trades_beta.sql
🟠 Modified by:
🔧 PR: #5166, Update dex info
🧙 Author: @Hosuke on 2024-01-16
📝 Summary: The added logic in this SQL model is a macro called 'enrich_dex_trades' which enriches the dex trades data.
MODEL: contracts_system_predeploys.sql
🟠 Modified by:
🔧 PR: #5158, Add BNB System Addresses & Handle for OP Chains
🧙 Author: @MSilb7 on 2024-01-16
📝 Summary: In this SQL model, a new CTE called 'bnb_predeploys' is added. It selects contract information for the BSC blockchain from a values table and assigns it to the variables contract_project, contract_name, and contract_address. The bnb_predeploys CTE is then used in a UNION ALL statement with another SELECT statement to include the blockchain name 'bnb' along with the previously selected variables from bnb_predeploys.
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: In this SQL model, a new predeploy contract called 'create2Deployer' with the address 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 was added to the op_stack_predeploys table.
MODEL: beethoven_x_fantom_base_trades.sql
🟢 Added by:
🔧 PR: #5047, Add beethoven_x to
dex.trades_beta🧙 Author: @tomfutago on 2024-01-15
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer protocol. It enables data analysts to analyze trades on the Fantom blockchain for the project 'beethoven_x'. The table includes information about swaps from a vault event and pool fees.
MODEL: contracts_arbitrum_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: The 'on_table_exists' parameter was removed from the dbt SQL model.
MODEL: contracts_base_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: The 'on_table_exists' parameter was removed from the SQL model. The model is in the 'contracts_base' schema and has an alias of 'contract_mapping'. It is a materialized table partitioned by the column 'created_month'.
MODEL: contracts_bnb_contract_mapping_dynamic.sql
🟠 Modified by:
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: The 'on_table_exists' parameter was removed from the SQL model. The model is in the 'contracts_bnb' schema and has an alias of 'contract_mapping_dynamic'. It is a table materialization with partitioning by the column 'created_month'.
MODEL: contracts_celo_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: The 'on_table_exists' parameter was removed from the SQL model.
MODEL: contracts_ethereum_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5158, Contract Updates - Remove 'Drop Table' and Simplify Min Block Time
🧙 Author: @MSilb7 on 2024-01-15
📝 Summary: The 'on_table_exists' parameter was removed from the dbt SQL model.
MODEL: contracts_optimism_contract_mapping.sql
🟠 Modified by:
🔧 PR: #5158, [Contract Updates - Remove 'Drop Table'
Beta Was this translation helpful? Give feedback.
All reactions