📰 2023-05-19: Weekly Prophet!

[andrewhong5297]

This is your weekly summary of 41 PRs merged from 21 wizards. Great job everyone! 🎉
We had 73 added models 🟢 and 129 modified models 🟠 for 25 Sectors.

Sector	🔧 # PRs	🟢 # Added	🟠 # Modified	🧙 # Authors
dex	1	0	1	1
nft	3	0	5	2
tokens	7	0	9	4
prices	3	0	3	3
opensea	2	0	4	2
lido	3	2	16	3
oneinch	3	1	4	3
seaport	1	0	1	1
contracts	3	0	4	1
_sector	10	45	51	2
staking	1	0	1	1
chain_info	1	1	0	1
quickswap	1	1	1	1
clipper	2	6	3	1
cryptopunks	1	0	6	1
superrare	1	0	1	1
trove	1	0	2	1
gitcoin	1	4	0	1
blur	1	0	1	1
ironbank	1	0	1	1
zora	1	0	1	1
paraswap	1	13	3	1
cow_protocol	2	0	3	2
balancer	1	0	5	1
zeroex	3	0	3	2

SECTOR: dex

toggle to see all model updates

MODEL: dex_aggregator_seed.csv

🟠 Modified by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: [changes too large] The model dex_aggregator_seed.csv was modified.

SECTOR: nft

toggle to see all model updates

MODEL: nft_ethereum_native_mints.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model adds a sum aggregation function to the nfts_minted_in_tx column in the nfts_per_tx CTE. The previous version of the model used a count function instead. This change will affect how many NFTs are counted per transaction in subsequent queries that use this CTE. Additionally, an optional filter was added to only include data from transactions within the last week if running an incremental build.

MODEL: nft_mints.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a SQL model. A set of NFT models were removed and replaced with a single reference to an nft_events table. The new query selects blockchain, project, version, tx_from, tx_to and unique_trade_id from the nft_events table where the event type is 'Mint'. If incremental mode is enabled it will only select events that occurred within the last week. Finally two tables are unioned together: one containing data on native mints and another containing data on project mints (mints from specific projects).

MODEL: nft_optimism_native_mints.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model is used to calculate the amount and value of NFTs minted on the Optimism blockchain. The added code includes selecting data from various tables, joining them together, and filtering based on certain conditions such as excluding bridged L1 NFT collections to L2. Additionally, some columns were renamed or modified for clarity purposes.

MODEL: nft_polygon_aggregators.sql

🟠 Modified by:

🔧 PR: #3345, Add polygon nft aggregators
🧙 Author: @sohwak on 2023-05-16
📝 Summary: The diff shows that two new contract addresses and their corresponding names were added to an existing SQL model. The first one is for 'Element Swap 2' and the second one is for 'BitKeep'. Additionally, a third contract address was added with the name 'OKX'. No other changes were made to this section of the code.

MODEL: nft_events.sql

🟠 Modified by:

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: The added code sets a variable called 'nft_models' which is a list of two dbt models. These models are references to other SQL files in the project, specifically 'aavegotchi_polygon_events' and 'archipelago_ethereum_events'.

SECTOR: tokens

toggle to see all model updates

MODEL: tokens_optimism_erc20_curated.sql

🟠 Modified by:

🔧 PR: #3337, [easy] OP Static Updates
🧙 Author: @MSilb7 on 2023-05-18
📝 Summary: Several tokens were added to the raw_token_list CTE. The new tokens include SGETH, anyWETH, vaETH, vaUSDC, PEPE Optimism, OptiPepe and CLPRDRPL. Each token has a contract address associated with it as well as its symbol and decimals. Some of these tokens are classified under 'receipt' while others are classified under 'underlying'.

🔧 PR: #3337, OP Project Name Mappings
🧙 Author: @MSilb7 on 2023-05-16
📝 Summary: This diff of a SQL model shows the addition of several tokens to a temporary table called raw_token_list. Each token has its contract address, symbol, decimals and type specified. The added tokens include AVT, LAME, MLP and USDM among others.

MODEL: tokens_optimism_nft_curated.sql

🟠 Modified by:

🔧 PR: #3337, [easy] OP Static Updates
🧙 Author: @MSilb7 on 2023-05-18
📝 Summary: The diff of the SQL model shows additions of contract addresses and their corresponding names to a temporary table. These contracts are likely related to blockchain transactions or smart contracts, as indicated by their hexadecimal format. The logic added is simply inserting new rows into the temporary table with these contract addresses and names.

🔧 PR: #3337, OP Project Name Mappings
🧙 Author: @MSilb7 on 2023-05-16
📝 Summary: The diff of the SQL model shows that two new contracts, 'Optimistic World' and 'Mirror Zorb', have been added to a temporary table. The logic of this change is to include these contracts in the analysis performed by the SQL model. No other changes were made to the existing code.

MODEL: tokens_avalanche_c_erc20.sql

🟠 Modified by:

🔧 PR: #3327, Adding VINTAGE and NRWL tokens
🧙 Author: @discochuck on 2023-05-17
📝 Summary: Two tokens were added to the model: VINTAGE and NRWL.

🔧 PR: #3327, Adding DEI and yyAVAX to avalanche_c tokens
🧙 Author: @discochuck on 2023-05-16
📝 Summary: The token symbol 'yyAVAX' was added to the model. No tokens were removed from the model.

🔧 PR: #3327, Adding Grain, IBEX, WINE, xSHRAP, RPEPE
🧙 Author: @discochuck on 2023-05-16
📝 Summary: The following token symbols were added: DEI, GRAIN, xSHRAP, IBEX, RPEPE and WINE. No token symbols were removed.

MODEL: tokens_polygon_erc20.sql

🟠 Modified by:

🔧 PR: #3313, Add Quickswap v2 to dex.trades
🧙 Author: @darvinrio on 2023-05-17
📝 Summary: [changes too large] The model tokens_polygon_erc20.sql was modified.

MODEL: tokens_ethereum_erc20.sql

🟠 Modified by:

🔧 PR: #3343, [ERC20] Add 511 Mainnet Tokens
🧙 Author: @bh2smith on 2023-05-16
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.

SECTOR: prices

toggle to see all model updates

MODEL: prices_polygon_tokens.sql

🟠 Modified by:

🔧 PR: #3313, Add Quickswap v2 to dex.trades
🧙 Author: @darvinrio on 2023-05-17
📝 Summary: The tokens that were added are QUICK, DIMO, and GDDY. The token that was removed is TETU.

MODEL: prices_ethereum_tokens.sql

🟠 Modified by:

🔧 PR: #3347, Restructure Blur to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: The token symbol that was added is bpETH and the token symbols that were removed are SHIH, CAW, YEL and POP.

🔧 PR: #3347, add verse to prices.usd
🧙 Author: @henrystats on 2023-05-16
📝 Summary: The token symbols that were added or removed are:

• Added: VERSE
• Removed: GRAIN Note: The model includes a list of tokens with their respective information such as ID, blockchain, symbol, contract address and decimals. The diff shows that the token 'VERSE' was added to the list while 'GRAIN' was removed.

SECTOR: opensea

toggle to see all model updates

MODEL: opensea_v3_polygon_events.sql

🟠 Modified by:

🔧 PR: #3323, Add seaport v1.5 to opensea_events
🧙 Author: @sohwak on 2023-05-16
📝 Summary: This SQL model adds a filter to an existing select statement that creates a unique trade ID for each row in the 'seaport_polygon_trades' table. The filter checks if the value of 'project_contract_address' is equal to '0x00000000006c3852cbef3e08e8df289169ede581', which corresponds to Seaport v1.0 blockchain project.

MODEL: opensea_v4_polygon_events.sql

🟠 Modified by:

🔧 PR: #3323, Add seaport v1.5 to opensea_events
🧙 Author: @sohwak on 2023-05-16
📝 Summary: The diff shows changes made to a SQL model that sources data from the Seaport_evt_OrdersMatched and Seaport_evt_OrderFulfilled tables. The main logic added is filtering by contract address, which now includes two versions of the Seaport contract (v1.4 and v1.5). Additionally, there are new conditions in the WHERE clause for selecting trades based on fee_wallet_name or right_hash values.

MODEL: opensea_polygon_seaport_trades_samples.csv

🟠 Modified by:

🔧 PR: #3323, Add seaport v1.5 to opensea_events
🧙 Author: @sohwak on 2023-05-16
📝 Summary: [changes too large] The model opensea_polygon_seaport_trades_samples.csv was modified.

MODEL: opensea_inorganic_volume_filter_wallet_funders_wallets.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The added code selects distinct buyer and seller wallets from the 'nft_events' table where the project is either 'looksrare', 'x2y2', or 'blur'. The removed code selected distinct buyer and seller wallets from different tables ('looksrare_ethereum_trades', etc.) but did not filter by project.

SECTOR: lido

toggle to see all model updates

MODEL: lido_ethereum_accounting_revenue.sql

🟠 Modified by:

🔧 PR: #3351, lido accounting revenue fixes
🧙 Author: @ppclunghe on 2023-05-18
📝 Summary: The diff of the SQL model shows that a new CTE called 'addresses' was added, which contains hardcoded addresses and their corresponding names. The query also includes two new CTEs: 'oraclev2_txns' and 'protocol_fee_distribution'. The former calculates revenue from different sources (treasury, operators, insurance) for each period. The latter joins oracle transactions with protocol fees to calculate revenue distribution among depositors, treasury fund, operators and insurance fund. Finally a union all is used to combine results from both queries into one table.

🔧 PR: #3351, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_revenue.sql was renamed.

🔧 PR: #3351, Update lido decoded table name
🧙 Author: @antonio-mendes on 2023-05-16
📝 Summary: The change in the SQL model involves renaming a source from 'LidoOracle_evt_PostTotalShares' to 'LegacyOracle_evt_PostTotalShares'. This affects the table being queried and therefore changes the data that is returned. The rest of the code remains unchanged, with a query selecting specific columns from this table and ordering them by descending order based on one of those columns.

MODEL: lido_ethereum_accounting_dai_referral_payment.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_dai_referral_payment.sql was renamed.

MODEL: lido_ethereum_accounting_deposits.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: The only change made to the SQL model is the addition of a commented line that references another query. No changes were made to the SELECT statement or any other part of the code.

MODEL: lido_ethereum_accounting_fundraising.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_fundraising.sql was renamed.

MODEL: lido_ethereum_accounting_ldo_referral_payment.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_ldo_referral_payment.sql was renamed.

MODEL: lido_ethereum_accounting_lego_expenses.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_lego_expenses.sql was renamed.

MODEL: lido_ethereum_accounting_liquidity_incentives.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_liquidity_incentives.sql was renamed.

MODEL: lido_ethereum_accounting_lox_incentives.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_lox_incentives.sql was renamed.

MODEL: lido_ethereum_accounting_operating_expenses.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_operating_expenses.sql was renamed.

MODEL: lido_ethereum_accounting_other_expenses.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_other_expenses.sql was renamed.

MODEL: lido_ethereum_accounting_other_income.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_other_income.sql was renamed.

MODEL: lido_ethereum_accounting_sources.yml

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_sources.yml was renamed.

MODEL: lido_ethereum_accounting_trp_expenses.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_accounting_trp_expenses.sql was renamed.

MODEL: lido_ethereum_accounting.sql

🟠 Modified by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: The SQL model selects data from a table named lido_ethereum_accounting_lox_incentives and calculates the period by truncating the date to day level. It also adds a category column with value '3.2.3.3.Domain Incentives'. The amount_token is negated and added as value in the select statement along with token column.The UNION ALL operator combines this result set with another one that is not shown here, but was present before changes were made to this model in a merged pull request.

MODEL: lido_ethereum_liquidity.sql

🟢 Added by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: This SQL model creates a view that combines data from the 'lido_ethereum_liquidity_kyberswap_pools' table with other tables (if they exist) to provide a comprehensive overview of liquidity pools. The view includes information such as pool name, blockchain, project, fee structure, token reserves and trading volume. This enables data analysts to easily query and analyze liquidity pool data across multiple sources in one place.

MODEL: lido_ethereum_liquidity_kyberswap_pools.sql

🟢 Added by:

🔧 PR: #3240, Add lido liquidity initial model
🧙 Author: @gregshestakovlido on 2023-05-18
📝 Summary: [changes too large] The model lido_ethereum_liquidity_kyberswap_pools.sql was added.

SECTOR: oneinch

toggle to see all model updates

MODEL: oneinch_unoswap_v5_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3366, remove another tx for oneinch bug
🧙 Author: @jeff-dude on 2023-05-18
📝 Summary: The diff shows changes made to a SQL model. A few transactions were not joining correctly with the traces table due to an incorrect join condition, which was fixed by changing '+2' to '+3'. The update statement was used for v1 engine as full refresh is less common there. Additionally, a new transaction hash filter '0xafba4b3db26b0e9f26d0ca4c709e80ee2b8bc18e3298fa67126697fc45fba0c6' was added and it's suggested that the tx_hash filter should be removed if the join is fixed.

MODEL: oneinch_contract_addresses.sql

🟠 Modified by:

🔧 PR: #3328, [oneinch] add oneinch_fusion_executors and fix naming in oneinch_contract_addresses
🧙 Author: @grkhr on 2023-05-18
📝 Summary: The SQL model has been modified to change the name of a column from 'address' to 'contract_address'. The logic for selecting data remains the same, with no other changes made.

MODEL: oneinch_fusion_executors.sql

🟢 Added by:

🔧 PR: #3328, [oneinch] add oneinch_fusion_executors and fix naming in oneinch_contract_addresses
🧙 Author: @grkhr on 2023-05-18
📝 Summary: This SQL model enables data analysts to query Ethereum traces and extract information about resolver addresses, their executors, the blockchain they belong to (identified by chain ID), and whether or not they require KYC. The model also includes a join with two tables containing additional information on resolver addresses and chains. This allows for more comprehensive analysis of Ethereum transactions related to these resolvers.

MODEL: oneinch_limit_order_protocol_rfq_v2_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3355, Rename onceinch_lop_v2 to oneinch schema for decoded tables
🧙 Author: @antonio-mendes on 2023-05-16
📝 Summary: The diff shows that the source of three dbt SQL models has been changed from oneinch_lop_v2_ethereum to oneinch_ethereum. The models are named limit_order_protocol_rfq_v2, and each model is associated with a different function call. The WHERE clause filters for successful calls, and there is an optional check for incremental updates.

MODEL: oneinch_limit_order_protocol_v2_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3355, Rename onceinch_lop_v2 to oneinch schema for decoded tables
🧙 Author: @antonio-mendes on 2023-05-16
📝 Summary: The diff shows that the source of three SQL models has been changed from oneinch_lop_v2_ethereum to oneinch_ethereum. The models are related to the Limit Order Protocol and its various functions. The change is made in order to update the source for these models.

SECTOR: seaport

toggle to see all model updates

MODEL: seaport_v2_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3359, add seaport v1.5 to seaport_v2_ethereum_trades
🧙 Author: @denz-e on 2023-05-18
📝 Summary: The diff shows changes made to a SQL model that involves the Seaport Ethereum platform. The changes include adding two new contract addresses for version 1.5 of Seaport, and removing the previous address for version 1.4 from certain parts of the code where it was used as a filter condition in queries on source_ethereum_transactions and ref_seaport_ethereum_base_pairs tables respectively. There are also some minor formatting changes such as indentation, removal of comments, etc., but no significant logic has been added or removed apart from these modifications related to contract addresses.

SECTOR: contracts

toggle to see all model updates

MODEL: contracts_optimism_contract_creator_address_list.sql

🟠 Modified by:

🔧 PR: #3337, [easy] OP Static Updates
🧙 Author: @MSilb7 on 2023-05-18
📝 Summary: The diff shows additions and removals to a SQL model that creates a temporary table called 'curated_list'. The table contains columns for creator_address and contract_project. Three rows were initially present in the table, but three more have been added in the pull request.

🔧 PR: #3337, OP Project Name Mappings
🧙 Author: @MSilb7 on 2023-05-16
📝 Summary: The diff shows changes made to a SQL model that creates a temporary table called 'curated_list' with two columns: creator_address and contract_project. The changes involve adding or removing rows from the table, where each row represents an Ethereum smart contract address and its corresponding project name. Some of the project names were modified by replacing certain words or adding symbols at the end of their names.

MODEL: contracts_optimism_contract_mapping.sql

🟠 Modified by:

🔧 PR: #3281, Add Decoded Contracts to OP Contract mapping
🧙 Author: @MSilb7 on 2023-05-17
📝 Summary: The SQL model has been updated with additional code to include missing contracts. The new code uses a union all statement and left join to add the missing contracts. It also includes filters that will only be applied on an incremental run, such as block time and contract address not existing in creator_contracts table. Additionally, there are changes made to some of the select statements where NULL is replaced with cast(NULL as string) for trace_creator_address, creator_address and contract_factory columns in synthetix genesis contracts and uniswap pools from ovm1 sections of the model.

MODEL: contracts_optimism_project_name_mappings.sql

🟠 Modified by:

🔧 PR: #3337, OP Project Name Mappings
🧙 Author: @MSilb7 on 2023-05-16
📝 Summary: The SQL model contains a select statement that maps Dune Analytics project names to human-readable names. The diff shows changes made to the mapping of some project names, with some being updated and others added or removed. Specifically, 'Lyra' was changed to 'Lyra Finance', 'Avalon Lyra' was changed to 'Lyra Finance', and new mappings were added for projects such as Collab.Land, Biconomy - Hyphen, Angle Protocol and Overnight+.

SECTOR: _sector

toggle to see all model updates

MODEL: rarible_polygon_events.sql

🟠 Modified by:

🔧 PR: #3326, Rarible polygon direct purchase and direct accept bid updates
🧙 Author: @BennyFeng on 2023-05-18
📝 Summary: This SQL model adds two new trade categories, 'buy' and 'sell', to the existing trades table. It includes information such as block time, block number, transaction hash, contract address of the NFT being traded along with its token ID and standard (erc721 or erc1155), currency contract used for payment along with amount paid in raw form. The data is sourced from Rarible Polygon's ExchangeMetaV2_call_directPurchase and ExchangeMetaV2_call_directAcceptBid tables joined with Polygon's transactions table based on matching block numbers and hashes.

MODEL: collectionswap_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3330, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table of secondary and primary trades for NFTs, including information such as the buyer, seller, price paid (including fees), and trade type. It also includes details about the NFT itself such as its ID and amount traded. This enables data analysts to track trading activity on various platforms that use CollectionSwap's smart contract infrastructure.

🔧 PR: #3330, Restructure collectionswap to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table of secondary and primary trades for NFTs, including information such as the buyer, seller, price paid (including fees), and trade type. It also includes details about the NFT itself such as its ID and amount traded. This enables data analysts to track trading activity on various platforms that use CollectionSwap's smart contract infrastructure.

MODEL: cryptopunks_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3286, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table that tracks secondary market trades of CryptoPunks NFTs on the Ethereum blockchain. It enables data analysts to analyze trade volume, prices, and buyer/seller behavior over time. The table includes information such as the date and time of each trade, the type (buy or bid accepted), price in ETH, buyer and seller addresses, NFT token ID and contract address. This model also filters out flash loan transactions from its results if it is run incrementally within one week's timeframe.

🔧 PR: #3286, Restructure Cryptopunks to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table that tracks secondary market trades of CryptoPunks NFTs on the Ethereum blockchain. It enables data analysts to analyze trade volume, prices, and buyer/seller behavior over time. The table includes information such as the date and time of each trade, the type (buy or bid accepted), price in ETH, buyer and seller addresses, NFT token ID and contract address. This model also filters out flash loan transactions from its results if it is run incrementally within one week's timeframe.

MODEL: looksrare_v1_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3332, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table that enables data analysts to track LooksRareExchange's secondary market trades, including private sales and offers accepted. The table includes information on the buyer, seller, price of the trade in raw currency units (with platform fees included), royalty fee amount paid for each transaction and its recipient address. Data is sourced from Ethereum blockchain events using incremental updates where applicable.

🔧 PR: #3332, Restructure looksrare to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table that enables data analysts to track LooksRareExchange's secondary market trades, including private sales and offers accepted. The table includes information on the buyer, seller, price of the trade in raw currency units (with platform fees included), royalty fee amount paid for each transaction and its recipient address. Data is sourced from Ethereum blockchain events using incremental updates where applicable.

MODEL: looksrare_v2_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3332, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model creates a table that summarizes trade data for LooksRareProtocol_evt_TakerAsk and LooksRareProtocol_evt_TakerBid events. The resulting table includes information such as the block date, transaction hash, project contract address, NFT contract address and token ID, trade category (Offer Accepted or Buy), buyer/seller addresses and currency. It also calculates raw prices for platform fees and royalty fees associated with each trade. This model enables data analysts to easily query this summarized trading data in their analytics work.

🔧 PR: #3332, Restructure looksrare to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model creates a table that summarizes trade data for LooksRareProtocol_evt_TakerAsk and LooksRareProtocol_evt_TakerBid events. The resulting table includes information such as the block date, transaction hash, project contract address, NFT contract address and token ID, trade category (Offer Accepted or Buy), buyer/seller addresses and currency. It also calculates raw prices for platform fees and royalty fees associated with each trade. This model enables data analysts to easily query this summarized trading data in their analysis of the LooksRare Protocol ecosystem.

MODEL: sudoswap_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3329, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table of NFT trades on the SudoSwap decentralized exchange. It includes data such as the buyer, seller, price paid (including fees), and token ID for each trade. The model uses call trace information to piece together details about each trade since Sudoswap doesn't emit any data in events for swaps. Additionally, it joins with tables that track changes to pool fees and protocol fees over time so that analysts can see how these factors affect trading activity on Sudoswap.

🔧 PR: #3329, Restructure Sudoswap to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model creates a table of NFT trades on the SudoSwap decentralized exchange. It includes data such as the buyer, seller, price paid (including fees), and token ID for each trade. The model uses call trace information to piece together details about each trade since Sudoswap doesn't emit any data in events for swaps. Additionally, it joins with tables that track changes to pool fees and protocol fees over time so that analysts can see how these factors affect trading activity on Sudoswap.

MODEL: nft_ethereum_trades_beta.sql

🟠 Modified by:

🔧 PR: #3322, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model adds references to various Ethereum base trades for different platforms such as Zora, CryptoPunks, Sudoswap and Looksrare. It suggests removing a CTE (Common Table Expression) and including ETH into the general prices table once everything is migrated.

🔧 PR: #3322, Restructure looksrare to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: Two references were added to the SQL model: 'looksrare_v1_ethereum_base_trades' and 'looksrare_v2_ethereum_base_trades'. These are being used in conjunction with existing references for three other trade types. The comment at the end suggests that a CTE should be removed once everything is migrated, but it's unclear what this refers to.

🔧 PR: #3322, Restructure collectionswap to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: A new reference to a table called 'collectionswap_ethereum_base_trades' was added in the SQL model. The comment suggests that a CTE should be removed and ETH should be included in the general prices table after migration.

🔧 PR: #3322, Restructure Sudoswap to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: A new reference to a table called 'sudoswap_ethereum_base_trades' was added. The rest of the code remains unchanged except for a comment suggesting that an existing CTE should be removed and ETH should be included in the general prices table after migration.

🔧 PR: #3322, Restructure Cryptopunks to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: A reference to a new table called 'cryptopunks_ethereum_base_trades' was added to the SQL model. The rest of the code remains unchanged, except for a comment suggesting that an existing CTE should be removed once everything is migrated.

🔧 PR: #3322, Restructure Blur to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: A new reference to a table called 'blur_ethereum_base_trades' has been added to the SQL model. The rest of the code remains unchanged and consists of references to other tables with their respective names and versions.

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: Three references to different versions of the Zora Ethereum base trades were added to this SQL model. A comment was made suggesting that a CTE should be removed and ETH should be included in the general prices table once everything is migrated.

MODEL: nft_ethereum_trades_beta_ported.sql

🟢 Added by:

🔧 PR: #3350, NFT Restructuring
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model creates a new table by merging data from an existing table called 'nft_ethereum_trades_beta'. This new table enables data analysts to access and analyze historical trade information for non-fungible tokens (NFTs) on the Ethereum blockchain.

🔧 PR: #3350, NFT trades backwards compatibility
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model creates a new table that maps Ethereum trades to NFT transfers. This enables data analysts to analyze the relationship between NFT transfers and Ethereum trades, providing insights into the behavior of users in these markets. The port_to_old_schema function is used to migrate data from an old schema to this new one.

MODEL: nft_events.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model selects all columns from a table called 'nft_events_old'. It enables data analysts to retrieve and analyze data stored in the 'nft_events_old' table.

MODEL: nft_events_old.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model is a list of nft_models with some models being added and removed. The added models include events from various platforms such as Ethereum, Polygon, Binance Smart Chain (BNB), Optimism, Solana and Arbitrum. The removed models include 'element_events', 'looksrare_ethereum_events', 'magiceden_events', 'oneplanet_polygon_events','pancakeswap_bnb_nft_events','quix_optimism_event' among others. Finally, the SELECT statement selects all columns from these nft_models without any filtering or aggregation logic applied to them.

MODEL: blur_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: Unfortunately, there is no SQL model provided to summarize. The only line given in the example is a variable assignment which does not provide enough information to summarize any changes made in a pull request. Please provide the SQL model diff for me to accurately summarize it within 100 words limit.

MODEL: collectionswap_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model collectionswap_ethereum_events.sql was renamed.

MODEL: cryptopunks_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff of the SQL model shows changes made to a query that retrieves data on CryptoPunks sales and bids. The changes involve adding or removing lines of code that define variables, join tables, filter results, and select columns. Specifically, the added lines calculate row numbers for each punk ID event number; look up who the seller transferred to in a block with 1 offset index; group by certain fields; cast values as decimals or varchars; and concatenate strings to create unique trade IDs. No column names are mentioned in this diff.

MODEL: element_avalanche_c_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model element_avalanche_c_events.sql was renamed.

MODEL: element_bnb_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model element_bnb_events.sql was renamed.

MODEL: element_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model element_ethereum_events.sql was renamed.

MODEL: foundation_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model foundation_ethereum_sources.yml was renamed.

MODEL: fractal_polygon_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model fractal_polygon_sources.yml was renamed.

MODEL: liquidifty_bnb_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The added lines are initializing several columns with null values. These include platform_fee_amount_raw, platform_fee_amount, platform_fee_amount_usd, and others. Additionally, the model selects the symbol of a BEP20 token as royalty fee currency symbol and concatenates various fields to create a unique trade ID. The removed lines are not shown in this diff so it is impossible to summarize what was removed from the previous version of this SQL model.

MODEL: liquidifty_bnb_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model liquidifty_bnb_sources.yml was renamed.

MODEL: liquidifty_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The added lines are initializing null values for platform and royalty fees, as well as adding a column for the currency symbol. No other changes were made to the SQL model.

MODEL: liquidifty_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model liquidifty_ethereum_sources.yml was renamed.

MODEL: looksrare_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model looksrare_ethereum_sources.yml was renamed.

MODEL: nftb_bnb_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model is a diff of a merged pull request. It adds and removes some lines in the code. The main logic added includes selecting data from three different tables, mints, burns and trades using inner joins to join them with other tables such as NFT_evt_Transfer and NFT_call_royaltyInfo. A left join is also used to combine the result set with another table called logs based on certain conditions being met for each row in the result set.The final output selects specific columns from all_events table along with calculated values for platform fee amount raw, royalty fee amount raw etc.,

MODEL: nftb_bnb_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model nftb_bnb_sources.yml was renamed.

MODEL: nftearth_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model includes changes to two subqueries, erc721_transfer and erc1155_transfer, where the select statement was modified by adding a new column. The two subqueries were then combined using union all. Finally, there is a subquery called iv_columns that renames a column to align with other tables in the database.

MODEL: nftrade_bnb_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model nftrade_bnb_sources.yml was renamed.

MODEL: oneplanet_polygon_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The change made to the SQL model is very minimal. The last line of the code was modified by removing a hyphen and adding a semicolon at the end. This suggests that there were no changes in logic or functionality, but rather just formatting or syntax adjustments.

MODEL: quix_v1_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a SQL model that calculates royalties for NFT sales on the Optimism blockchain. The changes include minor formatting and syntax adjustments, as well as modifications to join conditions between tables. The main logic of the model remains unchanged: it retrieves raw event data from two sources, joins them with transfer data and token metadata, calculates fees based on various criteria such as currency type and platform percentage, then outputs a final table of royalty information for each sale transaction.

MODEL: quix_v2_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a SQL model that calculates royalties for NFTs and ERC-721 tokens on the Optimism blockchain. The changes include minor formatting adjustments, such as removing extra spaces and adding or removing line breaks. There are also some modifications to the join conditions between tables, including filtering out specific addresses from certain columns. Additionally, there are updates to how platform fees and royalty fees are calculated based on token values in USD currency using external price data sources.

MODEL: quix_v3_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model is a diff of an existing model. The changes include removing white spaces, adding comments and changing the formatting of some lines. There are no significant changes to the logic or functionality of this code.

MODEL: quix_v4_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model is modified to include the latest data from different sources. The modifications include adding and removing rows of code, changing some variable names, and updating the date range for incremental updates. The main changes involve joining tables to get additional information about transactions such as token standard, trade type, currency symbol etc., calculating platform fees and royalty fees based on transaction values and percentages specified in other tables. Finally a unique trade ID is generated by concatenating several columns together.

MODEL: quix_v5_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model is a diff of an existing dbt model. The changes include adding and removing white spaces, changing the indentation, and modifying some comments. There are no significant changes to the logic or functionality of this SQL code.

MODEL: rarible_polygon_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model rarible_polygon_sources.yml was renamed.

MODEL: stealcam_arbitrum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model has been modified to correct a typo in the project name. The word 'Stealcam' was changed to 'stealcam'. This change was made on line 4 by removing the '-' and adding '+' at the start of each line that reflects this modification. No other changes were made in this SQL model, which selects data from a table where evt_block_time is greater than or equal to a given date and returns blockchain, project, version, block time and block date information for further analysis.

MODEL: stealcam_arbitrum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model stealcam_arbitrum_sources.yml was renamed.

MODEL: superrare_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model superrare_ethereum_sources.yml was renamed.

MODEL: tofu_arbitrum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: There is no SQL model provided in the prompt. The only line given sets a variable called ARETH_ERC20_ADDRESS to a specific value. Therefore, there is nothing to summarize about added or removed logic in this case.

MODEL: tofu_arbitrum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model tofu_arbitrum_sources.yml was renamed.

MODEL: tofu_bnb_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff of the SQL model is not provided, only a variable assignment statement. The statement sets the value of BNB_ERC20_ADDRESS to '0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c'.

MODEL: tofu_bnb_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model tofu_bnb_sources.yml was renamed.

MODEL: tofu_optimism_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a SQL model that extracts data from the Tofu NFT Optimism blockchain. The changes include minor formatting and syntax adjustments, such as removing whitespace and adding commas. There are also some conditional statements added for incremental updates of the database. The model selects various fields related to trades on the platform, including trade type (single item or bundle), number of items traded, price in original currency and USD equivalent, seller/buyer addresses etc., along with additional information about tokens being traded like collection name and token standard.

MODEL: tofu_optimism_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model tofu_optimism_sources.yml was renamed.

MODEL: tofu_polygon_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model contains a variable MATIC_ADDRESS set to the value '0x000000000000000000000...1010'. No other changes were made to the model.

MODEL: tofu_polygon_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model tofu_polygon_sources.yml was renamed.

MODEL: trove_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model adds several columns to the existing query, including platform_fee_amount_raw, platform_fee_amount, platform_fee_amount_usd, and others. These columns are all set to null values. Additionally, a new table is joined called erc20 which includes the symbol for royalty fee currency. The unique_trade_id column has been modified to include block_number and evt_index in addition to tx_hash as part of its value.

MODEL: trove_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model trove_sources.yml was renamed.

MODEL: trove_v1_arbitrum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model selects block number, transaction sender and receiver addresses, and a unique trade ID from the marketplace table joined with the transactions table. The diff adds columns for platform fee amount (raw), platform fee amount (USD), platform fee percentage, royalty fee amount (raw), royalty currency symbol, royalty receive address as well as their respective USD amounts and percentages. All of these added columns are set to null values.

MODEL: trove_v2_arbitrum_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model selects block number, transaction sender and receiver addresses, and a unique trade ID from the marketplace table joined with the transactions table. The diff adds columns for platform fee amount (raw), platform fee amount (USD), platform fee percentage, royalty fee amount (raw), royalty currency symbol, royalty receive address as well as their respective USD amounts and percentages. All of these added columns have null values in this version of the code.

MODEL: x2y2_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model x2y2_ethereum_sources.yml was renamed.

MODEL: zonic_optimism_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model zonic_optimism_sources.yml was renamed.

MODEL: zora_ethereum_sources.yml

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model zora_ethereum_sources.yml was renamed.

MODEL: aavegotchi_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from the 'nft_trades' table where the project is equal to 'aavegotchi'. This enables data analysts to easily filter and analyze NFT trades specifically related to the Aavegotchi project.

MODEL: archipelago_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'archipelago'. This enables data analysts to easily query and analyze trade data specific to the Archipelago project.

MODEL: blur_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'blur'. This enables data analysts to easily query and analyze trade data for NFTs specifically related to the Blur project.

MODEL: collectionswap_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'collectionswap'. This enables data analysts to easily query and analyze trade data specifically related to the CollectionSwap project.

MODEL: cryptopunks_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'cryptopunks'. This enables data analysts to easily query and analyze trade data specifically for the Cryptopunks project.

MODEL: element_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'element'. This enables data analysts to easily query and analyze trade data specific to the Element project.

MODEL: foundation_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'foundation'. This enables data analysts to easily query and analyze trade data for NFTs specifically related to the Foundation project.

MODEL: fractal_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'fractal'. This enables data analysts to easily query and analyze trade data for NFTs specifically related to the Fractal project.

MODEL: looksrare_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include trades where the project is equal to 'looksrare'. This enables data analysts to easily query and analyze NFT trade data specifically for the LooksRare project.

MODEL: magiceden_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'magiceden'. This enables data analysts to easily query and analyze trade data specifically for the Magic Eden project.

MODEL: nftb_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'nftb'. This enables data analysts to easily query and analyze trade data specific to the NFTB project.

MODEL: nftearth_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'nftearth'. This enables data analysts to easily query and analyze trade data specific to the nftearth project.

MODEL: nftrade_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'nftrade'. This enables data analysts to easily query and analyze trade data specific to the nftrade project.

MODEL: oneplanet_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'oneplanet'. This enables data analysts to easily query and analyze trade data for NFTs (non-fungible tokens) specifically related to the One Planet project.

MODEL: opensea_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'opensea'. This enables data analysts to easily query and analyze trade data specifically for projects on OpenSea.

MODEL: pancakeswap_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'pancakeswap'. This enables data analysts to easily query and analyze NFT trade data specifically related to PancakeSwap.

MODEL: quix_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'quix'. This enables data analysts to easily query and analyze trade data specific to the Quix project.

MODEL: rarible_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'rarible'. This enables data analysts to easily query and analyze trade data specifically for the Rarible project.

MODEL: stealcam_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'stealcam'. This enables data analysts to easily query and analyze trade data for a specific project within an NFT marketplace.

MODEL: sudoswap_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'sudoswap'. This enables data analysts to easily query and analyze NFT trade data specific to the Sudoswap project.

MODEL: superrare_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'superrare'. This enables data analysts to easily query and analyze trade data specifically for the Superrare NFT project.

MODEL: tofu_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'tofu'. This enables data analysts to easily query and analyze trade data for NFTs specifically related to the Tofu project.

MODEL: x2y2_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'x2y2'. This enables data analysts to easily query and analyze trade data specific to project x2y2.

MODEL: zonic_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'zonic'. This enables data analysts to easily query and analyze trade data specific to the Zonic project.

MODEL: zora_trades_view.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_trades' and filters the results to only include rows where the 'project' column equals 'zora'. This enables data analysts to easily query and analyze trade data specific to the Zora project.

MODEL: nft_burns.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This SQL model selects all columns from a table called 'nft_events_old' where the event type is equal to 'Burn'. This enables data analysts to easily filter and analyze specific events related to burning NFTs.

MODEL: nft_fees.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This new dbt SQL model enables data analysts to query and filter the 'nft_events' table by selecting all columns where the event type is equal to 'Trade'. This allows for more targeted analysis of trade events within the NFT ecosystem.

MODEL: nft_trades.sql

🟢 Added by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: This dbt SQL model selects all columns from a table called 'nft_events' and filters the results to only include rows where the 'evt_type' column equals 'Trade'. This enables data analysts to easily query and analyze trade events within this specific dataset.

MODEL: blur_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3284, Restructure Blur to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: This SQL model creates a view that combines sales data from two different Ethereum exchanges, Blur and Seaport. The resulting table includes information about the date, time, block number, contract addresses of NFTs sold and bought on each exchange as well as their respective token IDs. It also provides details about the seller and buyer of each transaction along with its category (buy or sell), type (secondary) and price in raw format. Additionally it calculates royalty fees for both exchanges while hardcoding platform fee to 0%. This enables data analysts to analyze sales trends across multiple platforms in one place.

MODEL: zora_v1_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: This SQL model creates a table that enables data analysts to track NFT trades on the Zora marketplace. The table includes information such as block date, block time, project contract address, transaction hash, NFT token ID and amount traded. It also categorizes trades as primary or secondary and identifies buyers and sellers by their wallet addresses. Additionally, it captures trade prices in both raw decimal format and currency contracts used for payment while excluding auction house sales from its results.

MODEL: zora_v2_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: This SQL model creates a table that tracks secondary auctions of NFTs on the Zora platform. It includes information such as the date and time of the auction, block number, contract addresses for both project and NFT tokens, buyer and seller information, price in raw format along with currency contract details. This enables data analysts to analyze trends in secondary market sales on Zora's platform over time. The model also has an optional incremental feature that only pulls data from auctions within the last week if specified by users.

MODEL: zora_v3_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: This SQL model creates a table that tracks secondary market trades of NFTs on the Zora platform. It enables data analysts to analyze trade volume, prices, and fees for different categories of trades (such as offers accepted or private sales) and different types of NFTs. The model also includes information about royalty payouts to creators based on the sale price of their work.

SECTOR: staking

toggle to see all model updates

MODEL: staking_ethereum_entities.sql

🟠 Modified by:

🔧 PR: #3346, Staking entity update (stakefish)
🧙 Author: @hildobby on 2023-05-17
📝 Summary: In this SQL model, a list of cryptocurrency exchanges and staking pools is being defined. The removed line was for a stakefish pool that has been forked and the new line added explains that it is not controlled by stakefish anymore. The rest of the lines define various exchanges such as Gemini, WEX Exchange, Celsius etc., along with their names and categories like CEX (Centralized Exchange), Liquid Staking or Staking Pools.

SECTOR: chain_info

toggle to see all model updates

MODEL: chain_info_dune_chains.sql

🟢 Added by:

🔧 PR: #3339, ENH: New table to facilitate matching chain_id -> chain_name in prices tables
🧙 Author: @cc7768 on 2023-05-17
📝 Summary: This SQL model creates a table that maps Dune Analytics chain names to their corresponding chain IDs. This enables data analysts to easily join and analyze data across different chains using the standardized IDs instead of having to manually match up the various naming conventions used by different protocols.

SECTOR: quickswap

toggle to see all model updates

MODEL: quickswap_polygon_trades.sql

🟠 Modified by:

🔧 PR: #3313, Add Quickswap v2 to dex.trades
🧙 Author: @darvinrio on 2023-05-17
📝 Summary: In this diff of a dbt SQL model, a reference to 'quickswap_v2_polygon_trades' has been added to the existing reference for 'quickswap_v3_polygon_trades'. This means that both tables will now be included in the set of models referred to as 'quickswap_polygon_models'.

MODEL: quickswap_v2_polygon_trades.sql

🟢 Added by:

🔧 PR: #3313, Add Quickswap v2 to dex.trades
🧙 Author: @darvinrio on 2023-05-17
📝 Summary: This SQL model creates a view that enables data analysts to query Quickswap v2 factory deployment on the Polygon network. The view includes information such as blockchain, project, version, block date and time, token bought and sold symbols and amounts (both raw and converted), USD amount of tokens traded if available or calculated from prices in USD otherwise. It also provides addresses for tokens bought/sold/taker/maker/project contract/transactions along with their trace address within the transaction hash.

SECTOR: clipper

toggle to see all model updates

MODEL: clipper_trades.sql

🟠 Modified by:

🔧 PR: #3311, Add clipper.exchange on Optimism
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: In this SQL model, a list of clipper models is defined. The clipper_polygon_trades model was removed and then added back to the list, while the clipper_optimism_trades model was added to the list.

MODEL: clipper_coves_v1_optimism_trades.sql

🟢 Added by:

🔧 PR: #3311, Add clipper.exchange on Optimism
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a table that enables data analysts to track token swaps on the Clipper project's CoveSwap feature on the Optimism blockchain. The table includes information such as block time, taker and maker addresses, token amounts and symbols, contract addresses, transaction hashes and trace address. Additionally it calculates USD value of tokens swapped using current prices from an external source. This model can be used for analysis of trading volumes or liquidity pools in relation to specific tokens or pairs over time periods specified by users (either since a certain date or within the last week).

MODEL: clipper_optimism_trades.sql

🟢 Added by:

🔧 PR: #3311, Add clipper.exchange on Optimism
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a view that combines data from three different Clipper DEX models into one table. The resulting table includes information about trades made on the blockchain, such as token symbols, amounts bought and sold, USD value of the trade, addresses involved in the transaction and more. This enables data analysts to easily query and analyze trading activity across multiple versions of Clipper's decentralized exchange platform.

MODEL: clipper_v1_optimism_trades.sql

🟢 Added by:

🔧 PR: #3311, Add clipper.exchange on Optimism
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze transaction data from the Clipper project on the Optimism blockchain. The view includes information such as token pair, amount bought/sold, USD value of transactions, contract addresses involved in each transaction, and more. It also joins with other tables to provide additional context such as token symbols and prices at the time of each transaction. This allows for deeper analysis of trading activity on this specific platform within this blockchain ecosystem.

MODEL: clipper_v2_optimism_trades.sql

🟢 Added by:

🔧 PR: #3311, Add clipper.exchange on Optimism
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a table that enables data analysts to query and analyze transaction data from the Clipper exchange on the Optimism blockchain. The table includes information such as token pair, amount of tokens bought/sold, USD value of transactions, addresses involved in transactions (taker/maker), contract address for the project, and more. This allows analysts to gain insights into trading activity on this specific exchange and blockchain. The model also incorporates incremental updates based on block time or date range criteria specified by users.

MODEL: clipper_arbitrum_trades.sql

🟠 Modified by:

🔧 PR: #3318, Add clipper.exchange Coves
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: In this SQL model, a list of two clipper models is defined using the set function. The first model named 'clipper_v1_arbitrum_trades' is already present in the codebase and no changes were made to it. The second model named 'clipper_coves_v1_arbitrum_trades' was added in this pull request.

MODEL: clipper_coves_v1_arbitrum_trades.sql

🟢 Added by:

🔧 PR: #3318, Add clipper.exchange Coves
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze transaction data from the Clipper project on the Arbitrum blockchain. The view includes information such as token pair, amount of tokens bought/sold, USD value of transactions, addresses involved in transactions and more. It also joins with other tables to provide additional context such as token symbols and prices at the time of transaction. This model supports incremental updates based on a specified start date or within the last week if no start date is provided.

MODEL: clipper_coves_v1_polygon_trades.sql

🟢 Added by:

🔧 PR: #3318, Add clipper.exchange Coves
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze transaction data from the Clipper project on the Polygon blockchain. The view includes information such as token pair, amount of tokens bought/sold, USD value of transactions, addresses involved in transactions and more. It also joins with other tables to provide additional context such as token symbols and prices at the time of transaction. This model supports incremental updates based on block time or last week's date for efficient querying over large datasets.

MODEL: clipper_polygon_trades.sql

🟠 Modified by:

🔧 PR: #3318, Add clipper.exchange Coves
🧙 Author: @amalashkevich on 2023-05-17
📝 Summary: A new reference to a SQL model called 'clipper_coves_v1_polygon_trades' was added to the existing list of references named 'clipper_models'.

SECTOR: cryptopunks

toggle to see all model updates

MODEL: cryptopunks_ethereum_all_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a SQL model. The main logic added includes selecting data from different sources and combining them using UNION ALL, renaming columns, casting NULL values as varchar or double, grouping the results by certain columns and ordering them in descending order based on an event block number. Some column names were removed while others were added back with no significant change in their position within the query.

MODEL: cryptopunks_ethereum_current_bids.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model is updated to include a new table called cryptopunks_ethereum_events. The logic of the code remains the same, with some minor changes in syntax and formatting. The model still calculates bid amounts for each punk ID based on Ethereum prices, filters out withdrawn bids or those that have been accepted by other bidders, and cancels open bids if the bidder buys or transfers ownership of a punk. Finally, it sorts results by block number and index in descending order.

MODEL: cryptopunks_ethereum_current_listings.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The SQL model has undergone some changes. The source table cryptopunks_ethereum_trades was replaced with cryptopunks_ethereum_events. A new CTE called latest_eth_price was added to get the latest Ethereum price from a different source. There were no significant changes in the logic of other CTEs, but there were minor formatting and syntax updates such as removing extra spaces and adding missing ones. Finally, the main query had an addition of a condition to filter by event_sub_type 'Public Listing' along with existing conditions for punk_event_index = 1 and event_type = 'Offered'.

MODEL: cryptopunks_ethereum_floor_price_over_time.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The changes made to the SQL model involve adding and removing lines of code. The main logic added includes creating a new CTE called all_punk_events that combines data from three other CTEs, filtering out duplicates, and then aggregating the data by day. Additionally, there are some minor changes such as renaming columns and adjusting formatting. Overall, these modifications seem to be focused on improving efficiency in querying punk-related events while also providing more accurate pricing information for each day based on USD values obtained from an external source.

MODEL: cryptopunks_ethereum_listings_over_time.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The changes made to the SQL model involve adding and removing lines of code. The main logic added includes creating a new CTE called all_punk_events that combines data from three other CTEs, using window functions to calculate row numbers for each punk event, and joining tables based on specific conditions. Additionally, there are minor changes such as renaming columns and adjusting whitespace in the code. Overall, these modifications aim to improve data aggregation by providing more accurate information about active listings per day for Cryptopunks Ethereum trades.

MODEL: cryptopunks_ethereum_punk_offer_events.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows changes made to a dbt SQL model. The materialization is set to incremental with merge strategy and delta file format. A unique key constraint was added on three columns. The select statement retrieves data from two tables, one for Offered events and the other for Offer Withdrawn events, using union all operator.The where clause filters out certain rows based on conditions such as time range or existence in other tables.A left join is performed with another table named 'prices'.

SECTOR: superrare

toggle to see all model updates

MODEL: superrare_ethereum_usernames.sql

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: The diff shows that there were no changes to the SELECT statement, but a new row was added to the VALUES clause of the SQL model. The new row includes information about an Ethereum address, its associated name on Superrare platform, and other metadata such as blockchain type and contributor details.

SECTOR: trove

toggle to see all model updates

MODEL: trove_v1_arbitrum_nft_samples.csv

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model trove_v1_arbitrum_nft_samples.csv was renamed.

MODEL: trove_v2_arbitrum_nft_samples.csv

🟠 Modified by:

🔧 PR: #3253, Big NFT sector cleanup!
🧙 Author: @0xRobin on 2023-05-17
📝 Summary: [changes too large] The model trove_v2_arbitrum_nft_samples.csv was renamed.

SECTOR: gitcoin

toggle to see all model updates

MODEL: gitcoin_ethereum_donations.sql

🟢 Added by:

🔧 PR: #3298, Gitcoin Donations
🧙 Author: @hildobby on 2023-05-16
📝 Summary: This dbt SQL model creates a table that summarizes Gitcoin donations made in Ethereum. It includes information such as the amount donated, donor and recipient addresses, currency symbol and contract address, block number and time of donation. Additionally, it calculates the USD value of each donation based on current market prices at the time of transaction. This model enables data analysts to easily analyze Gitcoin donations made in Ethereum by various dimensions such as project name or grant round.

MODEL: gitcoin_donations.sql

🟢 Added by:

🔧 PR: #3298, Gitcoin Donations
🧙 Author: @hildobby on 2023-05-16
📝 Summary: This SQL model merges two Gitcoin donation tables, one for Ethereum and one for Polygon. It creates a single table that includes information on the blockchain, project, version, grant round, block date and time of each donation transaction. Additionally it provides details on the amount donated in both raw and original currency values as well as donor and recipient addresses. This merged table enables data analysts to easily query all Gitcoin donations across multiple blockchains in a single location.

MODEL: gitcoin_grant_round_dates.sql

🟢 Added by:

🔧 PR: #3298, Gitcoin Donations
🧙 Author: @hildobby on 2023-05-16
📝 Summary: This SQL model creates a temporary table with information about various rounds, including their names and start/end dates. This enables data analysts to easily reference this information in queries or analyses related to these rounds.

MODEL: gitcoin_polygon_donations.sql

🟢 Added by:

🔧 PR: #3298, Gitcoin Donations
🧙 Author: @hildobby on 2023-05-16
📝 Summary: This SQL model creates a view of Gitcoin donations on the Polygon blockchain, including information such as the amount donated in both raw and original currency values, donor and recipient addresses, token contract address and symbol. It also calculates the USD value of each donation based on current exchange rates. The model enables data analysts to easily query Gitcoin donation data for analysis or reporting purposes.

SECTOR: blur

toggle to see all model updates

MODEL: blur_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3284, Restructure Blur to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: The SQL model is a union of two select statements that query the Ethereum blockchain for transactions related to the 'blur' project. The first select statement joins tables and filters by payment token, while also checking if it's an incremental run. The second select statement only selects from one table and doesn't have any additional filters or joins. Both queries are filtered by events that occurred within the last week.

SECTOR: ironbank

toggle to see all model updates

MODEL: ironbank_ethereum_itokens.sql

🟠 Modified by:

🔧 PR: #3325, add iWSTETH to ironbank itokens
🧙 Author: @mmibmm on 2023-05-16
📝 Summary: In this diff of a SQL model, one line was removed and two lines were added. The removed line was for the iUNI token, while the added lines were for iUNI and iWSTETH tokens. The model includes columns for symbol and contract address as well as decimals and underlying symbol information.

SECTOR: zora

toggle to see all model updates

MODEL: zora_ethereum_events.sql

🟠 Modified by:

🔧 PR: #3322, Restructure Zora to new NFT trades setup
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: A new common table expression (CTE) named 'zora_trades' was added to the SQL model. It selects a version and block time from a specific column in another CTE called 'z3_o1_ee'.

SECTOR: paraswap

toggle to see all model updates

MODEL: paraswap_arbitrum_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a unified table of trade data from the Paraswap v5 Arbitrum DEX. It enables data analysts to easily query and analyze trade information across multiple versions of the DEX, including details such as token symbols, amounts, addresses, and transaction hashes. The resulting table can be used for various analyses such as liquidity tracking or market trend analysis.

MODEL: paraswap_v5_arbitrum_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade events on the Arbitrum blockchain for the ParaSwap project. The view includes information such as token pair, amount bought/sold, USD value of trades, taker/maker addresses and contract addresses. It also joins with other tables to provide additional details such as token symbols and prices at the time of each trade event. This allows analysts to gain insights into trading activity on ParaSwap in order to inform investment decisions or identify trends in user behavior.

MODEL: paraswap_v5_avalanche_c_trades.sql

🟠 Modified by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: The SQL model adds a block number column to the dexs table and joins it with the transactions table on both transaction hash and block number. The join is conditional on whether or not it's an incremental build, in which case only transactions after a certain date are included.

MODEL: paraswap_bnb_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a union of two existing dbt models, paraswap_v4_bnb_trades and paraswap_v5_bnb_trades, allowing data analysts to query both sets of data together. The resulting table includes information on blockchain transactions such as token symbols, amounts bought and sold, addresses involved in the transaction, contract addresses used for the trade, and more.

MODEL: paraswap_v4_bnb_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade events from the ParaSwap decentralized exchange on the Binance Smart Chain. The view includes information such as block time, taker/maker addresses, token pair traded, amounts bought/sold in both raw and converted USD values, project contract address and transaction hash. It also joins with other tables to provide additional details such as token symbols/decimals/prices for each trade event. This allows analysts to gain insights into trading activity on ParaSwap on BSC over time.

MODEL: paraswap_v5_bnb_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade events from the ParaSwap decentralized exchange on the Binance Smart Chain. The view includes information such as block time, taker/maker addresses, token pair traded, amounts bought/sold in both raw and converted USD values, project contract address and transaction hash. It also joins with other tables to provide additional details such as token symbols/decimals/prices for each trade event. This allows analysts to gain insights into trading activity on ParaSwap on BSC over time periods specified by parameters like project_start_date.

MODEL: paraswap_ethereum_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a union of two existing dbt models, paraswap_v4_ethereum_trades and paraswap_v5_ethereum_trades, allowing data analysts to query both sets of trade data together. The resulting table includes information such as token symbols, amounts bought and sold, USD value, addresses involved in the transaction, and more. This enables analysts to perform deeper analysis on Paraswap's Ethereum trades across multiple versions.

MODEL: paraswap_v4_ethereum_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: [changes too large] The model paraswap_v4_ethereum_trades.sql was added.

MODEL: paraswap_v5_ethereum_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: [changes too large] The model paraswap_v5_ethereum_trades.sql was added.

MODEL: paraswap_v5_fantom_trades.sql

🟠 Modified by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: The SQL model adds a block number column to the dexs table and joins it with the transactions table on both transaction hash and block number. The join is conditional on whether or not it's an incremental build, in which case only transactions after a certain date are included.

MODEL: paraswap_optimism_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that combines data from the 'paraswap_v5_optimism_trades' table and any other tables specified in the 'paraswap_models' list. The resulting view includes information about blockchain transactions, including token symbols, amounts, addresses, and contract details. This enables data analysts to easily query and analyze transactional data across multiple sources within a single view.

MODEL: paraswap_v5_optimism_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This dbt SQL model creates a table that enables data analysts to query and analyze trade events from the Paraswap project on the Optimism blockchain. The resulting table includes information such as token pair, amount bought/sold, USD value of trades, taker/maker addresses and contract details. It also joins with other tables to provide additional context such as token symbols and prices at the time of each trade event. This model supports incremental updates for efficient processing over time.

MODEL: paraswap_trades.sql

🟠 Modified by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: The diff of the SQL model shows that several references to different trades tables were added, including those for Arbitrum, Binance Smart Chain (BNB), Ethereum, Optimism and Polygon. These new references were added to a list called 'paraswap_models' which already contained two existing trade table references.

MODEL: paraswap_polygon_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a union of two existing dbt models, paraswap_v4_polygon_trades and paraswap_v5_polygon_trades, to provide data analysts with a single table containing trade information from both versions of the ParaSwap decentralized exchange on the Polygon blockchain. The resulting table includes details such as token symbols, amounts bought and sold, transaction hashes, addresses involved in trades, and more.

MODEL: paraswap_v4_polygon_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade events on the Polygon network for the ParaSwap project. The view includes information such as token pair, amount bought/sold, USD value of trades, taker/maker addresses and contract address. It also joins with other tables to provide additional details such as token symbols and prices at the time of trade. This allows analysts to gain insights into trading activity on ParaSwap in order to inform investment decisions or track market trends over time.

MODEL: paraswap_v5_polygon_trades.sql

🟢 Added by:

🔧 PR: #3288, Paraswap dex add more blockchain
🧙 Author: @springzh on 2023-05-16
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade events on the Polygon network for the ParaSwap project. The view includes information such as token pair, amount bought/sold, USD value of trades, taker/maker addresses and contract address. It also joins with other tables to provide additional information about tokens and prices at the time of each trade event. This allows analysts to gain insights into trading activity on ParaSwap in order to inform investment decisions or improve user experience.

SECTOR: cow_protocol

toggle to see all model updates

MODEL: cow_protocol_ethereum_solvers.sql

🟠 Modified by:

🔧 PR: #3285, CoW Protocol: New Solver Addresses
🧙 Author: @nlordell on 2023-05-16
📝 Summary: Rows were added to the known_solver_metadata table for various solvers, including Naive, Baseline and Gnosis. The rows include metadata such as address, environment and name of each solver. Some rows were also added for a new environment called 'barn'.

MODEL: cow_protocol_gnosis_solvers.sql

🟠 Modified by:

🔧 PR: #3285, CoW Protocol: New Solver Addresses
🧙 Author: @nlordell on 2023-05-16
📝 Summary: Rows were added to the known_solver_metadata table, including new addresses and corresponding solver names. The select statement was not changed except for removing a line that had no effect on the output. The SQL model joins two tables (registered_solvers and known_solver_metadata) using an outer join based on their address columns, then selects certain columns from them while replacing null values with 'Uncatalogued'.

MODEL: cow_protocol_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3352, [Bug] Fix Trade Surplus for Partial Fills
🧙 Author: @bh2smith on 2023-05-16
📝 Summary: The SQL model calculates the fill proportion of trades based on whether they are buy or sell orders. It also calculates the relative and absolute surplus in USD for each trade. The 'partial_fill' column is added to indicate if a trade was partially filled, while the 'fill_proportion' column is added to calculate how much of an order was filled. Finally, these columns are used to calculate the surplus_usd by multiplying with usd_value and using atoms_bought/sold and limit_buy/sell_amounts in their respective formulas.

SECTOR: balancer

toggle to see all model updates

MODEL: balancer_arbitrum_trades.sql

🟠 Modified by:

🔧 PR: #3283, Fix Balancer Trades
🧙 Author: @viniabussafi on 2023-05-16
📝 Summary: In this SQL model, a new condition has been added to filter out certain rows from the source tables. Specifically, any row where the 'tokenIn' or 'tokenOut' column is equal to the 'poolAddress' column will be excluded. Additionally, some changes have been made to how time-based filtering is applied depending on whether it's an incremental or full-refresh run. No other significant changes were made in this pull request diff.

MODEL: balancer_v2_ethereum_trades.sql

🟠 Modified by:

🔧 PR: #3283, Fix Balancer Trades
🧙 Author: @viniabussafi on 2023-05-16
📝 Summary: The added code filters out certain tokens from the Balancer V2 Ethereum Vault_evt_Swap table by checking if they are not equal to the pool address. Additionally, it modifies the WHERE clause for incremental and non-incremental builds to filter events based on their block time. No changes were made in the 'prices' CTE or any other part of this SQL model.

MODEL: balancer_gnosis_trades.sql

🟠 Modified by:

🔧 PR: #3283, Fix Balancer Trades
🧙 Author: @viniabussafi on 2023-05-16
📝 Summary: In this SQL model, a new condition has been added to the join statement in the v2 CTE. The condition filters out rows where tokenIn and tokenOut are equal to poolAddress. Additionally, changes have been made to the WHERE clause for is_incremental() and not is_incremental() blocks by replacing 'where' with 'AND'. No other significant changes were made in this diff of dbt SQL model.

MODEL: balancer_optimism_trades.sql

🟠 Modified by:

🔧 PR: #3283, Fix Balancer Trades
🧙 Author: @viniabussafi on 2023-05-16
📝 Summary: The added logic filters out certain token pairs in the Vault_evt_Swap table and adds a condition to filter events based on their block time. The removed logic changes the syntax of filtering by block time. In addition, an inner join is added to link two tables together, and a left join is modified to include another condition for matching contract addresses.

MODEL: balancer_polygon_trades.sql

🟠 Modified by:

🔧 PR: #3283, Fix Balancer Trades
🧙 Author: @viniabussafi on 2023-05-16
📝 Summary: The added logic filters out certain tokens from the Balancer V2 Polygon Vault_evt_Swap table by checking if they are not equal to the pool address. Additionally, it modifies the WHERE clause for incremental and non-incremental builds to filter events based on their block time. No columns or specific lines were mentioned in this diff of a dbt SQL model.

SECTOR: zeroex

toggle to see all model updates

MODEL: zeroex_api_fills_deduped.sql

🟠 Modified by:

🔧 PR: #3354, exclude polygon from 0x trades
🧙 Author: @jeff-dude on 2023-05-16
📝 Summary: The diff shows that a comment was added to exclude certain models in the short term. The excluded model is 'zeroex_polygon_api_fills_deduped'. This exclusion is reflected in the list of models, where this model has been removed from the list.

MODEL: zeroex_polygon_api_fills_deduped.sql

🟠 Modified by:

🔧 PR: #3353, Exclude zeroex_polygon_api_fills_deduped.sql
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: The change made to the SQL model is the addition of a semicolon at the end of the query. This does not affect or modify any logic in the existing code, but it ensures that multiple queries can be executed together without causing errors.

MODEL: zeroex_polygon_api_fills.sql

🟠 Modified by:

🔧 PR: #3349, Exclude zeroex_polygon_api_fills.sql
🧙 Author: @0xRobin on 2023-05-16
📝 Summary: The diff shows a change in the WHERE clause of an SQL query. The line that was removed excluded a specific transaction hash, while the line that was added is identical to the previous one and also excludes this same transaction hash. The rest of the code includes several LEFT OUTER JOIN statements joining different tables based on certain conditions, with some filtering done using WHERE clauses and variables defined elsewhere in the model.