📰 2023-06-09: Weekly Prophet! #3501
andrewhong5297
announced in
Prophet (Weekly Updates)
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is your weekly summary of 47 PRs merged from 25 wizards. Great job everyone! 🎉
We had 76 added models 🟢 and 118 modified models 🟠 for 65 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_aggregator_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In the given diff of the SQL model, one reference model was added which is 'dodo_aggregator_trades'. No reference models were removed.
MODEL: dex_trades_seed.csv
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: [changes too large] The model dex_trades_seed.csv was modified.
MODEL: dex_pools.sql
🟠 Modified by:
🔧 PR: #3445, add wigoswap fantom pools to dex _pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: A reference to a new table called 'wigoswap_fantom_pools' was added to the SQL model, which is being merged into an existing set of tables including 'uniswap_pools', 'spiritswap_fantom_pools', and others.
🔧 PR: #3445, add spartacus exchange pools to dex pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: In this diff of a dbt SQL model, a reference to 'spartacus_exchange_fantom_pools' has been added. The other references are unchanged.
🔧 PR: #3445, add equalizer exchange pools to dex pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: In this diff of a dbt SQL model, a reference to 'equalizer_exchange_fantom_pools' has been added. The other references remain the same as before.
🔧 PR: #3445, add spiritswap_fantom_pools to dex pools - ready for review
🧙 Author: @henrystats on 2023-06-06
📝 Summary: In this SQL model, a set of three dbt models are defined using the
setfunction. The first model isuniswap_pools, and two additional models have been added to the set:spiritswap_fantom_poolsandspookyswap_fantom_pools.🔧 PR: #3445, add spookyswap pools to dex pools - ready for review
🧙 Author: @henrystats on 2023-06-05
📝 Summary: The added code is adding a reference to a new table called 'spookyswap_fantom_pools' in addition to the existing 'uniswap_pools' table. These tables are part of the dex_pool_models list, which is used elsewhere in the SQL model. No other changes were made.
SECTOR: nft
toggle to see all model updates
MODEL: nft_arbitrum_aggregators.sql
🟠 Modified by:
🔧 PR: #3480, Add Reservoir v6.0.1 aggregator contracts
🧙 Author: @hildobby on 2023-06-06
📝 Summary: A new contract address and name were added to the SQL model. The contract address belongs to Reservoir v6.0.1, while the name is simply 'Reservoir'.
MODEL: nft_bnb_aggregators.sql
🟠 Modified by:
🔧 PR: #3480, Add Reservoir v6.0.1 aggregator contracts
🧙 Author: @hildobby on 2023-06-06
📝 Summary: A new contract address and name were added to the SQL model for Reservoir v6.0.1, joining three other contracts including Element NFT Marketplace Aggregator, Oxalus NFT Aggregator, and Uniswap's Universal Router in a temporary table called 'temp_table'.
MODEL: nft_ethereum_aggregators_manual.sql
🟠 Modified by:
🔧 PR: #3480, Add Reservoir v6.0.1 aggregator contracts
🧙 Author: @hildobby on 2023-06-06
📝 Summary: A new contract address for Reservoir v6.0.1 was added to the SQL model, while some other contracts were already present in the original model and remained unchanged.
MODEL: nft_optimism_aggregators.sql
🟠 Modified by:
🔧 PR: #3480, Add Reservoir v6.0.1 aggregator contracts
🧙 Author: @hildobby on 2023-06-06
📝 Summary: A contract address and name were added to a temporary table in the SQL model. The contract belongs to Reservoir v6.0.1, which was not previously included in the model's list of contracts.
MODEL: nft_polygon_aggregators.sql
🟠 Modified by:
🔧 PR: #3480, Add Reservoir v6.0.1 aggregator contracts
🧙 Author: @hildobby on 2023-06-06
📝 Summary: A contract address and name for Reservoir v6.0.1 was added to a temporary table that already contained addresses and names for Uniswap, BitKeep, and OKX.
MODEL: nft_mints.sql
🟠 Modified by:
🔧 PR: #3471, NFT mints
🧙 Author: @0xRobin on 2023-06-05
📝 Summary: This SQL model adds a new set of tables called
project_mintswhich is a union of four different tables. The resulting table contains information about blockchain transactions where NFTs were minted. This data is then used in the subsequent CTE callednative_mints.MODEL: nft_arbitrum_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions. The filter checks if a transaction is a flashloan by joining two tables and comparing their values. If the transaction is not a flashloan, it returns false; otherwise, it returns true. The result of this filter is used in conjunction with other filters to determine whether or not a trade constitutes wash trading.
MODEL: nft_avalanche_c_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions by joining two tables and checking if a specific column is null. The result of this filter is used in an existing logic that determines whether a trade is considered a wash trade or not. No other significant changes were made to the model, except for some minor adjustments related to syntax and formatting.
MODEL: nft_bnb_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions by joining two tables and checking if a specific column is null. The result of this filter is used in an existing logic that determines whether a trade is considered a wash trade or not. No other significant changes were made to the model, except for some minor adjustments related to syntax and formatting.
MODEL: nft_ethereum_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions by joining two tables and checking if a specific column is null. The result of this filter is used in an existing logic that determines whether a trade is considered as wash trade or not. No other significant changes were made to the model, except for some minor modifications such as adding aliases and changing indentation.
MODEL: nft_gnosis_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan trades by checking if a trade's transaction hash is not present in the
dex_flashloanstable. The result of this filter is used as an input for another filter that checks if a trade is part of wash trading. If any of several conditions are met, including being identified as a flashloan trade, then it will be marked as such in the output.MODEL: nft_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter called 'filter_5_flashloan' was added to the existing filters in a dbt SQL model. The model is based on an nft_wash_model and includes filters for back-and-forth trades, buying or selling three times, first funding by the same wallet, and wash trading.
MODEL: nft_optimism_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions by checking if a trade's transaction hash is not present in the
dex_flashloanstable. The result of this filter is used as an input for another filter calledis_wash_trade, which determines whether a trade should be classified as wash or not based on several conditions, including whether it involves the same buyer and seller, back-and-forth trading, buying/selling three times or more, being funded by the same wallet address and now also involving flashloans.MODEL: nft_polygon_wash_trades.sql
🟠 Modified by:
🔧 PR: #3360, Add Flashloans to NFT Wash Filter
🧙 Author: @hildobby on 2023-06-05
📝 Summary: A new filter was added to the SQL model that identifies flashloan transactions by joining two tables and checking if a specific column is null. The result of this filter is used in an existing logic that determines whether a trade is considered a wash trade or not. No other significant changes were made to the model, except for some minor adjustments related to syntax and formatting.
SECTOR: labels
toggle to see all model updates
MODEL: labels_l2_batch_submitters.sql
🟢 Added by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model creates a new table called 'l2_batch_submitters' that contains information about Ethereum Layer 2 batch submitters. The table includes columns for blockchain, address, name (a combination of several other columns), category, contributor, source, created_at timestamp and updated_at timestamp. This model enables data analysts to easily access and analyze information about Ethereum Layer 2 batch submitters in their infrastructure.
MODEL: labels_l2_fee_vaults.sql
🟢 Added by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model creates a view called 'l2_fee_vaults' that selects data from the 'addresses_optimism_fee_vaults' table. It includes columns for blockchain, address, vault name, category, contributor and source. The view also adds two timestamp columns for creation and update dates as well as a label type column. This model enables data analysts to easily access information about fee vaults on the Optimism blockchain in order to analyze infrastructure costs and identify trends over time.
MODEL: labels_system_addresses.sql
🟠 Modified by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: The removed code was a reference to two system addresses in the 'temp_table' table. The addresses were related to the Optimism - L1 Attributes Depositor Contract and Predeployed Contract, respectively.
MODEL: labels_balancer_v2_gauges_arbitrum.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The added SQL model selects distinct values for the column 'arbitrum' as blockchain. There is no removal in this diff.
MODEL: labels_cex_users.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The following token symbols were added or removed: ethereum.
MODEL: labels_cex.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The model added the following reference models: labels_cex_arbitrum, labels_cex_avalanche_c, labels_cex_bitcoin, labels_cex_bnb,labels_cex_fantom ,labels_optimism. No reference models were removed in this diff.
MODEL: labels_cex_arbitrum.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This new dbt SQL model creates a table that maps blockchain addresses to their corresponding distinct names, contributors, and categories. It enables data analysts to easily identify institutions associated with specific blockchain addresses. The model also includes metadata such as creation date and source information for each entry in the table.
MODEL: labels_cex_avalanche_c.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that maps blockchain addresses to distinct names, categories, and contributors. It enables data analysts to easily identify the institutions associated with specific blockchain addresses. The model also includes information on when each entry was added and last updated. This can be useful for tracking changes over time or identifying potential errors in the data set.
MODEL: labels_cex_bitcoin.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The added or removed token symbols cannot be determined from the given SQL model as it does not contain any information about tokens.
MODEL: labels_cex_bnb.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The added or removed token symbols cannot be determined from the given SQL model as it only contains addresses and names of institutions.
MODEL: labels_cex_ethereum.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: [changes too large] The model labels_cex_ethereum.sql was modified.
MODEL: labels_cex_fantom.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The added token symbols are not explicitly mentioned in the diff of this SQL model. Therefore, I cannot provide a comma-separated list of added or removed tokens.
MODEL: labels_cex_optimism.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that maps blockchain addresses to distinct names, categories, and contributors. It enables data analysts to easily query this information for institutions on the specified blockchain. The model also includes timestamps for when each entry was added and updated, as well as a label type identifier.
MODEL: labels_cex_polygon.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that maps blockchain addresses to distinct names, categories, and contributors. It enables data analysts to easily identify institutions associated with specific blockchain addresses. The model also includes timestamps for when the information was added and updated, as well as a label type identifier.
MODEL: labels_institution.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: I'm sorry, but I cannot summarize the SQL model without seeing it. Can you please provide me with the diff of the model?
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_optimism_erc20.sql
🟠 Modified by:
🔧 PR: #3377, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: Based on the diff of the SQL model, it is not possible to determine which token symbols were added or removed.
MODEL: tokens_optimism_erc20_curated.sql
🟠 Modified by:
🔧 PR: #3377, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: Several tokens were added to a SQL model called
raw_token_list. The new tokens include GIV, HAUS, AMKT, IBEX, RFWSTETH,VITA ,PIKA,RPL , EXTRA and MINE. Each token has its contract address,symbol name and decimals specified in the model.MODEL: tokens_optimism_nft_curated.sql
🟠 Modified by:
🔧 PR: #3470, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model shows a diff of added and removed contract addresses and their corresponding names. Five new contracts were added, including OP-ARMY-DSBT, Gitcoin Passport Score (Unaffiliated), Treasure Fragments in Another World, Bedrock, and Myhome. Two contracts were removed: _404/LostLayer and Caravaggio Editions.
🔧 PR: #3470, [EASY]Add new Optimism NFTs
🧙 Author: @chuxinh on 2023-06-06
📝 Summary: The diff of the SQL model shows that several contract addresses and their corresponding names were added to a temporary table. No contracts were removed from the table.
MODEL: tokens_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #3467, Adding EUROC to avalanche_c_erc20 tokens
🧙 Author: @discochuck on 2023-06-06
📝 Summary: The token symbol that was added is 'EUROC'.
MODEL: tokens_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #3460, [Erc20] Add 410 Missing Mainnet Tokens
🧙 Author: @bh2smith on 2023-06-05
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
🔧 PR: #3460, Revert '[Erc20] Adding 477 missing tokens to mainnet (#3460)'
🧙 Author: @jeff-dude on 2023-06-02
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
🔧 PR: #3460, [ERC20] [Easy] Add missing & new tokens
🧙 Author: @gentrexha on 2023-06-05
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
🔧 PR: #3460, [Erc20] Adding 477 missing tokens to mainnet
🧙 Author: @bh2smith on 2023-06-02
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
MODEL: tokens_gnosis_erc20.sql
🟠 Modified by:
🔧 PR: #3444, [Erc20] Add 410 Missing Mainnet Tokens
🧙 Author: @bh2smith on 2023-06-05
📝 Summary: The added token symbol is 'CRC'.
🔧 PR: #3444, [ERC20] [Easy] Add missing & new tokens
🧙 Author: @gentrexha on 2023-06-05
📝 Summary: The token symbol that was added is '𝚫'. No tokens were removed.
MODEL: tokens_optimism_erc20_bridged_mapping.sql
🟠 Modified by:
🔧 PR: #3466, Fix OP ERC20 Bridged Mapping Duplicate
🧙 Author: @MSilb7 on 2023-06-03
📝 Summary: The diff shows changes made to a SQL model that selects data from an Ethereum bridge event table. The change adds a filter condition to exclude bad events and modifies the date range filter for incremental updates. The output columns remain unchanged, with null values assigned to symbol and decimals columns. Finally, the query groups results by two token addresses extracted from the source table's
_l1Tokenand_l2Tokenfields respectively.MODEL: tokens_optimism_erc20_generated.sql
🟠 Modified by:
🔧 PR: #3466, Fix OP ERC20 Bridged Mapping Duplicate
🧙 Author: @MSilb7 on 2023-06-03
📝 Summary: This SQL model adds and removes lines of code to a query that generates a list of unique tokens. The added lines filter the results by grouping them based on certain criteria, such as token type and source. Additionally, it ensures there are no duplicates with different symbols by ranking the tokens based on decimals and symbol in ascending order. Finally, it filters out any duplicate entries using the newly created token_rank column where only rows with rank 1 are selected for output.
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #3441, [EASY] Adding WINR into tokens.erc20
🧙 Author: @0xroll on 2023-06-05
📝 Summary: The token symbol 'WINR' was added to the model.
SECTOR: prices
toggle to see all model updates
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #3440, feat(prices): add ramses
🧙 Author: @echovl on 2023-06-08
📝 Summary: Two tokens were added to the model: RAM and WINR.
🔧 PR: #3440, add unshETH token to prices
🧙 Author: @RaveenaBhasin on 2023-06-05
📝 Summary: The token symbol 'unshETH' was added to the model.
🔧 PR: #3440, [EASY] Update prices_arbitrum_tokens.sql
🧙 Author: @0xroll on 2023-06-05
📝 Summary: Two tokens were added to the model: 'WINR' and '0xd77b108d4f6cefaa0cae9506a934e825becca46e'. One token was removed from the model: 'OATH'. Therefore, the comma-separated list of all token symbols that were added or removed is: WINR, OATH.
MODEL: prices_native_tokens.sql
🟠 Modified by:
🔧 PR: #3485, [quick] add celo to prices
🧙 Author: @MSilb7 on 2023-06-07
📝 Summary: The token symbol 'CELO' was added to the list.
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #3484, feat(prices): add DFI
🧙 Author: @gjj on 2023-06-07
📝 Summary: The token symbol 'DFI' was added to the model.
SECTOR: opensea
toggle to see all model updates
MODEL: opensea_v4_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3489, Exclude problematic tx in Seaport V2
🧙 Author: @0xRobin on 2023-06-08
📝 Summary: The SQL model is filtering transactions from the Seaport_evt_OrdersMatched and Seaport_evt_OrderFulfilled tables based on contract addresses. A new row was added to iv_platform_fee_wallet with a wallet address and name. The query also filters out specific transaction hashes from the result set.
MODEL: opensea_arbitrum_events.sql
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: This SQL model creates a union of two tables containing data on OpenSea transactions in the Arbitrum blockchain. The resulting table includes information such as token ID, collection, trade type, buyer and seller addresses, transaction hash and block number. This enables data analysts to perform analysis on OpenSea transactions in the Arbitrum blockchain using a single table instead of having to query multiple tables separately.
MODEL: opensea_arbitrum_fees.sql
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: This SQL model selects various fields from the 'opensea_arbitrum_events' table where the event type is a trade. The selected fields include information about blockchain, project, version, token ID, collection name and fees associated with platform and royalty. This model enables data analysts to analyze trades on OpenSea marketplace by providing detailed information about buyers/sellers involved in each transaction along with other relevant details such as contract addresses and unique trade IDs.
MODEL: opensea_arbitrum_schema.yml
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: [changes too large] The model opensea_arbitrum_schema.yml was added.
MODEL: opensea_arbitrum_trades.sql
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: This SQL model selects various columns from the 'opensea_arbitrum_events' table where the event type is a trade. The selected columns include information about blockchain, project, version, token ID and collection as well as details on trade amount in USD and original currency symbol. This model enables data analysts to analyze trading activity on OpenSea's marketplace for NFTs (non-fungible tokens) specifically on Arbitrum network.
MODEL: opensea_v3_arbitrum_events.sql
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: This SQL model creates a view that merges data from the
seaport_arbitrum_tradestable and filters it to only include trades with specifiednft_contract_address. It includes various columns related to trade details such as buyer, seller, token_id, amount_usd etc. The view is materialized and enables analysts to easily query and analyze trade data for the specified project/version on OpenSea's platform.MODEL: opensea_v4_arbitrum_events.sql
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: [changes too large] The model opensea_v4_arbitrum_events.sql was added.
MODEL: opensea_arbitrum_seaport_trades_samples.csv
🟢 Added by:
🔧 PR: #3324, Init opensea_arbitrum.events
🧙 Author: @sohwak on 2023-06-05
📝 Summary: [changes too large] The model opensea_arbitrum_seaport_trades_samples.csv was added.
MODEL: opensea_v3_polygon_events.sql
🟠 Modified by:
🔧 PR: #3421, Rework
opensea_v3_polygon.events🧙 Author: @sohwak on 2023-06-02
📝 Summary: [changes too large] The model opensea_v3_polygon_events.sql was modified.
MODEL: opensea_polygon_seaport_trades_samples.csv
🟠 Modified by:
🔧 PR: #3421, Rework
opensea_v3_polygon.events🧙 Author: @sohwak on 2023-06-02
📝 Summary: [changes too large] The model opensea_polygon_seaport_trades_samples.csv was modified.
SECTOR: seaport
toggle to see all model updates
MODEL: seaport_v2_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3489, Exclude problematic tx in Seaport V2
🧙 Author: @0xRobin on 2023-06-08
📝 Summary: The added code filters transactions from two specific contract addresses and excludes certain types of orders. It then groups the remaining trades by date, token contract address, and trade type. The removed code includes a filter for traded NFTs in addition to the existing order exclusion filter. Finally, there is an additional line that excludes two specific transaction hashes from being included in the results.
SECTOR: addresses
toggle to see all model updates
MODEL: addresses_ethereum_bridges.sql
🟠 Modified by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: The diff of the SQL model shows changes made to a table containing bridge addresses and their descriptions. The changes include adding, removing, renaming and duplicating some rows. Specifically, new rows were added for Optimism's L1StandardBridge, L1ERC721Bridge and their respective proxies as well as OptimismPortalProxy; while the row for Optimism: Gateway was removed but later duplicated with a different name. Other existing rows remained unchanged in this merged pull request.
MODEL: addresses_ethereum_l2_batch_submitters.sql
🟠 Modified by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This diff of a dbt SQL model adds and removes rows from the 'addresses' table. The SELECT statement now uses 'AS' to alias column names, and some new addresses have been added for various protocols such as Optimism, Arbitrum, Boba, Metis and Aevo. Some existing addresses have also had their role_type or version changed.
MODEL: addresses_optimism_fee_vaults.sql
🟢 Added by:
🔧 PR: #3463, Add Labels for Bedrock Addresses & Configure L2 Labels
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model creates a table with three columns:
address,vault_nameand the lower case version of the address. The table contains predeployed contract addresses for Optimism's SequencerFeeVault, BaseFeeVault and L1FeeVault. This enables data analysts to easily reference these addresses in their queries without having to manually input them each time they are needed.MODEL: addresses_ethereum_cex.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: [changes too large] The model addresses_ethereum_cex.sql was removed.
SECTOR: lido
toggle to see all model updates
MODEL: lido_liquidity.sql
🟠 Modified by:
🔧 PR: #3451, lido liquidity uniswap/camelot pools
🧙 Author: @ppclunghe on 2023-06-08
📝 Summary: This diff shows changes made to a dbt SQL model that defines a list of lido liquidity models. One item was removed from the list, and four new items were added. The removed item is related to KyberSwap pools on Optimism, while the added items include Uniswap v3 pools on Ethereum, Arbitrum and Optimism networks as well as Camelot Pools on Arbitrum network.
MODEL: lido_liquidity_arbitrum_camelot_pools.sql
🟢 Added by:
🔧 PR: #3451, lido liquidity uniswap/camelot pools
🧙 Author: @ppclunghe on 2023-06-08
📝 Summary: [changes too large] The model lido_liquidity_arbitrum_camelot_pools.sql was added.
MODEL: lido_liquidity_arbitrum_uniswap_v3_pools.sql
🟢 Added by:
🔧 PR: #3451, lido liquidity uniswap/camelot pools
🧙 Author: @ppclunghe on 2023-06-08
📝 Summary: [changes too large] The model lido_liquidity_arbitrum_uniswap_v3_pools.sql was added.
MODEL: lido_liquidity_ethereum_uniswap_v3_pools.sql
🟢 Added by:
🔧 PR: #3451, lido liquidity uniswap/camelot pools
🧙 Author: @ppclunghe on 2023-06-08
📝 Summary: [changes too large] The model lido_liquidity_ethereum_uniswap_v3_pools.sql was added.
MODEL: lido_liquidity_optimism_uniswap_v3_pools.sql
🟢 Added by:
🔧 PR: #3451, lido liquidity uniswap/camelot pools
🧙 Author: @ppclunghe on 2023-06-08
📝 Summary: [changes too large] The model lido_liquidity_optimism_uniswap_v3_pools.sql was added.
MODEL: lido_liquidity_optimism_kyberswap_pools.sql
🟠 Modified by:
🔧 PR: #3443, fix for lido_liquidity_optimism_kyberswap_pools
🧙 Author: @ppclunghe on 2023-06-06
📝 Summary: The SQL model has been updated to include additional tokens in the
tokens_mappingCTE. The new tokens are added using a union all statement. A left join is also added to join theprices_tokenstable with the existing query, and a coalesce function is used for paired_token_symbol column in order to handle null values. Finally, CONCAT function is used on multiple columns including blockchain, project, paired_token_symbol and main_token_symbol columns as part of pool_name selection in all_metrics CTE.SECTOR: time_utils
toggle to see all model updates
MODEL: time_utils_days.sql
🟢 Added by:
🔧 PR: #3455, time utils
🧙 Author: @dot2dotseurat on 2023-06-08
📝 Summary: This SQL model creates a table with a single column 'day' that contains all dates between January 1, 2000 and January 1, 2100. This enables data analysts to easily join this table with other tables on the date field and perform time-based analysis or aggregations.
MODEL: time_utils_minutes.sql
🟢 Added by:
🔧 PR: #3455, time utils
🧙 Author: @dot2dotseurat on 2023-06-08
📝 Summary: This SQL model creates a table with a single column 'minute' that contains all the minutes between January 1st, 2000 and January 1st, 2100. This enables data analysts to easily join this table with other tables containing time-based data and perform analyses at the minute level.
SECTOR: contracts
toggle to see all model updates
MODEL: contracts_optimism_contract_creator_address_list.sql
🟠 Modified by:
🔧 PR: #3377, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: The diff of the SQL model shows changes made to a list of Ethereum addresses and their corresponding project names. Some projects were renamed, while others were added or removed from the list. The main logic involves updating this curated list with accurate information about each project's name based on its contract address.
MODEL: contracts_optimism_contract_overrides.sql
🟠 Modified by:
🔧 PR: #3377, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model is a list of Ethereum smart contracts and their labels. Three new Seaport contracts were added to the existing list, each with a different version number. No other changes were made to the model except for adding these three new lines.
MODEL: contracts_optimism_project_name_mappings.sql
🟠 Modified by:
🔧 PR: #3377, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: The diff shows additions and modifications to a mapping table that maps Dune Analytics project names to their corresponding human-readable names. Several new projects were added, including Frax Finance, DeFi Saver, Decent.xyz and Pika Protocol. Additionally, some existing mappings were modified for consistency purposes (e.g., 'overnight' was changed to 'Overnight+').
SECTOR: op
toggle to see all model updates
MODEL: op_token_distributions_optimism_project_wallets.sql
🟠 Modified by:
🔧 PR: #3448, [easy] OP Updates + ERC20 Mapping Fix
🧙 Author: @MSilb7 on 2023-06-08
📝 Summary: This SQL model is a list of Ethereum addresses and their corresponding names and roles. The diff shows that several new addresses have been added to the list, all belonging to Pika Protocol with the role of 'Distributor'. No other changes were made in this pull request.
🔧 PR: #3448, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The diff shows that the SQL model has not been changed except for a minor modification in two lines. The reference to an existing table named 'addresses_optimism_cex' was replaced with another table called 'cex_optimism_addresses'. This change ensures that the query does not accidentally include any CEX addresses while selecting unique addresses from a list of proposals.
🔧 PR: #3448, Update op_token_distributions_optimism_project_wallets.sql
🧙 Author: @raho11 on 2023-06-06
📝 Summary: A new address was added to the SQL model for Kwenta's MultipleMerkleDistributor. No other changes were made to the existing addresses and their corresponding platforms.
MODEL: op_token_distributions_optimism_all_distributions_labels.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The SQL model is a
WITHstatement that creates a temporary table calledall_labels. The table has three columns:proposal_name,address_descriptor, andproject_name. The data for these columns comes from the referenced model, which was changed from'addresses_optimism_cex'to'cex_optimism_addresses'. Additionally, any addresses found in the referenced model are excluded if they also appear in another reference called'op_token_distributions_optimism_project_wallets'.MODEL: op_token_distributions_optimism_other_tags.sql
🟠 Modified by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The SQL model adds a new table to the existing
tagged_walletstable by performing a union with another table calledcex_optimism_addresses. The rows from this new table are tagged as 'Other'. The WHERE clause filters out any addresses that already exist in theop_token_distributions_optimism_project_walletsreference.MODEL: op_token_distributions_optimism_transfer_mapping.sql
🟠 Modified by:
🔧 PR: #3419, OP Rewards - Make name label checks 'Like'
🧙 Author: @MSilb7 on 2023-06-06
📝 Summary: The SQL model has been updated to handle different scenarios of token transfers. The changes include handling tokens going to 'Other' addresses as end users, assuming deployed when tokens go to a 'Deployed' address or an unknown address, marking grants from the foundation wallets as 'op_to_project', and handling distributions between projects. Additionally, it handles clawbacks for both project deployers and airdrops by checking the type of transaction. Finally, it tracks tokens going into intermediate utility contracts and coming back from unknown wallets into the project or foundation wallet.
MODEL: op_optimism_airdrop_1_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks the distribution of an Optimism token airdrop. It includes information such as the recipient's address, amount received in raw and original format, USD value at time of receipt, and other identifying details like blockchain name and project name. The model also incorporates pricing data to calculate USD values for each transaction. This enables data analysts to track the distribution of this specific token on Optimism blockchain over time.
SECTOR: balancer
toggle to see all model updates
MODEL: balancer_v2_arbitrum_bpt_prices.sql
🟠 Modified by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This SQL model calculates the median price of tokens in Balancer pools on Arbitrum. It does this by first selecting all trades from the
Vault_evt_Swaptable that involve a pool token (bpt_trades). Then, it joins these trades with other tables to get information about each trade and calculate normalized rates between input and output tokens. Next, it backfills missing pricing data for some trades using averages of prices from similar transactions. Finally, it calculates the median price for each token in each hour based on available pricing data or approximations if no data is available within 10 hours before or after an hour block.MODEL: balancer_bpt_prices.sql
🟢 Added by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This new dbt SQL model creates a union of four Balancer pool token (BPT) price tables from different blockchains - Ethereum, Arbitrum, Polygon and Gnosis. The resulting table includes columns for blockchain name, hour timestamp, contract address and median BPT price. This enables data analysts to easily query and analyze BPT prices across multiple blockchains in one consolidated table.
MODEL: balancer_v2_ethereum_bpt_prices.sql
🟠 Modified by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This SQL model calculates the median price of Balancer Pool Tokens (BPTs) in USD for each hour. It does this by joining data from various sources, including a Balancer Swap event table and token pricing tables. The added code includes several CTEs that perform calculations on the data to derive normalized rates and prices for tokens involved in swaps, as well as backfilling missing pricing information using averages or calculated values. Finally, it uses an
approx_percentilefunction to calculate the median BPT price over a sliding window of 21 hours around each hour interval.MODEL: balancer_v2_gnosis_bpt_prices.sql
🟢 Added by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This SQL model creates a view that calculates the median price of tokens traded in Balancer V2 pools on Gnosis blockchain. It uses data from various sources to calculate token prices, including trades and token metadata. The resulting view enables data analysts to analyze historical trends in Balancer V2 pool trading volumes and liquidity by providing them with accurate pricing information for each trade pair at hourly intervals.
MODEL: balancer_v2_optimism_bpt_prices.sql
🟠 Modified by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This SQL model calculates the median price of Balancer Pool Tokens (BPTs) on Optimism blockchain. It does so by joining data from various sources and calculating token prices based on trades, backfilling missing pricing information, and formulating a final price using approximated percentiles. The added code includes several CTEs that perform these calculations in stages before finally outputting the median BPT prices per hour for each contract address. The removed code was replaced with more efficient queries that achieve similar results but with additional features such as incremental updates to reduce query times.
MODEL: balancer_v2_polygon_bpt_prices.sql
🟠 Modified by:
🔧 PR: #3416, Balancer Pool Token Prices
🧙 Author: @thetroyharris on 2023-06-08
📝 Summary: This SQL model calculates the median price of Balancer Pool Tokens (BPTs) on Polygon blockchain. It does so by joining data from various sources, including token prices and trades, to calculate the BPT's estimated price at each trade. The model then uses this information to backfill missing pricing data for previous trades and finally calculates a median hourly price for each contract address using approx_percentile function with 10 preceding and following rows as window frame.
SECTOR: _sector
toggle to see all model updates
MODEL: decentraland_polygon_events.sql
🟢 Added by:
🔧 PR: #3447, add decentraland polygon to nft trades (old) - Ready for review
🧙 Author: @henrystats on 2023-06-07
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze successful trades of NFTs on the Decentraland marketplace on Polygon. The view includes information such as the blockchain, project, version, block date and time, trade amount in USD and original currency symbol (MANA), token ID and standard (ERC721), contract addresses for various parties involved in the trade, platform fees charged by Decentraland Marketplace V2 for facilitating trades etc.
🟠 Modified by:
🔧 PR: #3447, Fix decentraland_polygon_events amount_raw
🧙 Author: @belen-pruvost on 2023-06-08
📝 Summary: The diff shows that the model has been updated to cast a column as DECIMAL(38,0) and remove another column. The SELECT statement now includes block_number, amount_usd (which is calculated using price_converted and p.price), amount_original (which is equal to price_converted), amount_raw (which was previously included but now casted as DECIMAL(38,0)), currency_symbol ('MANA'), currency_contract ('0xa1c57f48f0deb89f569dfbe6e2b7f46d33606fd4') and token_id.
MODEL: nft_events_old.sql
🟠 Modified by:
🔧 PR: #3348, add decentraland polygon to nft trades (old) - Ready for review
🧙 Author: @henrystats on 2023-06-07
📝 Summary: A new reference to 'decentraland_polygon_events' was added to the SQL model. The SELECT statement remains unchanged.
🔧 PR: #3348, add element nft trades polygon
🧙 Author: @henrystats on 2023-06-05
📝 Summary: In this diff of a dbt SQL model, one event table for the Polygon network was added while no tables were removed. The other existing event tables are still being referenced in the model.
MODEL: element_polygon_events.sql
🟢 Added by:
🔧 PR: #3348, add element nft trades polygon
🧙 Author: @henrystats on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze trade transactions for Element, an NFT project on the Polygon blockchain. The view includes information such as the blockchain, project name and version, block time, token ID and standard (ERC721 or ERC1155), trade type (single item or bundle), number of items traded, seller/buyer addresses and amounts paid in both raw tokens and USD. It also includes information about any aggregators involved in the transaction as well as platform/royalty fees if applicable.
SECTOR: cex
toggle to see all model updates
MODEL: cex_arbitrum_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that lists various cryptocurrency exchanges and their associated wallet addresses on the Arbitrum blockchain. The table includes columns for the exchange name, distinct name, address, date added to the list and who added it. This enables data analysts to track transactions on these exchanges using this information as a reference point.
MODEL: cex_avalanche_c_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that lists cryptocurrency exchange addresses and their associated names on the Avalanche blockchain. The table includes columns for the blockchain name, address (in lowercase), exchange name, distinct name, who added it to the list and when it was added. This enables data analysts to easily query this information for various purposes such as tracking trading volumes or identifying potential market manipulations by exchanges.
MODEL: cex_bitcoin_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: [changes too large] The model cex_bitcoin_addresses.sql was added.
MODEL: cex_bnb_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: [changes too large] The model cex_bnb_addresses.sql was added.
MODEL: cex_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a view that combines data from multiple CEX (centralized exchange) blockchain addresses tables into one table. The resulting view includes columns for the blockchain name, address, CEX name, distinct name, added by and added date. This enables data analysts to easily query and analyze centralized exchange activity across multiple blockchains in a single table.
MODEL: cex_ethereum_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: [changes too large] The model cex_ethereum_addresses.sql was added.
MODEL: cex_fantom_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that lists various cryptocurrency exchanges and their associated wallet addresses on the Fantom blockchain. The table includes columns for the exchange name, distinct name, blockchain type, address (in lowercase), who added it to the list and when it was added. This enables data analysts to track transactions on these exchanges using their respective wallet addresses as identifiers.
MODEL: cex_optimism_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that lists various cryptocurrency exchanges and their associated wallet addresses on the Optimism blockchain. The table includes columns for the blockchain name, address, exchange name, distinct exchange identifier, who added it to the list and when it was added. This enables data analysts to track transactions across different exchanges on this particular blockchain.
MODEL: cex_polygon_addresses.sql
🟢 Added by:
🔧 PR: #3137, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: This SQL model creates a table that lists cryptocurrency exchange addresses and their associated names on the Polygon blockchain. The table includes columns for the blockchain name, address (in lowercase), exchange name, distinct name, who added it to the list and when it was added. This enables data analysts to easily query this information for analysis or use in other models.
SECTOR: staking
toggle to see all model updates
MODEL: staking_ethereum_entities.sql
🟠 Modified by:
🔧 PR: #3461, Restructure
cex.addressesand add a few hundred addresses across Bitcoin, Ethereum, Arbitrum, Optimism, Fantom, BNB & Polygon🧙 Author: @hildobby on 2023-06-07
📝 Summary: The SQL model is selecting data from the Ethereum blockchain traces table and joining it with itself on the 'from' field. The original code was filtering for a specific address using a reference to an addresses table, but this was changed to use a reference to another CEX Ethereum addresses table instead. Additionally, there is an optional filter on block time that only applies if the model is not being run incrementally.
🔧 PR: #3461, Add ETH staking entities
🧙 Author: @hildobby on 2023-06-06
📝 Summary: This SQL model selects and formats data from a table with columns for Ethereum addresses, entities associated with those addresses, unique entity names, and categories. The 'trim' function is used to remove any leading or trailing white space in the entity and unique name columns. The 'lower' function is used to convert all characters in the address column to lowercase letters. Rows are added for several new Ethereum addresses associated with various staking pools or independent stakers involved in liquid staking or traditional proof-of-stake validation on the Ethereum network.
SECTOR: layerzero
toggle to see all model updates
MODEL: layerzero_arbitrum_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between two chains. The unique key has been updated to exclude one column. A new column, call_send_index, has been added to send_detail table using ROW_NUMBER() function and a join condition with destination_gas_summary table was modified accordingly. Two tables have been removed: destination_trace_address_summary and native_transfer_value_summary while trans_detail table now includes both erc20 transfers and native transfers in its UNION ALL statement.The SELECT statement at the end returns information about blockchain transactions including source/destination chain names, amount_original (in decimals), amount_raw (in integer) etc.
MODEL: layerzero_avalanche_c_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between two chains. The unique key has been updated to exclude one column. A new column, call_send_index, has been added to send_detail table using ROW_NUMBER() function and a join condition with destination_gas_summary table was modified accordingly. Two tables have been removed: destination_trace_address_summary and native_transfer_value_summary while trans_detail table now includes only erc20 transfers or native transfers where transaction amount > endpoint gas amount. Finally, the SELECT statement at the end returns information about blockchain transactions including source/destination chain names and original/raw amounts of tokens transferred in each transaction (if any).
MODEL: layerzero_bnb_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between two chains. The unique key has been updated to exclude one column. A new column, call_send_index, has been added to send_detail table using ROW_NUMBER() function and a UNION ALL clause was used in trans_detail table for native transfers where transaction amount > endpoint gas amount. Finally, the SELECT statement returns information about blockchain name and original/ raw transfer amounts from send_detail and trans_details tables joined on block_number, tx_hash columns with left join condition on call_send_index = 1 in order to get only first row of each group defined by partitioning over s.call_block_number,s.call_tx_hash columns respectively.
MODEL: layerzero_ethereum_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between Ethereum chains. The unique key has been updated to exclude one column. A new call_send_index column has been added to send_detail, and native_transfer_value_summary and destination_trace_address_summary have been removed. trans_detail now includes only two transfer types: erc20 and native, with a UNION ALL statement joining them together.The SELECT statement at the end returns information about blockchain transactions including amount_original and amount_raw columns joined from other tables using LEFT JOIN statements on various conditions such as chain_id or contract_address.
MODEL: layerzero_fantom_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between two chains. The unique key has been updated to exclude one column. A new column, call_send_index, has been added to send_detail table using ROW_NUMBER() function and a join condition with destination_gas_summary table was modified accordingly. Two tables have been removed: destination_trace_address_summary and native_transfer_value_summary while trans_detail table now includes both erc20 transfers and native transfers in a UNION ALL statement.The amount of erc721 tokens are ignored in the final SELECT statement which returns data from multiple joined tables for analysis purposes on Fantom blockchain transactions
MODEL: layerzero_gnosis_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between chains. The unique key has been updated to exclude one column. A new call_send_index column has been added to send_detail, and native_transfer_value_summary and destination_trace_address_summary have been removed. trans_detail now includes only two transfer types: erc20 and native transfers, with a UNION ALL statement joining them together.The amount of ERC721 tokens was ignored in this summary query.The final SELECT statement returns information about the blockchain used for each transaction along with its original amount value in decimals or raw format depending on whether it's an ERC20 or Native transfer type respectively
MODEL: layerzero_optimism_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the gas usage and transfer details of cross-chain transactions. The unique key has been updated to exclude a currency contract column. A row number function has been added to the send_detail CTE, which also includes source_chain_id, tx_hash, block_number and destination_chain_id columns. The trans_detail CTE now includes only erc20 transfers or native transfers where transaction amount > endpoint gas amount.The blockchain name 'optimism' is selected along with other relevant columns from various tables in the final SELECT statement.
MODEL: layerzero_polygon_send.sql
🟠 Modified by:
🔧 PR: #3437, Add missing data in layzerzero
🧙 Author: @BennyFeng on 2023-06-07
📝 Summary: The SQL model is an incremental merge strategy that summarizes the details of transactions between two chains. The unique key has been updated to exclude one column. A new column, call_send_index, has been added to send_detail table using ROW_NUMBER() function and a join condition with destination_gas_summary table was modified accordingly. Two tables have been removed: destination_trace_address_summary and native_transfer_value_summary while trans_detail table now includes both erc20 transfers and native transfers in a UNION ALL statement.The SELECT query at the end returns information about blockchain transactions including amount_original and amount_raw columns for each transaction.
SECTOR: dodo
toggle to see all model updates
MODEL: dodo_aggregator_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The SQL model has been updated to include a new SELECT statement that retrieves data from another table called DODOFeeRouteProxy_evt_OrderHistory. The UNION ALL operator is used to combine the results of both SELECT statements. Additionally, an optional filter has been added for incremental updates based on the evt_block_time column in both tables. Finally, a new column named trace_address with an empty array as its default value was added and replaces the previous empty string value for all rows returned by both SELECT statements.
MODEL: dodo_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In this diff of a dbt SQL model, the only change made was to remove the reference to 'dodo_aggregator_arbitrum_trades' and add a reference to 'dodo_pools_arbitrum_trades'. The set variable 'dodo_models' now only includes the latter.
MODEL: dodo_pools_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff of the dbt SQL model shows that a filter condition was removed from each of the four subqueries in a CTE named
dodo_view_markets. The filter conditions were checking if certain traders were not equal to specific addresses. Additionally, an optional time-based filtering condition was added to each subquery. The main logic remains unchanged and involves joining data from different sources on market contract addresses and selecting relevant columns for analysis.MODEL: dodo_aggregator_bnb_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff shows changes made to three SQL models that query different tables in the Dodoex_bnb database. In each model, a new column called 'trace_address' was added and its value set to an empty string in the original code but changed to an array of big integers using CAST function in the updated code. The other columns selected from their respective tables are token_sold_address, project_contract_address, tx_hash and evt_index.
MODEL: dodo_bnb_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In this diff of a dbt SQL model, the reference to 'dodo_aggregator_bnb_trades' was removed and the reference to 'dodo_pools_bnb_trades' was added.
MODEL: dodo_pools_bnb_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff of the dbt SQL model shows that a filter condition was removed from all the queries in this model. The filter condition excluded certain traders (identified by their wallet addresses) from being included in the results. Additionally, an incremental load feature was added to some of these queries which only includes data for events that occurred within one week prior to running this query.
MODEL: dodo_aggregator_trades.sql
🟢 Added by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: This SQL model creates a view that aggregates trade data from multiple DEXs on different blockchains (Ethereum, Binance Smart Chain, Polygon, Arbitrum and Optimism) into a single table. The view includes information such as token symbols and amounts bought/sold in each trade, USD value of the trade amount at the time of transaction and addresses involved in each transaction. This enables data analysts to easily query across multiple DEXs for insights into trading activity on various blockchains.
MODEL: dodo_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The removed code was a SQL query that selected all columns from a subquery. The added code included a reference to two other dbt models and used a for loop to iterate over the dodo_models list, but it is unclear what logic was implemented within this iteration.
MODEL: dodo_aggregator_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff shows changes made to a SQL model in a merged pull request. The changes involve replacing an empty string with an array of big integers for the trace_address column in several queries that source data from different tables within the dodo_ethereum database. No other significant logic was added or removed.
MODEL: dodo_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In this diff of a dbt SQL model, the reference to 'dodo_aggregator_ethereum_trades' was removed and the reference to 'dodo_pools_ethereum_trades' was added.
MODEL: dodo_pools_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff of the SQL model shows that a filter condition was removed from all the subqueries in a CTE named
dodo_view_markets. The filter condition excluded certain traders based on their addresses. Additionally, an if statement was modified to remove an unnecessary check for incremental updates.MODEL: dodo_aggregator_optimism_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The SQL model has been updated to include a new SELECT statement that retrieves data from another table called DODOFeeRouteProxy_evt_OrderHistory. The UNION ALL operator is used to combine the results of both SELECT statements. Additionally, there are conditional statements that filter the results based on whether it's an incremental update or not. Finally, a new column called trace_address has been modified from an empty string to an array of big integers using CAST().
MODEL: dodo_optimism_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In this diff of a dbt SQL model, the reference to 'dodo_aggregator_optimism_trades' was removed and the reference to 'dodo_pools_optimism_trades' was added.
MODEL: dodo_pools_optimism_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff of the SQL model shows that a set of DODO V1 and V2 adapters were removed. The WHERE clause for each adapter was also removed, which filtered out trades made by specific traders. Instead, an is_incremental() function was added to filter events based on their block time being within the last week.
MODEL: dodo_aggregator_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff shows changes made to a SQL model. The original code selects data from the DODOV2Proxy02_evt_OrderHistory table and renames some columns, while also casting an empty string as an array of big integers. The new code adds another select statement that retrieves data from the DODOFeeRouteProxy_evt_OrderHistory table, with similar column renaming and typecasting operations. Both select statements are combined using UNION ALL operator to create a single result set that is filtered by block time if it's incremental mode before being returned with additional metadata about blockchain information.
MODEL: dodo_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: In this diff of a dbt SQL model, the reference to 'dodo_aggregator_polygon_trades' was removed and the reference to 'dodo_pools_polygon_trades' was added.
MODEL: dodo_pools_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3436, Restruct dodo aggregator and pools
🧙 Author: @owen05 on 2023-06-07
📝 Summary: The diff of the dbt SQL model shows that a set of DODO V1 & V2 adapters were removed. The WHERE clauses for filtering out specific traders from each event type were also removed, and instead, all events are now being selected. Additionally, an is_incremental() function was added to filter events based on their block time within the last week. Finally, a SELECT statement at the end selects data from all previous CTEs (common table expressions) created in this model.
SECTOR: wigoswap
toggle to see all model updates
MODEL: wigoswap_fantom_pools.sql
🟢 Added by:
🔧 PR: #3472, add wigoswap fantom pools to dex _pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: This dbt SQL model creates a table that tracks the creation of new liquidity pools on the WigoSwap decentralized exchange on Fantom blockchain. It includes information such as pool name, fee percentage, tokens involved in each pool, and creation block time and number. The model also allows for incremental updates by filtering only events from the past week. This enables data analysts to better understand trading activity and liquidity provision trends on WigoSwap's platform over time.
SECTOR: spartacus_exchange
toggle to see all model updates
MODEL: spartacus_exchange_fantom_pools.sql
🟢 Added by:
🔧 PR: #3473, add spartacus exchange pools to dex pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: This dbt SQL model creates a table that extracts data from the
BaseV1Factory_evt_PairCreatedsource in thespartacus_exchange_fantomdatabase. It includes information about blockchain, project, version, pool pairings and fees. Additionally it provides details on token0 and token1 as well as creation block time and number for each contract address. The model also has an optional incremental feature to filter by event block time within the last week. This enables data analysts to easily access important transactional information related to pool pairs on Fantom's Spartacus Exchange platform for analysis purposes.SECTOR: spiritswap
toggle to see all model updates
MODEL: spiritswap_fantom_pools.sql
🟢 Added by:
🔧 PR: #3446, add spiritswap_fantom_pools to dex pools - ready for review
🧙 Author: @henrystats on 2023-06-06
📝 Summary: This dbt SQL model creates a table that tracks the creation of new liquidity pools on the Spiritswap decentralized exchange on Fantom blockchain. The table includes information such as pool name, fee percentage, tokens involved in each pool, and creation block time and number. This enables data analysts to analyze trends in new pool creations over time and gain insights into user behavior on the platform. An optional incremental load feature allows for efficient updates to the table with only recent data being added.
🟠 Modified by:
🔧 PR: #3446, add spartacus exchange pools to dex pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: This diff shows a change in a SQL model that selects data from the spiritswap_fantom database. The added and removed lines are related to selecting specific columns from the table, including blockchain, project, version, pool name and other details such as token0/1 and creation block time/number. Additionally, an incremental clause was added to filter results based on recent events within one week of current date/time.
SECTOR: equalizer_exchange
toggle to see all model updates
MODEL: equalizer_exchange_fantom_pools.sql
🟢 Added by:
🔧 PR: #3474, add equalizer exchange pools to dex pools
🧙 Author: @henrystats on 2023-06-06
📝 Summary: This dbt SQL model creates a table that tracks the creation of new liquidity pools on the Equalizer Exchange platform for Fantom blockchain. It includes information such as pool name, tokens involved, fee structure and creation block details. The model enables data analysts to easily query and analyze this data for insights into user behavior and platform performance. Additionally, it includes an optional incremental load feature to limit processing time by only pulling in recent data updates.
SECTOR: frax_finance
toggle to see all model updates
MODEL: frax_finance_bnb_bribes.sql
🟢 Added by:
🔧 PR: #3258, Frax finance
🧙 Author: @Vahid-flipside on 2023-06-06
📝 Summary: [changes too large] The model frax_finance_bnb_bribes.sql was added.
SECTOR: timeswap
toggle to see all model updates
MODEL: timeswap_arbitrum_pools.sql
🟠 Modified by:
🔧 PR: #3475, Add new pool in timeswap
🧙 Author: @RaveenaBhasin on 2023-06-06
📝 Summary: A new token pair 'unshETH-USDC' was added to the SQL model for the 'Arbitrum' network. The tokens involved in this pair are 'unshETH' and USDC'. Other details such as their contract addresses, decimals, reserve amounts, last updated timestamp etc were also included.
MODEL: timeswap_arbitrum_borrow.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: The diff of the SQL model shows changes made to a query that retrieves data on borrowing transactions from an arbitrage platform. The changes include adding a join with another table and filtering by date range for incremental updates.
MODEL: timeswap_arbitrum_lend.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: The diff of the SQL model shows that a new join has been added to the existing code. The join is with another table called 'transactions' and it is used to get information about users who performed certain transactions. Additionally, some conditional statements have been added for incremental updates in case there are any changes made within a week's time frame.
MODEL: timeswap_ethereum_borrow.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: The diff of the SQL model shows that a new column 'user' was added to the SELECT statement. Two JOINS were also modified to include this new column, and an IF statement was added for incremental updates. The rest of the code remains unchanged from before.
MODEL: timeswap_ethereum_lend.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: A new column 'user' was added to the SELECT statement by joining with a transaction table. An incremental condition was also added to filter transactions within the last week.
MODEL: timeswap_polygon_borrow.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: The diff of the SQL model shows changes made to a TimeswapV2PeripheryUniswapV3BorrowGivenPrincipal and TimeswapV2PeripheryNoDexBorrowGivenPrincipal table. The added code includes selecting transaction hash, time, strike price, pool pair and chain from these tables. Additionally, it selects user address by joining with polygon transactions table and calculates token amount in USD using prices.usd table. Finally, it unions all the selected data into one output for analysis purposes while filtering out any records older than 1 week if incremental update is enabled.
MODEL: timeswap_polygon_lend.sql
🟠 Modified by:
🔧 PR: #3459, Update lend & borrow model in timeswap spell with user data
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: The diff of the SQL model shows changes made to a TimeswapV2PeripheryUniswapV3LendGivenPrincipal table. The added code includes selecting transaction hash, time, strike price, pool pair and chain from the table. Additionally, it selects user information and calculates token amount in USD for each transaction using prices from another source. There are also some JOIN statements with other tables such as timeswap_polygon_pools and polygon_transactions that were added or modified to get more data on transactions within a week's timeframe.
MODEL: timeswap_polygon_pools.sql
🟠 Modified by:
🔧 PR: #3458, Add new pool to timeswap
🧙 Author: @RaveenaBhasin on 2023-06-02
📝 Summary: A new row was added to a table called 'temp_table'. The row contains information about the USDC-stMATIC pair on the Polygon network, including contract addresses and decimals.
SECTOR: element
toggle to see all model updates
MODEL: element_avalanche_c_assert_trades.sql
🟠 Modified by:
🔧 PR: #3348, add element nft trades polygon
🧙 Author: @henrystats on 2023-06-05
📝 Summary: [changes too large] The model element_avalanche_c_assert_trades.sql was renamed.
MODEL: element_bnb_assert_trades.sql
🟠 Modified by:
🔧 PR: #3348, add element nft trades polygon
🧙 Author: @henrystats on 2023-06-05
📝 Summary: [changes too large] The model element_bnb_assert_trades.sql was renamed.
SECTOR: spookyswap
toggle to see all model updates
MODEL: spookyswap_fantom_pools.sql
🟢 Added by:
🔧 PR: #3445, add spookyswap pools to dex pools - ready for review
🧙 Author: @henrystats on 2023-06-05
📝 Summary: This dbt SQL model creates a table that tracks the creation of new liquidity pools on the Spookswap decentralized exchange on the Fantom blockchain. It includes information such as pool name, fee percentage, tokens involved in each pool, and creation block time and number. The model enables data analysts to easily query this information for analysis or reporting purposes. Additionally, if run incrementally it will only pull data from within the last week to keep processing times efficient.
SECTOR: airdrop
toggle to see all model updates
MODEL: airdrop_claims.sql
🟠 Modified by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: The changes made to the SQL model involve adding a closing parenthesis and removing an opening parenthesis. The rest of the code is not provided, so it's impossible to determine what specific logic was affected by these changes.
MODEL: airdrop_ethereum_claims.sql
🟠 Modified by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model adds a list of 36 new references to the
airdrop_claims_modelsvariable. These references are for various Ethereum airdrop claims models. TheSELECT *statement at the end is unchanged and will select all columns from whatever table it is applied to.MODEL: airdrop_optimism_claims.sql
🟠 Modified by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: In this diff of a dbt SQL model, the reference to 'velodrome_optimism_airdrop_claims' was removed and replaced with two references: 'op_optimism_airdrop_1_claims' and 'velodrome_optimism_airdrop_claims'.
SECTOR: alchemydao
toggle to see all model updates
MODEL: alchemydao_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that calculates the USD value of AlchemyDAO token (ALCH) airdropped to recipients between March 28 and April 19, 2021. The table includes blockchain, block time and number, project name, recipient address, transaction hash, amount in raw and original formats as well as its equivalent in USD. It also lists the token's contract address and symbol along with event index. The calculation is based on median price data from DEX prices table for Ethereum blockchain where ALCH was traded during this period.
SECTOR: apecoin
toggle to see all model updates
MODEL: apecoin_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks ApeCoin airdrops on the Ethereum blockchain. It includes information such as block time, block number, recipient address, transaction hash and amount of tokens received in both raw and original (divided by 10^18) formats. Additionally, it calculates the USD value of each airdrop based on historical price data from an external source. This model enables data analysts to analyze ApeCoin's token distribution strategy and track its impact over time using standardized metrics like USD value per recipient or total tokens distributed during specific periods.
SECTOR: bend_dao
toggle to see all model updates
MODEL: bend_dao_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track the BendDAO Airdrop on Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash and token amount in both raw and original values. Additionally, it calculates the USD value of each transaction based on historical price data from an external source.
SECTOR: blur
toggle to see all model updates
MODEL: blur_ethereum_airdrop_1_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks the recipients of the Blur Airdrop 1 on Ethereum blockchain. It includes information such as block time, block number, recipient address, transaction hash and amount in both raw and original (BLUR) values. Additionally, it calculates the USD value of each transaction based on historical price data from an external source. This model enables data analysts to analyze and report on the distribution of BLUR tokens during this specific airdrop event for further insights into user behavior or market trends related to BLUR token usage.
SECTOR: botto
toggle to see all model updates
MODEL: botto_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track Botto Airdrop transfers on the Ethereum blockchain. The table includes information such as recipient, transaction hash, token symbol and amount in both raw and original values. Additionally, it calculates the USD value of each transfer based on historical price data from an external source.
SECTOR: component
toggle to see all model updates
MODEL: component_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query Ethereum blockchain data related to Component Airdrop. The view includes information such as the recipient's account, transaction hash, token amount in raw and original format, token symbol (CMP), and the USD value of tokens at the time of transfer. It also joins with a price table for forward-filled prices on Ethereum blockchain.
SECTOR: cow_protocol
toggle to see all model updates
MODEL: cow_protocol_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query and retrieve information about CoW Protocol Airdrop transactions on the Ethereum blockchain. The view includes details such as the recipient, transaction hash, amount of tokens claimed in raw and original format, USD value at time of claim (based on price data), token address and symbol. It also joins with a forward-filled price table for additional context. This allows analysts to perform analysis or reporting related to CoW Protocol Airdrops using this consolidated dataset.
SECTOR: dappradar
toggle to see all model updates
MODEL: dappradar_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track DappRadar Airdrop transactions on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash, token amount in raw and original format (with decimals), USD value of the token amount at the time of transaction based on historical price data from an external source. This allows for analysis and reporting on DappRadar's airdrop campaign performance over time.
SECTOR: dydx
toggle to see all model updates
MODEL: dydx_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks DYDX token transfers on the Ethereum blockchain. It includes information such as block time, block number, recipient address, transaction hash, and amount of tokens transferred in both raw and original values. Additionally, it calculates the USD value of each transfer based on historical price data from an external source. This model enables data analysts to analyze DYDX token transfer activity over time and understand its impact on the market.
SECTOR: ens
toggle to see all model updates
MODEL: ens_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks Ethereum Name Service (ENS) airdrops. It includes information such as the recipient, amount of tokens received, and the USD value of those tokens at the time they were claimed. The model also joins with another table to get historical price data for ENS tokens in order to calculate USD values accurately. This enables data analysts to track ENS token distribution and analyze trends in its usage over time.
SECTOR: forefront
toggle to see all model updates
MODEL: forefront_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query and retrieve information about the Forefront Airdrop on Ethereum blockchain. The view includes details such as block time, block number, recipient account, transaction hash, token address and symbol. It also calculates the amount of tokens received by each recipient in both raw and original values as well as its equivalent value in USD at the time of transaction based on available price data.
SECTOR: forta_network
toggle to see all model updates
MODEL: forta_network_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query Ethereum blockchain transactions related to the Forta Network Airdrop. The view includes information such as block time, block number, recipient address, transaction hash and token amount in both raw and original values. Additionally, it calculates the USD value of each transaction based on historical price data from an external source.
SECTOR: galxe
toggle to see all model updates
MODEL: galxe_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track Galxe Airdrop transactions on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash, amount of tokens received (in raw and original values), USD value of tokens at the time of transaction (based on price data), token address and symbol. This allows for analysis and reporting on Galxe Airdrop activity during a specific timeframe.
SECTOR: gas_dao
toggle to see all model updates
MODEL: gas_dao_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks Gas DAO Airdrop transactions on the Ethereum blockchain. It includes information such as the recipient, transaction hash, amount of tokens received in both raw and original (decimal) form, and the USD value of those tokens at the time of receipt. The model also joins with a price table to calculate USD values for historical transactions. This enables data analysts to track Gas DAO Airdrop activity over time and analyze trends in token distribution among recipients on Ethereum.
SECTOR: gearbox
toggle to see all model updates
MODEL: gearbox_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that calculates the USD value of Gearbox Protocol tokens distributed in an airdrop. It uses data from two sources: Ethereum blockchain events and DEX prices. The view includes columns for blockchain, block time, project name, recipient address, transaction hash, token amount (in raw and original decimal format), USD value of the token amount at the time of distribution based on DEX prices (or min/max values if outside price range), token address and symbol. This enables data analysts to analyze the distribution patterns and market valuation impact of Gearbox Protocol's airdrops over time.
SECTOR: genie
toggle to see all model updates
MODEL: genie_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This dbt SQL model creates a table that tracks Genie Airdrop events on the Ethereum blockchain. It includes information such as block time, block number, recipient address, transaction hash and amount in USDC token. The model also joins with a reference table to calculate the USD value of each transaction based on current prices. This enables data analysts to analyze and report on Genie Airdrop activity over time using standardized metrics like USD value of transactions.
SECTOR: gitcoin
toggle to see all model updates
MODEL: gitcoin_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track Gitcoin Airdrop transactions on the Ethereum blockchain. The table includes information such as the recipient's account, transaction hash, amount of tokens received in both raw and original values, and USD value at the time of transaction. It also joins with a reference table for price information to calculate USD value accurately. This allows analysts to better understand how GTC tokens are being distributed during this specific timeframe (May 24th - June 24th).
SECTOR: hop_protocol
toggle to see all model updates
MODEL: hop_protocol_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks Hop Protocol Airdrop transactions on the Ethereum blockchain. It includes information such as block time, block number, recipient address, transaction hash and amount in both raw and original (HOP) values. Additionally, it calculates the USD value of each transaction based on historical price data from an external source. This model enables data analysts to analyze and report on Hop Protocol Airdrop activity for insights into user behavior or market trends related to HOP token usage.
SECTOR: looksrare
toggle to see all model updates
MODEL: looksrare_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query Ethereum blockchain transactions related to the LooksRare Airdrop project. The view includes information such as block time, block number, recipient address, transaction hash and token amount in both raw and original formats. Additionally, it calculates the USD value of each transaction based on historical price data from an external source.
SECTOR: notional
toggle to see all model updates
MODEL: notional_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query Notional Finance Airdrop transactions on the Ethereum blockchain. The view includes information such as block time, block number, recipient account, transaction hash, token address and symbol. It also calculates the amount of tokens in both raw and original formats as well as their USD value based on historical prices from an external source. This model can be used for analysis of Notional Finance's airdrop campaign performance or other related research purposes by querying this view with SQL queries.
SECTOR: oneinch
toggle to see all model updates
MODEL: oneinch_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks 1inch Protocol Airdrop transactions on the Ethereum blockchain. It includes information such as block time, block number, recipient account, transaction hash, amount in raw and original formats (with decimals), USD value of the amount at the time of transaction based on historical price data for 1INCH token. The model also joins with a forward-filled price table to calculate USD values and filters by date range if run incrementally. This enables data analysts to analyze and report on 1inch Protocol Airdrop activity in relation to historical prices for better insights into user behavior.
SECTOR: paladin
toggle to see all model updates
MODEL: paladin_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track Paladin Airdrop transactions on the Ethereum blockchain. The table includes information such as the recipient's account, transaction hash, amount of tokens received in both raw and original values, and USD value at the time of transaction. It also joins with a reference table for price information to calculate USD value accurately. This allows analysts to analyze trends in token distribution over time and understand how much each recipient received in terms of USD value.
SECTOR: paraswap
toggle to see all model updates
MODEL: paraswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that calculates the USD value of ERC20 token transfers on the Ethereum blockchain for Paraswap's airdrop program. The view uses data from two tables,
erc20_ethereumanddex_prices, to calculate the USD value of each transfer based on median prices at specific hours. This enables data analysts to easily analyze and report on Paraswap's airdrop program in terms of both token amounts and their corresponding values in USD.SECTOR: pooltogether
toggle to see all model updates
MODEL: pooltogether_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks PoolTogether airdrops on the Ethereum blockchain. It includes information such as the recipient's account, transaction hash, amount of tokens received (in raw and original values), and USD value at the time of receipt. The model also joins with another table to fill in missing price data for POOL tokens. This enables data analysts to track POOL token distribution over time and analyze its impact on user behavior or market trends.
SECTOR: ribbon
toggle to see all model updates
MODEL: ribbon_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks Ribbon (RBN) token airdrops on the Ethereum blockchain. It includes information such as the recipient's address, transaction hash, amount of RBN tokens received and their USD value at the time of receipt. The model also joins with another table to fill in missing price data for RBN tokens and uses an early_price CTE to calculate USD values for older transactions where price data is not available. This enables analysts to track Ribbon token distribution and understand its impact on users' portfolios over time.
SECTOR: safe
toggle to see all model updates
MODEL: safe_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that calculates the USD value of Safe token transfers on Ethereum blockchain. It uses data from two sources: ERC20 transfer events and DEX prices. The view includes columns for blockchain, block time, block number, project name, airdrop identifier, recipient address and transaction hash. Additionally it shows the amount transferred in both raw and original (divided by 10^18) units as well as its equivalent value in USD at the time of transfer based on median price or min/max prices within certain hour range depending on when the event occurred.
SECTOR: shapeshift
toggle to see all model updates
MODEL: shapeshift_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track ShapeShift Airdrop transactions on the Ethereum blockchain. The table includes information such as block time, block number, recipient account, transaction hash, amount in various formats (raw and converted to USD), token address and symbol. It also joins with a price reference table for conversion of amounts to USD. This allows analysts to perform analysis on the distribution of FOX tokens during this period and gain insights into user behavior related to ShapeShift's airdrop campaign.
SECTOR: snowswap
toggle to see all model updates
MODEL: snowswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track SnowSwap Airdrop transactions on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash and amount in both raw and original formats. Additionally, it calculates the USD value of each transaction based on historical price data for SNOW token at the time of transaction or earliest available price if before then.
SECTOR: sudoswap
toggle to see all model updates
MODEL: sudoswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to query Sudoswap Airdrop transactions on the Ethereum blockchain. The view includes information such as block time, block number, recipient address, transaction hash, amount of SUDO tokens transferred (in raw and original values), USD value of the transfer at the time of transaction (using historical price data), token address and symbol. It also joins with a forward-filled table containing USD prices for SUDO tokens to calculate accurate USD values for recent transactions if run incrementally.
SECTOR: thales
toggle to see all model updates
MODEL: thales_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that calculates the USD value of Thales token (THALES) transactions made during a specific time period. It uses data from an Ethereum blockchain and joins it with median price data from a decentralized exchange (DEX). The view includes information such as block time, block number, recipient address, transaction hash, amount in THALES tokens and its equivalent value in USD. This enables analysts to easily track the performance of THALES token on DEXs over time and analyze user behavior related to this cryptocurrency.
SECTOR: tokenfy
toggle to see all model updates
MODEL: tokenfy_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a view that enables data analysts to retrieve Tokenfy Airdrop transaction details, including recipient address, token amount in raw and original format, USD value at the time of transfer (using forward-filled price data), and other relevant information. The view is filtered by a specific date range and joined with two source tables:
erc20_ethereumfor ERC-20 token transfers on Ethereum blockchain andtokenfy_ethereumfor Tokenfy-specific call claims.SECTOR: tornado_cash
toggle to see all model updates
MODEL: tornado_cash_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track Tornado Cash airdrops on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash, amount of TORN tokens transferred in both raw and original values (with conversion to USD), token address and symbol. This allows for analysis of the distribution of TORN tokens through airdrops over time.
SECTOR: uniswap
toggle to see all model updates
MODEL: uniswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that tracks Uniswap airdrops on the Ethereum blockchain. It includes information such as the recipient's account, transaction hash, amount of UNI tokens received, and their USD value at the time of receipt. The model also joins with another table to fill in missing price data for UNI tokens and uses an early price calculation if no historical prices are available. This enables data analysts to track Uniswap token distribution over time and analyze trends in token ownership among recipients.
SECTOR: value_defi
toggle to see all model updates
MODEL: value_defi_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that calculates the USD value of vUSD tokens distributed in the Value DeFi Airdrop. The table includes blockchain, block time and number, project name, recipient address, transaction hash, amount of tokens distributed (both raw and original), and the corresponding USD value at the time of distribution. This enables data analysts to analyze trends in token distribution values over time for this specific airdrop campaign.
SECTOR: x2y2
toggle to see all model updates
MODEL: x2y2_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #3434,
airdrop.claimswith fix from #3418🧙 Author: @hildobby on 2023-06-05
📝 Summary: This SQL model creates a table that enables data analysts to track X2Y2 token transfers on the Ethereum blockchain between February 15th and March 31st, 2022. The table includes information such as the recipient of each transfer, the amount transferred in both raw and original values, and an estimated USD value based on historical pricing data.
SECTOR: rubicon
toggle to see all model updates
MODEL: rubicon_optimism_offers.sql
🟠 Modified by:
🔧 PR: #3449, Rubicon V2 updates
🧙 Author: @denverbaumgartner on 2023-06-05
📝 Summary: The SQL model adds a new table called
raw_tradesthat selects trade data from two events. It then joins this table with other tables to get relevant token and price data, and calculates the sold/bought amounts in USD. The main change is that it replaces the use ofLogTakeevent with bothLogTakeandemitTake. Additionally, there are some minor changes such as filtering out offers created before project start date for both offer selection queries (offers, which remains unchanged) instead of just one query previously.MODEL: rubicon_optimism_trades.sql
🟠 Modified by:
🔧 PR: #3449, Rubicon V2 updates
🧙 Author: @denverbaumgartner on 2023-06-05
📝 Summary: The SQL model has been updated to include a new table called
emitTakewhich is used to calculate the token bought and sold amounts from the perspective of the taker. Theblock_timefilter has also been updated to cast as timestamp instead of using string interpolation. Additionally, there are changes in join conditions for tables such as transactions and prices where they have added filters based on timestamps.SECTOR: nexusmutual
toggle to see all model updates
MODEL: nexusmutual_ethereum_product_information.sql
🟠 Modified by:
🔧 PR: #3439, Update product type names
🧙 Author: @guyhow on 2023-06-05
📝 Summary: [changes too large] The model nexusmutual_ethereum_product_information.sql was modified.
SECTOR: airswap
toggle to see all model updates
MODEL: airswap_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3404, Add Airswap v4 ERC20 swaps
🧙 Author: @ivigamberdiev on 2023-06-05
📝 Summary: This is a SQL model that selects data from the
SwapERC20_v4_evt_SwapERC20table in theairswap_ethereumsource. It retrieves information about token swaps, including block time, version, taker and maker addresses, token amounts and addresses for both sold and bought tokens. The model also includes project contract address, transaction hash and event index. If it's an incremental update (as indicated by{% if is_incremental() %}), only events from the last week are selected. Finally'ethereum'is returned as blockchain name for all rows in this query result set after union with another query result set (not shown here).Beta Was this translation helpful? Give feedback.
All reactions