📰 2024-06-14: Weekly Prophet! #6178
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 43 PRs merged from 21 wizards. Great job everyone! 🎉
We had 52 added models 🟢 and 424 modified models 🟠 for 24 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_solana_trades.sql
🟠 Modified by:
🔧 PR: #6162, Materialize solana_dex_trades
🧙 Author: @aalan3 on 2024-06-13
📝 Summary: A reference to 'goosefx_ssl_v2_solana_trades' was removed, and a new column 'block_month' was added by casting the block_time to month. Additionally, a conditional statement was included to filter data based on an incremental predicate when applicable.
MODEL: dex_info.sql
🟠 Modified by:
🔧 PR: #6117, Add icecreamswap on Scroll v2 to dex.trades
🧙 Author: @intensodefi on 2024-06-11
📝 Summary: Added a new row to the temporary table with values for project, name, marketplace_type, and x_username.
SECTOR: labels
toggle to see all model updates
MODEL: labels_op_chains_likely_bot_addresses.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added logic to calculate the number of NFT transfer transactions and NFT trade transactions. Removed logic related to ERC20 transfer transactions. Adjusted conditions for identifying likely bot addresses based on transaction frequency and activity levels, such as hours active per week. Updated categorization of sender addresses as different types of bot addresses based on their activities like dex trades, nft trades, perpetual trades, erc20 transfers, nft transfers or other token transfers.
MODEL: labels_op_chains_likely_bot_contracts.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added logic to calculate the number of NFT transfer transactions and token transfer transactions for each blockchain. Also, added conditions to identify different types of potential bot contracts based on transaction volume percentages related to specific activities like DEX trades, NFT trades, perpetual trades, ERC20 transfers, NFT transfers, and other token transfers.
MODEL: labels_optimism_likely_bot_addresses.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added logic to calculate the number of NFT transfer transactions and token transfer transactions. Removed logic related to ERC20 transfer transactions and NFT trades. Updated conditions for identifying likely bot addresses based on transaction frequencies and activity levels, such as detecting dex trade bots, nft trade bots, perp trade bots, erc20 transfer bot addresses, nft transfer bot addresses, other token transfers by bots or non-token bot addresses.
MODEL: labels_optimism_likely_bot_contracts.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added logic to calculate the percentage of NFT transfer transactions and token transfer transactions. Added conditions to categorize likely bot types based on the percentage of different transaction types.
MODEL: labels_token_standards_arbitrum.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_arbitrum' with the alias 'transfers'. Removed a conditional statement that checked for incremental loading and joined the model with another table based on address matching.
MODEL: labels_token_standards_avalanche_c.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: A source reference was changed from
nft_avalanche_c_transferstonft_avalanche_c.transfers. Additionally, an{% endif %}block was added.MODEL: labels_token_standards_bnb.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference 'nft_bnb' with the alias 'transfers'. Removed a reference to 'nft_bnb_transfers'. Added an additional '{% endif %}' statement.
MODEL: labels_token_standards_ethereum.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_ethereum' and 'transfers'. Removed a reference to 'nft_ethereum_transfers'. Added an additional '{% endif %}' statement.
MODEL: labels_token_standards_fantom.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_fantom' with the alias 'transfers'. Removed a reference to 'nft_fantom_transfers'. Added an additional '{% endif %}' statement.
MODEL: labels_token_standards_gnosis.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_gnosis' with the alias 'transfers'. The incremental logic was also updated to include an additional condition for filtering data based on specific criteria.
MODEL: labels_token_standards_goerli.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_goerli' with the alias 'transfers'. Removed a reference to 'nft_goerli_transfers'. Added an additional '{% endif %}' statement.
MODEL: labels_token_standards_optimism.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_optimism' transfers and removed a reference to 'nft_optimism_transfers'. Also added an additional '{% endif %}' statement.
MODEL: labels_token_standards_polygon.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a source reference to 'nft_polygon' and 'transfers'. Removed a reference to 'nft_polygon_transfers'. Added an additional '{% endif %}' statement.
MODEL: labels_op_habitual_wash_traders.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model now references a source instead of a ref for the table 'wash_trades'. The model also includes an additional row in the final select statement.
MODEL: labels_op_nft_traders.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added logic to select data from a different source based on blockchain, calculate trade counts for each trader, determine percentiles of trades count, and categorize traders as 'Elite NFT Trader', 'Active NFT Trader', or 'Normie NFT Trader' based on their trade counts.
MODEL: labels_nft_users_platforms.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a dbt source for the 'nft_trades' table. The query now selects blockchain, project, and buyer as address from the new source 'nft.trades', followed by a UNION that selects blockchain, project, and seller as address also from the same new source.
MODEL: labels_nft_smart_trader_roi_eth.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a new CTE named 'aggregated_wallet_trading_stats' filtering specific conditions from a source table. Another CTE was added to assign ranks based on the descending order of 'roi_eth_realized'. A final CTE was included to label the data with additional information like blockchain, address, timestamp, model name, and label type. Some commented lines were removed for clarity.
MODEL: labels_nft_traders_transactions.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a dbt source for both buyer and seller addresses in the nft_trades table.
MODEL: labels_nft_traders_transactions_current.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a dbt source for the table 'nft_trades'. The logic remains the same, selecting blockchain, transaction hash, and either buyer or seller address based on certain conditions related to block time within the last 14 days.
MODEL: labels_nft_traders_volume_usd.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Changed the source of data from a dbt ref to a dbt source for both buyers and sellers in the nft_trades table.
MODEL: labels_nft_traders_volume_usd_current.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a dbt source for both buyer and seller information. The logic remains the same, selecting blockchain, amount_usd, and either buyer or seller address from the specified trades table where block_time is within the last 14 days.
MODEL: labels_balancer_v2_gauges.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added columns pool_address, child_gauge_address, status, and source to the SELECT statement.
MODEL: labels_balancer_v2_gauges_arbitrum.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added logic to create two CTEs for reward gauges and child gauges, including additional columns like pool address and child gauge address. Created a new CTE called 'gauges' to combine data from both reward_gauges and child_gauges while filtering out null names. Introduced a 'controller' CTE to filter for active gauges only based on the latest event block time. Finally, joined the 'gauges' with the 'controller' on gauge addresses to select relevant information about blockchain addresses, status (active or inactive), categories, contributors, etc.
MODEL: labels_balancer_v2_gauges_avalanche_c.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added a CTE 'gauges' to select specific columns and join tables. Added another CTE 'controller' to filter for active gauges only based on the latest event block time. The final query selects various columns from the 'gauges' and 'controller' CTEs, determining gauge status as active or inactive based on row number partitioning by pool address.
MODEL: labels_balancer_v2_gauges_base.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added a CTE 'gauges' to select specific columns and join tables. Another CTE 'controller' was added to filter for active gauges only based on the latest event block time. The final query selects various columns from the 'gauges' and 'controller' CTEs, determining gauge status as active or inactive based on row number partitioning by pool address in descending order of event block time.
MODEL: labels_balancer_v2_gauges_ethereum.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added a CTE 'gauges' to select data from different sources and perform transformations. Added another CTE 'controller' to filter for active gauges only based on the latest event block time. The final SELECT statement joins the two CTEs on gauge addresses and includes additional columns like status, source, created_at, updated_at, model_name, and label_type.
MODEL: labels_balancer_v2_gauges_gnosis.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added a CTE 'gauges' to select blockchain, address, pool_address, child_gauge_address, name, category and contributor. Also added a CTE 'controller' to filter for active gauges only based on the latest event block time. The final query selects various fields from the 'gauges' and 'controller' CTEs joining on gauge addresses.
MODEL: labels_balancer_v2_gauges_optimism.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Two new columns were added to the 'reward_gauges' and 'child_gauges' CTEs. A new CTE named 'gauges' was created by combining data from both previous CTEs with a filter for non-null names. Another CTE called 'controller' was added to filter for active gauges only based on certain conditions, joining it with the 'gauges'. The final SELECT statement retrieves specific columns from the combined dataset, determining gauge status as active or inactive based on row number partitioning.
MODEL: labels_balancer_v2_gauges_polygon.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added logic to create two CTEs for reward gauges and child gauges, joining them with pool addresses. Created a new CTE 'gauges' by unioning the two previous CTEs and filtering out null names. Added a 'controller' CTE to filter active gauges only based on the latest event block time. Finally, selected relevant columns from the combined data of 'gauges' and 'controller', including status as active or inactive based on row number partitioned by pool address's descending event block time.
MODEL: labels_balancer_v2_gauges_zkevm.sql
🟠 Modified by:
🔧 PR: #6138, Add pool_address and child_gauge_address to balancer gauge labels
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: Added a CTE 'gauges' to select specific columns and join tables. Another CTE 'controller' was added to filter for active gauges only based on the latest event block time. The final SELECT statement joins the two CTEs on address and includes additional columns like status, source, created_at, updated_at, model_name, and label_type.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_solana_transfers.sql
🟠 Modified by:
🔧 PR: #6107, Solana transfers: Change to LEFT join
🧙 Author: @aalan3 on 2024-06-13
📝 Summary: The changes involve replacing INNER JOINs with LEFT JOINs for two references to 'solana_utils_token_accounts'. This modification allows records from the base table to be retrieved even if there are no corresponding records in the 'solana_utils_token_accounts' table. Additionally, a commented-out condition related to call_block_time was removed.
🔧 PR: #6107, Use correct column name
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The logic of the changes made in this pull request is to replace a column reference with an alias and adjust the corresponding date truncation function accordingly.
🔧 PR: #6107, Solana transfers: fix join
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The main logic added in this change is to join the base table with the
solana_utils_token_accountstable twice, once onfrom_token_accountand once onto_token_account. Additionally, a comment regarding faster CI testing was removed from the model.🔧 PR: #6107, Solana transfers: Fix another typo
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The changes involve removing references to 'call_block_slot' and replacing them with 'block_slot' in the SELECT statements.
🔧 PR: #6107, Solana transfers: Fix comma typo
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The diff shows changes made to the SELECT statement in a CTE. The 'block_time' column was modified, and an incremental predicate condition was added for filtering data based on block time.
🔧 PR: #6107, Reapply solana transfers (#6136)
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: Added a common table expression (CTE) named 'base' that selects data from two different sources based on incremental predicate. The main query now includes the fee column and adjusts the selection of certain columns related to token transfers. Replaced multiple UNION ALL subqueries with a single base table 'tr'. Changed LEFT JOINs to INNER JOINs for joining token accounts, and added a condition filtering data based on block time interval for faster CI testing.
🔧 PR: #6107, Revert Solana
🧙 Author: @aalan3 on 2024-06-11
📝 Summary: The logic added includes selecting various fields from different sources based on actions like transfer, mint, and burn. The data is joined with token accounts using left joins. An incremental predicate is applied to filter the data if it's an incremental run.
🔧 PR: #6107, Reapply solana transfers
🧙 Author: @aalan3 on 2024-06-11
📝 Summary: Added a common table expression (CTE) named 'base' that selects data from two different sources and applies incremental logic. The main query now includes the fee column, along with various other columns related to token transfers. Replaced multiple subqueries with a single CTE for improved efficiency. Changed some left joins to inner joins for better performance and added a condition in the WHERE clause while commenting out another condition for faster CI testing.
🔧 PR: #6107, Revert solana transfers
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: The logic added includes selecting various columns from different sources based on specific conditions, joining tables using left joins, and applying additional filters. New columns were introduced such as account_source, account_destination, call_tx_signer, call_tx_id etc. The model now fetches data from multiple sources like spl_token_call_transferChecked and spl_token_call_mintToChecked among others to categorize actions like transfer, mint or burn. Additionally, an incremental predicate filter was included for the call_block_time column if the query is incremental.
🔧 PR: #6107, Reapply 'add back changes for solana token 2022 (#6107)' (#6124)
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: Added a common table expression to combine data from two sources based on incremental predicate. Selected specific columns and calculated block date. Replaced some column references with new ones, added fee column, and changed join types for token accounts. Removed multiple union queries for different actions and adjusted the WHERE clause condition by adding a comment about time interval for faster CI testing.
🔧 PR: #6107, Revert 'add back changes for solana token 2022 (#6107)'
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: The logic added includes selecting various columns from different sources based on specific conditions, joining tables using left joins, and applying incremental predicates. Different types of actions like transfer, mint, and burn are identified based on the data retrieved. The query also filters data based on a time interval condition for incremental processing.
🔧 PR: #6107, add back changes for solana token 2022
🧙 Author: @jeff-dude on 2024-06-10
📝 Summary: Added a common table expression (CTE) named 'base' that combines data from two different sources. Modified the SELECT statement to include a new column and changed some columns being selected. Replaced LEFT JOIN with INNER JOIN for joining token accounts. Added conditions in the WHERE clause and commented out an existing condition for faster CI testing.
MODEL: tokens_solana_spl_transfers.sql
🟢 Added by:
🔧 PR: #6107, Reapply solana transfers (#6136)
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: This model creates a dataset that tracks token transfers, mints, and burns on the Solana blockchain. It extracts relevant information such as block time, action type (transfer/mint/burn), amount transferred, fees incurred, account sources and destinations, transaction signers and IDs. This enables data analysts to analyze token movements within the Solana ecosystem for reporting or further analysis purposes.
🔧 PR: #6107, Reapply solana transfers
🧙 Author: @aalan3 on 2024-06-11
📝 Summary: This model creates a dataset that combines information on token transfers, mints, and burns from the Solana blockchain. It enables data analysts to track actions such as transfers, mints, and burns including details like amounts transferred, fees incurred, account sources and destinations involved in transactions. The model also includes metadata such as block time and slot information for further analysis of token movements within the Solana ecosystem.
🔧 PR: #6107, Reapply 'add back changes for solana token 2022 (#6107)' (#6124)
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: This model creates a dataset that combines information on token transfers, mints, and burns from the Solana blockchain. It enables data analysts to track actions such as transfers, mints, and burns including details like amounts transferred, fees incurred, account sources and destinations involved in transactions. The model also provides insights into transaction signers, IDs, instruction indices along with executing accounts for further analysis.
🔧 PR: #6107, add back changes for solana token 2022
🧙 Author: @jeff-dude on 2024-06-10
📝 Summary: This model creates a dataset that combines information on token transfers, mints, and burns from the Solana blockchain. It extracts details such as block time, action type (transfer/mint/burn), amount transferred, fees incurred, account sources and destinations for tokens involved in transactions. Additionally, it includes transaction signers' details and IDs along with other relevant execution data. This consolidated dataset enables data analysts to analyze token movements within the Solana ecosystem effectively.
🟠 Modified by:
🔧 PR: #6107, Solana spl transfers fix
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The SQL model was modified to remove a column and adjust the indentation of the FROM clause. Additionally, an incremental predicate condition was updated in the WHERE clause based on whether it is incremental or not.
MODEL: tokens_solana_spl_transfers_call_transfer.sql
🟢 Added by:
🔧 PR: #6107, Reapply solana transfers (#6136)
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: This model creates a dataset that enables data analysts to analyze transfer actions related to token transactions on the Solana blockchain. It includes information such as block time, date, month, slot number, amount transferred, source and destination token accounts, transaction signer details, transaction ID and various indexes for further analysis. This dataset can be used to track token movements and understand the flow of assets within the Solana ecosystem.
🔧 PR: #6107, Reapply solana transfers
🧙 Author: @aalan3 on 2024-06-11
📝 Summary: This model creates a dataset that enables data analysts to analyze transfer actions related to token transactions on the Solana blockchain. It includes information such as block time, date, month, slot number, amount transferred, source and destination token accounts, transaction signer details, transaction ID and various indexes for inner and outer instructions. The model allows for tracking these transfers over time and can be used for monitoring token movements within the network.
🔧 PR: #6107, Reapply 'add back changes for solana token 2022 (#6107)' (#6124)
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: This model creates a dataset that enables data analysts to track token transfers on the Solana blockchain. It includes information such as block time, date, slot, amount transferred, source and destination token accounts, transaction signer details, transaction ID and account executing the transfer. This dataset allows analysts to analyze and monitor token movements within the Solana network efficiently.
🔧 PR: #6107, add back changes for solana token 2022
🧙 Author: @jeff-dude on 2024-06-10
📝 Summary: This model creates a dataset that enables data analysts to track and analyze token transfers on the Solana blockchain. It extracts relevant information such as block time, date, slot, amount transferred, source and destination token accounts, transaction signer details, transaction ID, and executing account. This dataset can be used for monitoring transfer activities within the specified parameters.
🟠 Modified by:
🔧 PR: #6107, Add block_month and partition by it
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: Changed the partition key from 'block_date' to 'block_month'.Added logic to cast the block time as a month.
🔧 PR: #6107, Solana transfers: Test without decoding amount manually
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: Added a reference to the 'amount' column and removed a complex transformation involving byte arrays.
MODEL: tokens_solana_token22_spl_transfers.sql
🟢 Added by:
🔧 PR: #6107, Reapply solana transfers (#6136)
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: This model creates a base table that combines data from various token transactions (such as transfers, mints, burns) in the Solana blockchain. It extracts information like transaction amounts, fees, accounts involved, and transaction details. The model enables data analysts to analyze and track token movements for the 'token2022' version on Solana based on different actions performed like transfers or burns.
🔧 PR: #6107, Reapply solana transfers
🧙 Author: @aalan3 on 2024-06-11
📝 Summary: This model creates a base table that combines data from various token transactions (such as transfers, mints, burns) in the context of token2022 on Solana blockchain. It extracts details like amounts, fees, accounts involved, transaction metadata (block time/slot), and transaction actions. This enables data analysts to analyze and track token movements within the specified timeframe for further insights or reporting purposes.
🔧 PR: #6107, Reapply 'add back changes for solana token 2022 (#6107)' (#6124)
🧙 Author: @aalan3 on 2024-06-10
📝 Summary: This model creates a base table that consolidates data from various token transactions like transfers, mints, burns, and fee extensions in the 'token2022' version. It extracts relevant details such as amounts, fees, accounts involved, transaction information (block time/slot), and action types. This consolidated data enables analysts to track and analyze token movements efficiently for the specified token version.
🔧 PR: #6107, add back changes for solana token 2022
🧙 Author: @jeff-dude on 2024-06-10
📝 Summary: This model creates a base table that combines data from various token transactions (such as transfers, mints, burns) in the 'token2022' version. It extracts details like block time, slot, action type, amount transferred/burned/minted, fees involved (if any), account sources and destinations. This enables data analysts to analyze and track token movements within the specified timeframe for further insights or reporting purposes.
SECTOR: prices
toggle to see all model updates
MODEL: prices_base_tokens.sql
🟠 Modified by:
🔧 PR: #6129, Prices drop normie
🧙 Author: @aalan3 on 2024-06-12
📝 Summary: The token symbols that were added or removed are: NORMIE, STG, and KURBI.
🔧 PR: #6129, CHORE: add BET to base token list
🧙 Author: @ConnerEdgell on 2024-06-10
📝 Summary: BET
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #6132, Add TAIKO on Ethereum mainnet to prices.usd
🧙 Author: @cheeky-gorilla on 2024-06-11
📝 Summary: The token symbols that were added are: TAIKO
🔧 PR: #6132, prices ethereum: fix decimal on nmt
🧙 Author: @jeff-dude on 2024-06-10
📝 Summary: The token symbols that were added or removed are: NMT
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #6125, Update prices_arbitrum_tokens with osETH
🧙 Author: @viniabussafi on 2024-06-11
📝 Summary: osETH
🔧 PR: #6125, Add SLIZ token
🧙 Author: @IrishLatte19 on 2024-06-10
📝 Summary: YAK, ETHX, GYD, SLIZ
MODEL: prices_mantle_tokens.sql
🟢 Added by:
🔧 PR: #6112, Add mantle prices feed
🧙 Author: @Hosuke on 2024-06-11
📝 Summary: This model creates a table with columns for token ID, blockchain, symbol, contract address, and decimals. It enables data analysts to easily access information about various tokens such as MNT, WMNT, JOE, USDC,WETH,mETH ,USDT ,axlUSDC ,STG,PENDLE and ENA including their associated details like contract addresses and decimal values.
MODEL: prices_tokens.sql
🟠 Modified by:
🔧 PR: #6112, Add mantle prices feed
🧙 Author: @Hosuke on 2024-06-11
📝 Summary: The reference model 'prices_mantle_tokens' was added.
MODEL: prices_trusted_tokens.sql
🟠 Modified by:
🔧 PR: #6068, Update trusted_tokens
🧙 Author: @Hosuke on 2024-06-11
📝 Summary: USDC, cEUR, BTC, BIFI, USD₮, axlUSDC, WETH,WXDAI,wstETH,GNO,BUSD,linea,mETH,MNT,
JOE ,WMNT,rETH,WLD,polygon , WMATIC,Dai USDT 3c499c542cef5e3811e1192ce70d8cc03d5c3359
scroll scroll scroll zkevm MATIC rET BUSD,zksync,BUSD
SECTOR: oneinch
toggle to see all model updates
MODEL: oneinch_arbitrum_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information about oneinch project calls for a specific blockchain (in this case, 'arbitrum').
MODEL: oneinch_arbitrum_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a new column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_avalanche_c_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information about oneinch project calls on the Avalanche C blockchain.
MODEL: oneinch_avalanche_c_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a new column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_base_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information related to oneinch project calls for a specified blockchain.
MODEL: oneinch_base_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Changed the unique key in the dbt SQL model to include additional columns: 'block_number' and 'call_trade_id'.
MODEL: oneinch_bnb_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to retrieve information about oneinch project calls for a specific blockchain (in this case, 'bnb').
MODEL: oneinch_bnb_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Changed the unique key in the dbt model to include additional columns 'block_number' and 'call_trade_id'.
MODEL: oneinch_ethereum_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information related to oneinch project calls for a specific blockchain (in this case, Ethereum). It allows analysts to gather insights and perform analysis on the interactions with the oneinch project within the specified blockchain environment.
MODEL: oneinch_ethereum_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_fantom_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to query project calls data for the Fantom blockchain using a OneInch API macro.
MODEL: oneinch_fantom_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Changed the unique key in the dbt SQL model to include additional columns 'block_number' and 'call_trade_id'.
MODEL: oneinch_gnosis_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This model creates and enables data analysts to access information related to oneinch project calls for a specific blockchain (in this case, 'gnosis').
MODEL: oneinch_gnosis_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Changed the unique key in the dbt SQL model to include additional columns: 'block_number', 'call_trade_id'.
MODEL: oneinch_project_orders.sql
🟠 Modified by:
🔧 PR: #6064, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a new column 'order_hash' to the unique key. Defined base columns for orders and native addresses. Created a meta CTE with blockchain details. Modified the logic to handle assets based on native addresses. Joined orders with meta using blockchain and updated incremental predicates based on block_time. Calculated order_hash, maker_asset_symbol, taker_asset_symbol, making_amount_usd, taking_amount_usd in the final select statement grouping by additional column 'tag'. Removed symbol filtering logic and adjusted group by clause in the final select statement.Added tag to output columns of select query from joined table.
🔧 PR: #6064, 1inch: project orders materialize
🧙 Author: @grkhr on 2024-06-11
📝 Summary: An incremental logic was added to the SQL model for the 'orders' table. If the query is incremental, it will apply a filter based on an incremental predicate using the 'block_time' column.
MODEL: oneinch_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: The unique key in the dbt SQL model was updated to include additional columns: 'block_number' and 'call_trade_id'.
MODEL: oneinch_optimism_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to use a macro called 'oneinch_project_calls_macro' with the parameter 'blockchain' set to 'optimism'.
MODEL: oneinch_optimism_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a new column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_polygon_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information about oneinch project calls on the Polygon blockchain.
MODEL: oneinch_polygon_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a new column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_zksync_project_calls.sql
🟢 Added by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: This SQL model creates and enables data analysts to access information about project calls related to the specified blockchain (in this case, 'zksync') using a macro called 'oneinch_project_calls_macro'.
MODEL: oneinch_zksync_project_swaps.sql
🟠 Modified by:
🔧 PR: #6155, 1inch-U25: upgrade project_swaps & project_orders flow
🧙 Author: @max-morrow on 2024-06-14
📝 Summary: Added a column 'call_trade_id' to the unique key constraint in the dbt SQL model.
MODEL: oneinch_fusion_accounts.sql
🟠 Modified by:
🔧 PR: #6121, 1inch-U24: hot fix - update fusion_accounts
🧙 Author: @max-morrow on 2024-06-10
📝 Summary: A new table 'fusion' was added to select specific columns from a reference model. The logic for joining tables 'executors' and 'settlements' was updated to use the column names blockchain, resolver_executor, and settlement. A union all operation was added in the 'calls' table to combine results from two different sources. In the final output section, there were minor changes made in selecting columns and using an aggregation function max_by().
SECTOR: generic-tests
toggle to see all model updates
MODEL: equal_rowcount_with_sources.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model equal_rowcount_with_sources.sql was renamed.
SECTOR: _trino_upgrade
toggle to see all model updates
MODEL: trino_upgrade_alienswap_base_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: A condition filtering events based on block time is added. A function to add NFT transaction data will be removed once 'tx_from' and 'tx_to' are available in the base event tables.
MODEL: trino_upgrade_tevaera_zksync_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The code block that will be removed is a function call to add NFT transaction data once tx_from and tx_to are available in the base event tables.
SECTOR: cryptopunks
toggle to see all model updates
MODEL: cryptopunks_ethereum_current_bids.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a different source named 'nft'. The project filter condition was also added for 'cryptopunks'.
MODEL: cryptopunks_ethereum_current_listings.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a reference to a source named 'nft' and 'base_trades', replacing the previous reference to 'cryptopunks_ethereum_base_trades'.
MODEL: cryptopunks_ethereum_floor_price_over_time.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a reference to a source named 'nft' and changed the source from 'cryptopunks_ethereum_base_trades' to 'base_trades'.
MODEL: cryptopunks_ethereum_listings_over_time.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: The SQL model was updated to change the source of data from a dbt ref to a custom source named 'nft'. The project filter was also changed from 'cryptopunks_ethereum_base_trades' to just 'cryptopunks'.
SECTOR: sudoswap
toggle to see all model updates
MODEL: sudoswap_ethereum_pool_trades_agg_day.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: Added a dbt model with alias 'pool_trades' in schema 'sudoswap_ethereum', materialized as incremental delta. It uses an incremental merge strategy and has a unique key on ['day', 'pool_address']. The model selects data from the source table 'base_trades' in the same schema, calculating nft_change_trading based on conditions and joining with another reference table.
SECTOR: macros
toggle to see all model updates
MODEL: add_nft_tx_data.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model add_nft_tx_data.sql was renamed.
MODEL: nft_approvals.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model nft_approvals.sql was renamed.
MODEL: nft_transfers.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model nft_transfers.sql was renamed.
MODEL: element_v1_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model element_v1_base_trades.sql was renamed.
MODEL: seaport_v3_fork_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model seaport_v3_fork_trades.sql was renamed.
MODEL: seaport_v3_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model seaport_v3_trades.sql was renamed.
MODEL: seaport_v4_fork_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model seaport_v4_fork_trades.sql was renamed.
MODEL: seaport_v4_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model seaport_v4_trades.sql was renamed.
MODEL: sudoswap_v2_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model sudoswap_v2_base_trades.sql was renamed.
MODEL: tofu_v1_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model tofu_v1_base_trades.sql was renamed.
MODEL: zonic_base_trades.sql
🟠 Modified by:
🔧 PR: #6090, NFT dbt subproject
🧙 Author: @0xRobin on 2024-06-14
📝 Summary: [changes too large] The model zonic_base_trades.sql was renamed.
MODEL: [port_to_old_schema.sql](https:
Beta Was this translation helpful? Give feedback.
All reactions