📰 2023-05-26: Weekly Prophet! #3429
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 24 PRs merged from 17 wizards. Great job everyone! 🎉
We had 62 added models 🟢 and 68 modified models 🟠 for 48 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model creates a unified table that combines data from multiple flashloan models (Aave, Balancer, dYdX and Uniswap) into one. This enables data analysts to easily query and analyze flashloan activity across different protocols in a single location. The resulting table includes information such as blockchain, project name, version number, block time of the transaction, loan amount in various currencies including USD value at the time of transaction execution along with other relevant details like tx_hash etc.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #3381, add 148 new & missing tokens
🧙 Author: @bh2smith on 2023-05-24
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
🔧 PR: #3381, [Erc20] Add 514 missing tokens
🧙 Author: @bh2smith on 2023-05-22
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
MODEL: tokens_arbitrum_erc20.sql
🟠 Modified by:
🔧 PR: #3395, Adds ERC20 token to Arbitrum token model
🧙 Author: @ForrestChew on 2023-05-24
📝 Summary: The token symbol 'plsARB' was added to the model.
🔧 PR: #3395, Adds an ERC20 token to Arbitrum token table
🧙 Author: @rdiptan on 2023-05-23
📝 Summary: The token symbol 'VELA' was added to the model.
MODEL: tokens_gnosis_erc20.sql
🟠 Modified by:
🔧 PR: #3382, [Erc20-GnosisChain] Add 17 missing tokens
🧙 Author: @bh2smith on 2023-05-22
📝 Summary: The following token symbols were added: bCSPX, wagWXDAI, wagUSDC, hiveWATER (repeated), bb-ag-USDC, bb-ag-USD, wstETH (repeated), bb-ag-WXDAI, bIBTA , HoG , bIB01 , hiveWATER(repeated) CRC. The following token symbol was removed: CUSDCLP.
MODEL: tokens_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #3365, Adding MMTH, aBASED, agEUR and YFX
🧙 Author: @discochuck on 2023-05-22
📝 Summary: The added token symbols are MMTH, aBASED, agEUR and YFX. No tokens were removed.
SECTOR: prices
toggle to see all model updates
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #3399, [update] add wstEth, dQUICK token to prices.usd
🧙 Author: @RaveenaBhasin on 2023-05-24
📝 Summary: The token symbol 'wstETH' was added to the model.
MODEL: prices_polygon_tokens.sql
🟠 Modified by:
🔧 PR: #3399, [update] add wstEth, dQUICK token to prices.usd
🧙 Author: @RaveenaBhasin on 2023-05-24
📝 Summary: The token symbol that was added is 'dQUICK'. No tokens were removed.
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #3403, remove ANT from bnb feed
🧙 Author: @grkhr on 2023-05-24
📝 Summary: The token symbol 'ANT' was removed and the token symbols 'bXEN' and 'ANT' were added.
SECTOR: layerzero
toggle to see all model updates
MODEL: layerzero_arbitrum_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a table that summarizes data related to transactions between the Ethereum network and the Arbitrum Layer 2 network. It includes information such as source and destination chain IDs, transaction hash, block number, contract addresses involved in the transaction, transfer type (ERC20 or native), currency symbol and amount transferred. The model also calculates USD value of each transfer using current market prices for ERC20 tokens on Arbitrum L2. This enables data analysts to better understand cross-chain transfers between Ethereum mainnet and its layer 2 scaling solution - Arbitrum L2.
MODEL: layerzero_avalanche_c_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to transactions on the Avalanche blockchain. It enables data analysts to query and analyze transaction details such as source and destination chain IDs, contract addresses, block numbers, timestamps, transfer types (ERC20 or native), currency symbols and amounts in USD. The model also includes information about endpoint gas values for each transaction.
MODEL: layerzero_bnb_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to cross-chain transactions on the Binance Smart Chain. It enables data analysts to track transaction details such as source and destination chain IDs, block numbers, contract addresses, user addresses and transaction values. The view also includes information about transfer types (ERC20 or native), currency symbols and amounts in USD.
MODEL: layerzero_ethereum_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to transactions between Ethereum and other blockchains. It enables analysts to track the movement of ERC20 tokens and native currency, as well as calculate the value of these transfers in USD. The view includes information such as source/destination chain IDs, transaction hashes, contract addresses involved in the transfer, user address associated with each transaction and more.
MODEL: layerzero_fantom_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to cross-chain transactions on the Fantom blockchain. It enables data analysts to track and analyze various details of these transactions, including source and destination chain IDs, transaction values in both native tokens and ERC20 tokens, transfer types (native or ERC20), currency symbols, amounts in USD as well as original raw amounts. The view also includes information about endpoint contracts used for the transactions along with their adapter parameters.
MODEL: layerzero_gnosis_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to transactions made on the Gnosis blockchain. It enables data analysts to retrieve information such as source and destination chain IDs, transaction hashes, block numbers, contract addresses, transfer types (ERC20 or native), currency symbols and amounts in USD. The view also includes details about endpoint contracts used for sending transactions between chains and their associated gas fees.
MODEL: layerzero_chain_list.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a common table expression (CTE) called
chain_listthat contains information about various blockchain networks such as Ethereum, BNB Chain, Avalanche and others. The CTE includes the name of the network, its ID and endpoint address. This model enables data analysts to easily access this information for use in their queries without having to manually input it each time they need it.MODEL: layerzero_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that combines data from multiple blockchain networks, including Ethereum, Polygon and Avalanche. It enables data analysts to query transaction information such as source and destination chain IDs/names, transaction hash, block number/time and transfer amount in USD or original currency. The view is created by merging several existing models using the UNION ALL operator.
MODEL: layerzero_optimism_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a table that summarizes transactions between the LayerZero Optimism and Ethereum networks. It includes information such as source and destination chain IDs, transaction hash, block number, contract addresses involved in the transaction, transfer type (ERC20 or native), currency symbol and amount in USD. The model enables data analysts to analyze cross-chain transfers between these two networks by providing detailed information about each transfer including its value in USD.
MODEL: layerzero_polygon_send.sql
🟢 Added by:
🔧 PR: #3374, Layerzero endpoint call send
🧙 Author: @BennyFeng on 2023-05-25
📝 Summary: This SQL model creates a view that summarizes data related to transactions between the Polygon network and other chains. It includes information such as source and destination chain IDs, transaction hash, block number, contract addresses involved in the transaction, transfer type (ERC20 or native), currency symbol and amount transferred. The view also calculates the USD value of each transfer based on current market prices. This enables data analysts to easily query this information for analysis purposes without having to manually join multiple tables together.
SECTOR: airdrop
toggle to see all model updates
MODEL: airdrop_claims.sql
🟠 Modified by:
🔧 PR: #2979, Revert 'Create
airdrop.claimswith 38 airdrops (#2979)'🧙 Author: @jeff-dude on 2023-05-25
📝 Summary: The change made in the SQL model is a single line that replaces a closing parenthesis with an opening and closing parenthesis. This suggests that there was some code or query missing between the two parentheses, which has now been added. The rest of the code remains unchanged and it appears to be using a UNION ALL statement to combine data from multiple sources.
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Revert 'Create
airdrop.claimswith 38 airdrops (#2979)'🧙 Author: @jeff-dude on 2023-05-25
📝 Summary: The diff shows that a list of 36 references to other dbt SQL models has been removed from the
airdrop_claims_modelsvariable. The SELECT statement remains unchanged.🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Revert 'Create
airdrop.claimswith 38 airdrops (#2979)'🧙 Author: @jeff-dude on 2023-05-25
📝 Summary: In this diff of a dbt SQL model, the
op_optimism_airdrop_1_claimsreference was removed and replaced withvelodrome_optimism_airdrop_claims. The change was made in theairdrop_claims_modelsset.🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 source 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 amount of BEND tokens received by each recipient. Additionally, it calculates the USD value of each transaction based on historical price data for BEND token at the time of transaction or earliest available price if before then.
SECTOR: blur
toggle to see all model updates
MODEL: blur_ethereum_airdrop_1_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that enables data analysts to track Component Airdrop transactions on the Ethereum blockchain. The table includes information such as block time, block number, recipient account, transaction hash, token address and symbol. It also calculates the amount of CMP tokens received by each recipient in both raw and original values as well as their USD value at the time of transaction based on historical price data.
SECTOR: cow_protocol
toggle to see all model updates
MODEL: cow_protocol_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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.
MODEL: cow_protocol_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3375, [Bug] Fix Trade Surplus for Partial Fills
🧙 Author: @olgafetisova on 2023-05-22
📝 Summary: The diff shows that the calculation for 'surplus_usd' in the valued_trades SQL model has been updated. The previous calculation included a fill_proportion variable, which has now been removed. The new calculation only uses usd_value and some other variables to calculate surplus_usd as a ratio of limit_sell_amount and atoms_bought.
SECTOR: dappradar
toggle to see all model updates
MODEL: dappradar_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 both raw and original values (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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 transfers over time and understand their corresponding USD values for further analysis or reporting purposes.
MODEL: dydx_ethereum_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model creates a view called 'flashloans' that calculates the amount and fee of flash loans on dYdX, along with other relevant information such as block time, transaction hash, currency contract and symbol. It also joins this data with an external source to calculate the USD value of each loan. This enables data analysts to analyze flash loan activity on dYdX in terms of both cryptocurrency amounts and their corresponding USD values.
SECTOR: ens
toggle to see all model updates
MODEL: ens_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that enables data analysts to track the Forefront Airdrop on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash and amount of tokens received in both raw and original values. Additionally, it calculates the USD value of each token based on its price at the time of receipt or earliest available price if before then. This allows for analysis of user behavior during this specific event within a defined timeframe.
SECTOR: forta_network
toggle to see all model updates
MODEL: forta_network_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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.
MODEL: oneinch_fusion_executors.sql
🟠 Modified by:
🔧 PR: #3376, [oneinch] 0x hotfix
🧙 Author: @grkhr on 2023-05-24
📝 Summary: This SQL model adds a column to the chains table called resolver_executor. The new column is created by concatenating '0x' with a substring of input starting at position 99 and taking 40 characters. The original value of resolver_executor was removed from the select statement. All other columns remain unchanged in this model, which selects data from an Ethereum traces source where
toequals '0xcb8308fcb7bc2f84ed1bea2c016991d34de5cc77'.🔧 PR: #3376, [oneinch] fusion executors quotes fix
🧙 Author: @grkhr on 2023-05-22
📝 Summary: In this SQL model, the
fromcolumn is renamed toresolver_address. The query filters for specific conditions such as a certain value in the input and block time. A new CTE called 'chains' is added which selects all values from another table with some additional filtering. Finally, there's a Trino query that includes a new CTE called 'chains'.SECTOR: op
toggle to see all model updates
MODEL: op_optimism_airdrop_1_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that tracks the distribution of an airdrop on the Optimism blockchain. It includes information such as recipient address, transaction hash, amount received in both raw and original token units, USD value at time of distribution (using historical price data), and other identifying details about the project. The model also allows for incremental updates to be made based on recent activity within the past week.
SECTOR: paladin
toggle to see all model updates
MODEL: paladin_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that calculates the USD value of Paladin (PAL) tokens distributed during an airdrop. It uses data from two sources, one containing information about token distribution and another with historical price data for PAL. The resulting table includes columns for blockchain, block time and number, project name, recipient address, transaction hash, amount of tokens distributed in both raw and original values as well as their corresponding USD value at the time of distribution.
SECTOR: paraswap
toggle to see all model updates
MODEL: paraswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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. It uses data from two tables,
erc20_ethereumanddex_prices, to calculate the amount in USD based on median prices during specific time periods. The model also includes filters for specific contract addresses, sender addresses, and block times. This enables data analysts to easily track and analyze transaction volumes and values related to Paraswap's airdrop program on Ethereum.MODEL: paraswap_v5_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #3373, ParaSwap - Add missing events and price data
🧙 Author: @springzh on 2023-05-23
📝 Summary: The SQL model has been updated to include additional tables and variables. The
project_start_datevariable was changed from '2022-06-15' to '2021-09-08'. Two new CTEs,price_missed_previousandprice_missed_next, were added for USDC.e AND USDT.e price records that may be missing before 2022 or after the latest swaps. Several left joins were modified with coalesce statements in order to use the new CTEs when necessary. Finally, some formatting changes have been made throughout the code for readability purposes only.MODEL: paraswap_v5_bnb_trades.sql
🟠 Modified by:
🔧 PR: #3373, ParaSwap - Add missing events and price data
🧙 Author: @springzh on 2023-05-23
📝 Summary: In this SQL model, two new tables were added to the list of trade event tables: AugustusSwapperV5_evt_BoughtV3 and AugustusSwapperV5_evt_SwappedV3. These tables are sourced from paraswap_bnb. No other changes were made in the model except for adding these two new table sources to an existing list of table sources called 'trade_event_tables'.
MODEL: paraswap_v5_fantom_trades.sql
🟠 Modified by:
🔧 PR: #3373, ParaSwap - Add missing events and price data
🧙 Author: @springzh on 2023-05-23
📝 Summary: The code sets a variable for the project start date based on the earliest event block time in bought and swapped events. In this pull request, the project start date was changed from June 15th, 2022 to January 21st, 2022. The rest of the code appears unchanged.
MODEL: paraswap_v4_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3373, ParaSwap - Add missing events and price data
🧙 Author: @springzh on 2023-05-23
📝 Summary: Two new CTEs were added to the SQL model. The first one, 'price_missed_previous', selects the earliest WMATIC price record from a source table and is used to fill in missing prices for swaps that occurred before this record. The second one, 'price_missed_next', selects the latest WMATIC price record from a source table and is used to fill in missing prices for swaps that occurred after this record. Both CTEs are left joined with other tables using conditions based on swap times and contract addresses of tokens being bought or sold during these swaps.
MODEL: paraswap_v5_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3373, ParaSwap - Add missing events and price data
🧙 Author: @springzh on 2023-05-23
📝 Summary: Two new CTEs were added to the SQL model. The first one, 'price_missed_previous', selects the earliest WMATIC price record from a source table and is used to fill in missing prices for swaps that occurred before this record. The second one, 'price_missed_next', selects the latest WMATIC price record from a source table and is used to fill in missing prices for swaps that occurred after this record. Both CTEs are left joined with other tables using conditions based on swap times and contract addresses of tokens being bought or sold during these swaps.
SECTOR: pooltogether
toggle to see all model updates
MODEL: pooltogether_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 analyze trends in POOL token distribution over time and understand its impact on market dynamics.
SECTOR: ribbon
toggle to see all model updates
MODEL: ribbon_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that tracks Ribbon token airdrops on the Ethereum blockchain. It includes information such as the recipient's address, transaction hash, amount of tokens received in both raw and original (decimal) form, and USD value at time of receipt. The model also joins with another table to fill in missing price data for calculating USD value. If run incrementally, it only pulls data from the past week.
SECTOR: safe
toggle to see all model updates
MODEL: safe_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that tracks Safe token transfers on the Ethereum blockchain, including recipient address, transaction hash, amount transferred in both raw and original (decimal) values, and USD value at the time of transfer. It also includes information about the token itself such as its contract address and symbol. The model uses data from an external source to calculate USD value based on median prices during specific time periods. This enables data analysts to track Safe token movements over time and analyze trends in usage or adoption of this cryptocurrency.
SECTOR: shapeshift
toggle to see all model updates
MODEL: shapeshift_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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.
SECTOR: snowswap
toggle to see all model updates
MODEL: snowswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that enables data analysts to track SnowSwap airdrops on the Ethereum blockchain. The table includes information such as block time, block number, recipient address, transaction hash and amount of SNOW tokens distributed during the airdrop. Additionally, it calculates the USD value of each distribution based on historical price data from an external source.
SECTOR: sudoswap
toggle to see all model updates
MODEL: sudoswap_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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.
MODEL: sudoswap_ethereum_pool_trades_agg_day.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The SQL model calculates trading metrics for Sudoswap. The changes made include renaming columns, changing the calculation of volume and fees to use raw values instead of converted ones, adding a join with a price table to calculate USD volume, and updating the source table name. Additionally, there are changes in filtering by date based on whether it is an incremental or full refresh run.
SECTOR: thales
toggle to see all model updates
MODEL: thales_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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 over time and analyze user behavior related to its usage on the Ethereum network.
SECTOR: tokenfy
toggle to see all model updates
MODEL: tokenfy_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a view that enables data analysts to retrieve Tokenfy Airdrop transactions on the Ethereum blockchain between January 21, 2022 and February 5, 2022. The view includes information such as recipient address, transaction hash, token amount in raw and original format (with decimals), USD value of the token at the time of transfer based on available price data from an external source.
SECTOR: tornado_cash
toggle to see all model updates
MODEL: tornado_cash_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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.
MODEL: uniswap_v3_arbitrum_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that calculates the amount and fee of flash loans on Uniswap v3 Arbitrum, along with their corresponding USD value. It also includes information such as block time, block number, transaction hash, currency contract address and symbol. The model enables data analysts to easily query this information for analysis or reporting purposes.
MODEL: uniswap_v3_bnb_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model creates a view called 'flashloans' that joins data from UniswapV3Factory_evt_PoolCreated and Pair_evt_Flash tables to provide information on flash loans. It also includes left joins with tokens_bnb_bep20 and prices tables to get additional details such as currency symbol, decimals, price in USD etc. The final output of the model is a table containing blockchain name, project name, version number along with other loan-related details like amount borrowed (in raw form and converted), fee paid etc., which can be used by data analysts for further analysis.
MODEL: uniswap_v3_ethereum_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that calculates the amount and fee of flash loans on Uniswap v3, along with their corresponding currency symbol, decimals, contract address and transaction hash. It also joins this data with token information to display the currency's symbol and decimal places. Additionally, it includes a left join to get USD prices for each flash loan by matching blockchain type (Ethereum) and minute of block time. This enables data analysts to analyze trends in flash loans on Uniswap v3 over time in both native cryptocurrency units as well as USD value.
MODEL: uniswap_v3_optimism_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that calculates flash loan data for Uniswap v3 on the Optimism blockchain. It includes information such as block time, block number, amount of currency borrowed and fees paid in raw form and converted to their respective decimals. Additionally, it provides the currency contract address and symbol used in each transaction along with its corresponding USD value at the time of borrowing. This model enables data analysts to easily analyze flash loans on Uniswap v3 using Optimism blockchain data alongside price information from external sources.
MODEL: uniswap_v3_polygon_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that summarizes flash loans on the Polygon network's Uniswap v3 protocol. It includes information such as block time, block number, loan amount in both raw and converted (USD) form, transaction hash, fee paid for the loan in both raw and converted (USD) form, currency contract address and symbol. This model enables data analysts to easily analyze flash loans on Uniswap v3 by providing them with a consolidated view of relevant data points.
MODEL: uniswap_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model creates a unified table that combines flashloan data from multiple Uniswap V3 instances across different blockchains. This enables data analysts to easily query and analyze flashloan activity across various networks in one place, without having to manually combine separate tables. The resulting table includes information such as the blockchain, project, version, block time, amount borrowed and fees paid for each transaction.
SECTOR: value_defi
toggle to see all model updates
MODEL: value_defi_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 Summary: This SQL model creates a table that calculates the USD value of vUSD tokens distributed in the Value DeFi Airdrop. The table includes information such as blockchain, block time and number, project name, recipient address, transaction hash and token details. It uses data from two sources to calculate the USD value based on median prices during specific time periods. This enables data analysts to analyze the distribution of vUSD tokens in terms of their dollar value over time for further analysis or reporting purposes.
SECTOR: x2y2
toggle to see all model updates
MODEL: x2y2_ethereum_airdrop_claims.sql
🟢 Added by:
🔧 PR: #2979, Create
airdrop.claimswith 38 airdrops🧙 Author: @hildobby on 2023-05-25
📝 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: zeroex
toggle to see all model updates
MODEL: zeroex_bnb_api_fills.sql
🟠 Modified by:
🔧 PR: #3390, zeroex - bnb fills update
🧙 Author: @RantumBits on 2023-05-25
📝 Summary: The diff of the SQL model shows changes made to a query that extracts data from Binance Smart Chain (BSC) blockchain. The changes include removing some columns and adding others, such as
affiliate_addressandmatcha_limit_order_flag. There are also modifications in the conditions used to filter data from different tables, including logs and traces. Additionally, there is an update on how token addresses are handled when joining with other tables. Finally, there is a change in how timestamps are truncated for matching with price information obtained from another source called 'prices'.🔧 PR: #3390, zeroex - fix for txs with multiple affiliate addresses [arb, ava, op, bnb, ftm]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: This SQL model selects distinct maker_token_amount_raw divided by 10 to the power of decimals as maker_token_amount, and also selects all_tx type, affiliate_address (which is replaced with max(affiliate_address) over a partition), swap_flag, matcha_limit_order_flag and a case statement. The case statement checks if the maker token is one of four specific tokens.
MODEL: zeroex_ethereum_api_fills.sql
🟠 Modified by:
🔧 PR: #3356, zeroex - bnb fills update
🧙 Author: @RantumBits on 2023-05-25
📝 Summary: The diff of the dbt SQL model shows a change in the zeroex_tx CTE. The only change made was to remove an unnecessary if statement that checked if the model was incremental before filtering by date. This filter ensures that only events after a certain date are included in the query results.
🔧 PR: #3356, zeroex - fix for txs with multiple affiliate addresses [poly, eth]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: The SQL model has been modified to include a window function that retrieves the maximum value of affiliate_address for each transaction hash. The rest of the SELECT statement remains unchanged, with maker_token_amount_raw being divided by 10 raised to the power of mp.decimals and some additional columns being selected based on their values.
MODEL: zeroex_ethereum_native_fills.sql
🟠 Modified by:
🔧 PR: #3293, zeroex - bnb fills update
🧙 Author: @RantumBits on 2023-05-25
📝 Summary: The changes made to the SQL model involve commenting out a CTE (Common Table Expression) called 'v3_fills' and another CTE called 'v4_limit_fills'. The commented-out code is replaced with a new query that combines data from three different tables using UNION ALL. This change appears to be related to versioning of protocols, as the original code had separate queries for each protocol version while the updated code combines all versions into one query.
MODEL: zeroex_polygon_native_fills.sql
🟠 Modified by:
🔧 PR: #3293, zeroex - bnb fills update
🧙 Author: @RantumBits on 2023-05-25
📝 Summary: The SQL model adds and removes a few lines of code. The removed line specifies the protocol version as 'v4'. The added line specifies the native order type as 'otc' and selects the maker address from fills table. Additionally, there are some changes in column aliases for block time and block number columns.
MODEL: zeroex_arbitrum_api_fills.sql
🟠 Modified by:
🔧 PR: #3390, zeroex - fix for txs with multiple affiliate addresses [arb, ava, op, bnb, ftm]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: The SQL model has a SELECT statement that calculates the maker_token_amount and maker_token_amount_raw. It also includes the type, affiliate_address, swap_flag and matcha_limit_order_flag columns. The diff shows that a window function was added to get the maximum value of affiliate_address partitioned by tx_hash column. No other significant changes were made except for adding some token addresses in CASE statements at the end of SELECT statement.
MODEL: zeroex_avalanche_c_api_fills.sql
🟠 Modified by:
🔧 PR: #3390, zeroex - fix for txs with multiple affiliate addresses [arb, ava, op, bnb, ftm]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: The SQL model calculates the maker token amount by dividing the raw value with 10 to the power of decimals. It also includes columns for transaction type, affiliate address, swap flag and matcha limit order flag. The diff adds a window function that selects maximum affiliate address partitioned by transaction hash. There is also a case statement that checks if maker token belongs to certain addresses but it's incomplete in this diff.
MODEL: zeroex_fantom_api_fills.sql
🟠 Modified by:
🔧 PR: #3390, zeroex - fix for txs with multiple affiliate addresses [arb, ava, op, bnb, ftm]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: The SQL model calculates the maker token amount by dividing the raw value with 10 to the power of decimals. It also selects type, affiliate address, swap flag and matcha limit order flag from a table called all_tx. The new logic added is that it uses max function over partitioned data to get affiliate address for each transaction hash instead of selecting directly from all_tx table. There are no columns or lines listed in this diff so we cannot provide more details on what was removed or other changes made in this model.
MODEL: zeroex_optimism_api_fills.sql
🟠 Modified by:
🔧 PR: #3390, zeroex - fix for txs with multiple affiliate addresses [arb, ava, op, bnb, ftm]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: This SQL model calculates the maker token amount and type of a transaction, as well as whether it is a swap or matcha limit order. The diff adds a window function to retrieve the maximum affiliate address for each transaction hash. It also includes logic to calculate the USD volume of each transaction based on either maker or taker token amounts and their respective prices in USD.
MODEL: zeroex_polygon_api_fills.sql
🟠 Modified by:
🔧 PR: #3356, zeroex - fix for txs with multiple affiliate addresses [poly, eth]
🧙 Author: @RantumBits on 2023-05-23
📝 Summary: The diff of the dbt SQL model shows changes made to several CTEs. The
zeroex_txCTE had columns added and removed, while thev4_rfq_fills_no_bridge,v4_limit_fills_no_bridge,otc_fills,ERC20BridgeTransfer,NewBridgeFill,direct_PLPandall_txCTEs all had some columns removed. Additionally, a new window function was added to select distinct affiliate addresses over partitioned transactions in the final SELECT statement.SECTOR: _sector
toggle to see all model updates
MODEL: collectionswap_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #3405, nft.trades parents cast as decimal number_of_items
🧙 Author: @dot2dotseurat on 2023-05-25
📝 Summary: The SQL model is for a table called 'raw_trades'. The diff shows that the data type of the column 'nft_amount' was changed from an integer to a decimal. The other columns remain unchanged.
MODEL: looksrare_v2_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #3405, nft.trades parents cast as decimal number_of_items
🧙 Author: @dot2dotseurat on 2023-05-25
📝 Summary: The SQL model adds a cast function to convert the nft_amount column into DECIMAL(38,0) data type. The rest of the columns remain unchanged.
MODEL: nft_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The added code selects data from two different tables and combines them using UNION ALL. It selects multiple columns from each table, including blockchain, project, version, token_id and trade_type. The WHERE clause filters out any rows where the combination of project and version already exists in the first table selected.
MODEL: nft_events_old.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The given SQL model is a list of nft_models with some models being removed and others added. The removed models are 'aavegotchi_polygon_events', 'archipelago_ethereum_events', 'blur_ethereum_events', etc. while the added ones include 'element_bnb_events','element_avalanche_c_events','fractal_polygon_event' among others.The SELECT statement at the end selects all columns from these nft_models.
MODEL: blur_ethereum_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: [changes too large] The model blur_ethereum_events.sql was removed.
MODEL: sudoswap_ethereum_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: [changes too large] The model sudoswap_ethereum_events.sql was removed.
MODEL: superrare_ethereum_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: [changes too large] The model superrare_ethereum_events.sql was removed.
MODEL: zora_ethereum_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: [changes too large] The model zora_ethereum_events.sql was removed.
SECTOR: lido
toggle to see all model updates
MODEL: lido_accounting_ethereum_buffer_inflow.sql
🟢 Added by:
🔧 PR: #3391, buffer flow
🧙 Author: @ppclunghe on 2023-05-24
📝 Summary: This SQL model creates a table that combines data from three different sources related to the Lido Ethereum network. The resulting table includes information on the amount of tokens transferred, token type, transaction hash and date for each event. This enables data analysts to easily query and analyze transfer activity on the Lido Ethereum network over time periods ranging from daily to longer intervals.
MODEL: lido_accounting_ethereum_buffer_outflow.sql
🟢 Added by:
🔧 PR: #3391, buffer flow
🧙 Author: @ppclunghe on 2023-05-24
📝 Summary: This SQL model creates a view that retrieves data from the WithdrawalQueueERC721_evt_WithdrawalsFinalized table in the Lido Ethereum database. It selects and renames specific columns, including period, amount, token, evt_tx_hash and day. This view enables data analysts to easily query and analyze information about finalized withdrawals of ETH tokens from the Lido protocol on a daily basis.
MODEL: lido_accounting_ethereum_revenue.sql
🟠 Modified by:
🔧 PR: #3391, buffer flow
🧙 Author: @ppclunghe on 2023-05-24
📝 Summary: The diff shows changes made to the
protocol_fee_distributionSQL model. A new formula has been added to calculatedepositors_revenue. The previous formula subtracted a percentage of protocol fee points from the sum of revenue generated by treasury, operators and insurance fees. The new formula multiplies this sum with 10 before subtracting the percentage of protocol fee points. All other columns remain unchanged in this model.MODEL: lido_accounting_ethereum_deposits.sql
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: The SQL model adds a SELECT statement that selects the block_time column and aliases it as period.
MODEL: lido_accounting_ethereum_liquidity_incentives.sql
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: The diff of the SQL model is not provided in the question. Please provide the diff so that I can summarize it for you.
MODEL: lido_accounting_ethereum_sources.yml
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: [changes too large] The model lido_accounting_ethereum_sources.yml was renamed.
MODEL: lido_accounting.sql
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: [changes too large] The model lido_accounting.sql was renamed.
MODEL: lido_liquidity.sql
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: The change in this SQL model involves renaming a reference to another model. The original reference was to 'lido_ethereum_liquidity_kyberswap_pools' and it has been changed to 'lido_liquidity_ethereum_kyberswap_pools'.
MODEL: lido_liquidity_ethereum_kyberswap_pools.sql
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: [changes too large] The model lido_liquidity_ethereum_kyberswap_pools.sql was renamed.
MODEL: lido_liquidity_ethereum_sources.yml
🟠 Modified by:
🔧 PR: #3380, Fix Lido spells structure
🧙 Author: @gregshestakovlido on 2023-05-22
📝 Summary: [changes too large] The model lido_liquidity_ethereum_sources.yml was renamed.
SECTOR: openocean
toggle to see all model updates
MODEL: openocean_v2_avalanche_c_trades.sql
🟠 Modified by:
🔧 PR: #3389, Rename decoded table OpenOceanExchangeProxy to OpenOceanExchange on AVAX
🧙 Author: @antonio-mendes on 2023-05-23
📝 Summary: The change in the SQL model involves replacing a source table with another one. The new source table has the same name as the old one but with a slight difference in spelling. Additionally, there is an optional condition that filters out events before a certain date if it's not an incremental run.
SECTOR: cryptopunks
toggle to see all model updates
MODEL: cryptopunks_ethereum_all_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The changes made to the SQL model involve replacing a table with another one, renaming some columns and changing their values. The new table has an additional filter condition that limits the results to only those rows where project is 'cryptopunks'. A subquery was also modified by changing its source and column name. Finally, there were some modifications in grouping and ordering of data at the end of the query.
MODEL: cryptopunks_ethereum_current_bids.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The SQL model is making changes to a table called
combined_events_table. It removes two columns,token_idandamount_original, and replaces them with two new columns,nft_token_idandprice. It also renames one column from the original table to be named assub_tx_trade_id. The data source for this table has been changed from'cryptopunks_ethereum_events'to'nft_ethereum_trades_beta', but only where the project name is 'cryptopunks'.MODEL: cryptopunks_ethereum_current_listings.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The SQL model is being updated to reflect changes in the source data. The
all_buystable has been modified to use a new reference table,nft_ethereum_trades_beta, instead of the old one,cryptopunks_ethereum_events. Additionally, some column names have been changed:token_idis now callednft_token_id, and the column previously named asevt_indexhas been renamed as sub_tx_trade_id.MODEL: cryptopunks_ethereum_floor_price_over_time.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The SQL model is being updated to reflect changes in the source data. The
all_buystable has been modified to use a new reference table,nft_ethereum_trades_beta, instead of the old one,cryptopunks_ethereum_events. Additionally, some column names have been changed:token_idis now callednft_token_id, and the column previously named asevt_indexhas been renamed as sub_tx_trade_id.MODEL: cryptopunks_ethereum_listings_over_time.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The SQL model is being updated to reflect changes in the source data. The
all_buystable has been modified to use a new reference table,nft_ethereum_trades_beta, instead of the old one,cryptopunks_ethereum_events. Additionally, some column names have been changed:token_idis now callednft_token_id, and the column previously named asevt_indexhas been renamed as sub_tx_trade_id.MODEL: cryptopunks_ethereum_punk_offer_events.sql
🟠 Modified by:
🔧 PR: #3363, NFT deprecation 1
🧙 Author: @0xRobin on 2023-05-23
📝 Summary: The added code selects distinct
evt_tx_hashfrom a source table and uses it to filter out rows with matchingevt_tx_hashin the main table. The removed code used a different method of filtering by selecting distincttx_hashfrom another reference table. Both methods are used to ensure that duplicate data is not included in the final output, but the new method uses a different source for identifying duplicates. Additionally, there is an optional incremental update condition that filters results based on block time being within one week of current time.SECTOR: aave
toggle to see all model updates
MODEL: aave_v3_arbitrum_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model is for an Aave v3 arbitrum project. It selects data from a flashloans table and left joins it with tokens_arbitrum_erc20 and prices tables to get the blockchain, project, version, block time & number, amount in raw form as well as in USD after multiplying by price per unit of currency. The recipient's address along with contract address are also selected along with fee charged on the transaction. In addition to this if incremental update is being done then only those records will be selected which have event block time greater than or equal to 1 week ago from now.
MODEL: aave_v2_avalanche_c_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model is for an Aave v2 flash loan event on the Avalanche blockchain. The added code filters events that occurred within the last week if it's an incremental update. The SELECT statement retrieves various details about each flash loan, including its amount and fee in both raw and USD values, as well as information about the currency used, recipient address, contract address of the asset being borrowed against (if applicable), block number and time of occurrence. It also joins with a price table to convert amounts to USD using current exchange rates.
MODEL: aave_v3_avalanche_c_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loan data from an Aave v3 Avalanche pool. The change involves updating the version number of the project from 'v3' to '3'. Additionally, an incremental check was added such that only flash loans occurring within the last week are selected. The output columns include blockchain name, project name, block time and number as well as amount of currency involved in each transaction.
MODEL: aave_v1_ethereum_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loans data from Aave Ethereum LendingPool_evt_FlashLoan table. The change includes adding a filter condition for incremental updates, which limits the selection of data to events occurring within the last week. Additionally, there is an update in version number from 'v1' to '1'.
MODEL: aave_v2_ethereum_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The SQL model is for an Aave project on the Ethereum blockchain. The version has been updated from 'v2' to '2'. The model selects data from a table called
LendingPool_evt_FlashLoanand joins it with another table calledtokens_ethereum_erc20. It then filters the results where flash.amount is greater than 0. If it's an incremental update, only records within the last week are selected. Finally, some columns are selected and renamed as per requirements of this particular query output format.MODEL: aave_v3_ethereum_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loan data from Aave v3 Ethereum blockchain. The change involves updating the version number of the project and adding a conditional statement for incremental updates. The selected columns include blockchain, project name, block time and number, as well as amount in raw format converted to decimals using currency decimal places.
MODEL: aave_v3_fantom_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects data from the Aave v3 FlashLoan event table in Fantom blockchain. The change involves updating the version number of the project from 'v3' to '3'. Additionally, an incremental check was added such that only events within one week are selected.
MODEL: aave_v3_optimism_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loan data from Aave v3 on the Optimism blockchain. The change involves updating the version number of Aave from 'v3' to '3'. Additionally, an incremental check was added such that only flash loans occurring within the last week are selected. The resulting output includes details about each flash loan including its amount and currency decimals.
MODEL: aave_v2_polygon_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loans data from Aave v2 on Polygon blockchain. The main change is the version number which was updated from 'v2' to '2'. Additionally, an incremental check was added to filter results by date range if the query is run incrementally.
MODEL: aave_v3_polygon_flashloans.sql
🟠 Modified by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: The diff shows changes made to a SQL model that selects flash loan data from Aave v3 on Polygon. The main change is the version number, which was changed from 'v3' to '3'. Additionally, an incremental filter was added to only select flash loans within the last week. The selected columns include blockchain type, project name (Aave), block time and number of each transaction and amount of currency involved in each transaction after conversion using its decimal value.
SECTOR: balancer
toggle to see all model updates
MODEL: balancer_v2_arbitrum_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that calculates the amount and USD value of flash loans on the Balancer project in Arbitrum blockchain. It also includes information such as block time, block number, transaction hash, fee amount and currency details. The model enables data analysts to easily query this information for analysis purposes.
MODEL: balancer_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This SQL model creates a unified table that combines data from multiple Balancer flashloan models across different blockchain networks. This enables data analysts to easily query and analyze flashloan activity on various networks in one place, including the amount of funds borrowed, fees paid, and currency symbols used.
MODEL: balancer_v2_ethereum_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that enables data analysts to query and analyze flash loans on the Ethereum blockchain using Balancer v2. The table includes information such as block time, block number, loan amount in both raw and converted (USD) values, transaction hash, fee amount, currency contract address and symbol. It also joins with an external price source to provide USD conversion rates for each loan.
MODEL: balancer_v2_gnosis_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that summarizes flash loans data from the Balancer V2 Gnosis vault. It includes information such as block time, block number, loan amount in both raw and converted USD values, transaction hash, fee amount in both raw and converted USD values, currency contract address and symbol. This model enables data analysts to easily query this information for analysis purposes by joining with other tables or aggregating the results.
MODEL: balancer_v2_optimism_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that summarizes flash loans on the Balancer project in Optimism blockchain. It includes information such as block time, block number, loan amount and fee (in both raw and converted values), currency contract details, transaction hash and index. Additionally, it joins with another table to calculate the USD value of each loan at the given minute using current prices for each currency involved. This enables data analysts to easily analyze flash loans on Balancer in Optimism blockchain along with their corresponding USD values.
MODEL: balancer_v2_polygon_flashloans.sql
🟢 Added by:
🔧 PR: #3294, Balancer, dYdX & Uniswap Flashloans
🧙 Author: @hildobby on 2023-05-22
📝 Summary: This new dbt SQL model creates a table that summarizes flash loans on the Polygon blockchain using data from Balancer v2. The table includes information such as block time, block number, loan amount in both raw and USD values, transaction hash, fee amount in both raw and token-specific values, currency contract address and symbol. This model enables data analysts to easily query this information for analysis of flash loans on the Polygon network within Balancer v2.
Beta Was this translation helpful? Give feedback.
All reactions