📰 2023-12-01: Weekly Prophet! #4918
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 25 PRs merged from 15 wizards. Great job everyone! 🎉
We had 73 added models 🟢 and 149 modified models 🟠 for 8 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_trades.sql
🟠 Modified by:
🔧 PR: #4861, Added mummy_finance optimism trades
🧙 Author: @ARDev097 on 2023-11-30
📝 Summary: The reference models that were added or removed in the diff are: mummy_finance_optimism_trades
MODEL: dex_raw_pools.sql
🟠 Modified by:
🔧 PR: #4885, dex.raw_pools fix optimism legacy
🧙 Author: @grkhr on 2023-11-28
📝 Summary: In this SQL model, the 'optimism_legacy_ovm1' blockchain was removed from the list of blockchains. Additionally, a new table called '_optimism_ovm1_legacy' was added which contains hardcoded data for legacy pools in the 'optimism' blockchain. The main logic of this change is to replace occurrences of 'optimism_legacy_ovm1' with 'optimism', and include data from both tables in the final result set using a union all operation.
🔧 PR: #4885, dex.raw_pools: add missing legacy OP pools
🧙 Author: @grkhr on 2023-11-28
📝 Summary: In this SQL model, a new blockchain called 'optimism_legacy_ovm1' was added to the list of existing blockchains. Additionally, in the pool_created_logs table, any occurrence of 'optimism_legacy_ovm1' in the blockchain column is replaced with 'optimism'.
SECTOR: prices
toggle to see all model updates
MODEL: prices_solana_tokens.sql
🟠 Modified by:
🔧 PR: #4860, add PYTH to prices table
🧙 Author: @cctdaniel on 2023-11-30
📝 Summary: The token symbols that were added or removed are: PYTH
MODEL: prices_polygon_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Update prices_polygon_tokens.sql
🧙 Author: @hipiair on 2023-11-29
📝 Summary: The token symbols that were added or removed are: VOXEL
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: The token symbols that were added or removed are: AAVE, agEUR, axlUSDC, BAL
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: The token symbols that were added or removed are: ACH, axlUSDC
MODEL: prices_avalanche_c_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: The token symbols that were added or removed in the diff of the dbt SQL model are: Added: AAVE.e, axlUSDT, axlATOM, FRAX Removed: axlusdc-axelar-usd-coin
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: The token symbols that were added or removed in the diff are: ANKR, ATOM, AUTO, axlUSDC (removed), AXS, BANANA, BAT (added), GST, BSW (added), DAR (removed), CHR (removed), FGD,TWT,BFG.
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: The token symbols that were added or removed are: COLLAR, CORA, CXO, DAR, DDOS, EPK, EQUAD,
FANC, GOB,JAR,OATH,TOTM,BUCC,FOL0 ,IMGNAI ,WOXEN,XRIO,WETH,bpETH,GRAIN and VERSE
MODEL: prices_fantom_tokens.sql
🟠 Modified by:
🔧 PR: #4874, Drop stale prices
🧙 Author: @aalan3 on 2023-11-27
📝 Summary: [changes too large] The model prices_fantom_tokens.sql was modified.
SECTOR: _sector
toggle to see all model updates
MODEL: tokens_zora_base_transfers.sql
🟢 Added by:
🔧 PR: #4916, Add zora transfers
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers of assets on the Zora blockchain. It combines data from multiple sources including traces, transactions, and ERC20 transfers. The model does not specify a native contract address for the blockchain.
MODEL: tokens_zora_transfers.sql
🟢 Added by:
🔧 PR: #4916, Add zora transfers
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the Zora blockchain. It uses a base table called 'tokens_zora_base_transfers' and adds additional information related to the transfers, such as native symbol (ETH). This enriched data can be used for further analysis and insights by data analysts.
MODEL: tokens_arbitrum_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This dbt SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers on the Arbitrum blockchain. It combines data from multiple sources including traces, transactions, and ERC20 transfers. The model also allows for specifying a native contract address if needed.
MODEL: tokens_arbitrum_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the Arbitrum blockchain. It uses a base table called 'tokens_arbitrum_base_transfers' and adds additional information related to transfers on the blockchain, specifically for the native symbol 'ETH'.
MODEL: tokens_avalanche_c_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers on the Avalanche blockchain. It sources data from tables such as 'traces', 'transactions', and 'erc20_transfers'. The model also includes a parameter for the native contract address, which is currently set to null.
MODEL: tokens_avalanche_c_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich the transfers data from the 'tokens_avalanche_c_base_transfers' table with additional information related to the Avalanche blockchain. It specifically focuses on transfers involving the native token 'AVAX'.
MODEL: tokens_base_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that combines data from multiple sources including blockchain traces, transactions, and ERC20 transfers. It enables data analysts to analyze and track transfers of assets on the blockchain. The native_contract_address parameter allows for filtering specific contract addresses if needed.
MODEL: tokens_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich the transfers data from the base blockchain by adding additional information. It uses a reference to the
tokens_base_base_transferstable and specifies that it is for theETHnative symbol.MODEL: tokens_celo_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers on the Celo blockchain. It sources data from various tables including 'traces', 'transactions', and 'erc20_transfers'. The model does not specify a native contract address.
MODEL: tokens_celo_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the Celo blockchain. It uses a base table called 'tokens_celo_base_transfers' and adds additional information related to transfers on the Celo blockchain, specifically for the native token 'CELO'.
MODEL: tokens_ethereum_base_transfers.sql
🟠 Modified by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: The main logic added in this SQL model is the use of a variable for the native_contract_address. The transfers_base table is joined with the traces table from the ethereum blockchain. Additionally, there is a UNION ALL statement that selects all columns from transfers_base_wrapped_token and combines it with previous results.
MODEL: tokens_ethereum_transfers.sql
🟠 Modified by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: The diff of the dbt SQL model shows that a function called 'transfers_enrich' was added. It takes two arguments: 'blockchain' and 'transfers_base'. The value for the argument 'blockchain' is set to 'ethereum', and the value for the argument 'transfers_base' is set by referencing another model called 'tokens_ethereum_base_transfers'.
MODEL: tokens_fantom_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers of assets on the Fantom blockchain. It combines data from multiple sources including traces, transactions, and ERC20 transfers. The model does not specify a native contract address for the blockchain.
MODEL: tokens_fantom_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich the transfers data from the Fantom blockchain. It uses a base table called 'tokens_fantom_base_transfers' and adds additional information related to the transfers, such as native symbol (FTM). This enriched data can be used for further analysis and insights by data analysts.
MODEL: tokens_gnosis_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This dbt SQL model creates a base table called 'transfers_base' that enables data analysts to analyze and query transfer data from the Gnosis blockchain. It combines information from multiple sources including traces, transactions, and ERC20 transfers. The model does not specify a native contract address for the blockchain.
MODEL: tokens_gnosis_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the Gnosis blockchain with additional information. It uses a base table called 'tokens_gnosis_base_transfers' and adds details specific to the xDAI native symbol. This enriched data can be used for further analysis and insights by analysts.
MODEL: tokens_optimism_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze and query transfer data on the Optimism blockchain. It sources information from tables such as 'traces', 'transactions', and 'erc20_transfers'. The model does not specify a native contract address.
MODEL: tokens_optimism_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the Optimism blockchain. It uses a base table called 'tokens_optimism_base_transfers' and adds additional information related to transfers on the blockchain, specifically for the native symbol 'ETH'.
MODEL: tokens_zksync_base_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates a base table called 'transfers_base' that enables data analysts to analyze transfers on the zksync blockchain. It sources data from tables such as 'traces', 'transactions', and 'erc20_transfers'. The model also specifies the native contract address for zksync as '0x00000000000000000000000...'.
MODEL: tokens_zksync_transfers.sql
🟢 Added by:
🔧 PR: #4698, Token transfers more chains
🧙 Author: @aalan3 on 2023-12-01
📝 Summary: This SQL model creates and enables data analysts to enrich transfer data from the zksync blockchain. It uses a base table called 'tokens_zksync_base_transfers' and adds additional information related to transfers, specifically for the native symbol 'ETH'.
MODEL: nft_base_native_mints.sql
🟢 Added by:
🔧 PR: #4819, Create macro for
nft.mintsand addnft_base_native_mints🧙 Author: @chuxinh on 2023-11-30
📝 Summary: This dbt SQL model creates a table called 'nft_mints' that enables data analysts to analyze and track the mints of non-fungible tokens (NFTs) on the blockchain. It combines data from various sources such as contracts, traces, transfers, and transactions to provide insights into NFT minting activities. The model also includes a specific Ethereum currency contract for reference.
MODEL: nft_ethereum_native_mints.sql
🟠 Modified by:
🔧 PR: #4819, Create macro for
nft.mintsand addnft_base_native_mints🧙 Author: @chuxinh on 2023-11-30
📝 Summary: The diff shows that a common table expression (CTE) called 'namespaces' was removed. It was used to select the address and minimum namespace from the 'ethereum.contracts' source, grouped by address. In its place, a new model called 'nft_mints' is added. This model uses multiple sources such as 'ethereum.contracts', 'ethereum.traces', etc., and includes various joins and calculations to retrieve data related to NFT mints in Ethereum blockchain. Overall, the logic of selecting NFT mint data has been refactored into a separate model for better organization and readability.
MODEL: nft_optimism_native_mints.sql
🟠 Modified by:
🔧 PR: #4819, Create macro for
nft.mintsand addnft_base_native_mints🧙 Author: @chuxinh on 2023-11-30
📝 Summary: The main logic added in this SQL model is the
nft_mintsmacro. This macro takes several parameters and performs a series of joins and calculations to retrieve data related to NFT mints on the Optimism blockchain. The resulting dataset includes information such as blockchain, project, version, block time, token ID, trade type (single item mint or bundle mint), number of items minted, trade category (mint), event type (mint), buyer/seller addresses, transaction hash and more. The query also includes filtering conditions based on incremental updates and excludes bridged L1 NFT collections to L2.MODEL: nft_zora_native_mints.sql
🟢 Added by:
🔧 PR: #4819, Create macro for
nft.mintsand addnft_base_native_mints🧙 Author: @chuxinh on 2023-11-30
📝 Summary: This dbt SQL model creates a table called 'nft_mints' that enables data analysts to analyze and track NFT mints on the Zora blockchain. It uses various sources such as contracts, traces, ERC20 transfers, and transactions to gather relevant data. Additionally, it includes an Ethereum currency contract for reference.
MODEL: nft_mints.sql
🟠 Modified by:
🔧 PR: #4819, Create macro for
nft.mintsand addnft_base_native_mints🧙 Author: @chuxinh on 2023-11-30
📝 Summary: In this SQL model, four native mints are added to the existing list of native mints. The new additions include 'nft_base_native_mints' and 'nft_zora_native_mints'.
MODEL: dex_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #4832, Added mummy_finance optimism trades
🧙 Author: @ARDev097 on 2023-11-30
📝 Summary: In this SQL model, a new base model called 'mummy_finance_optimism_base_trades' was added to the existing list of base models.
🔧 PR: #4832, Add sushiswap to
dex.trades_beta🧙 Author: @tomfutago on 2023-11-27
📝 Summary: In this diff, two new base models (
sushiswap_v1_optimism_base_tradesandsushiswap_v2_optimism_base_trades) were added to the existing list of base models (uniswap_v3_optimism_base_tradesandwoofi_optimism_base_trades). These new models are then used in a common table expression calledbase_union.MODEL: mummy_finance_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #4861, Added mummy_finance optimism trades
🧙 Author: @ARDev097 on 2023-11-30
📝 Summary: This SQL model creates a table that combines trade data from the 'Router_evt_Swap' table in the 'mummy_finance_optimism' database. It includes information such as block time, taker and maker addresses, token amounts bought and sold, contract addresses, transaction hashes, and event indexes. This model enables data analysts to analyze trade activity on the Mummy Finance project on the Optimism blockchain.
MODEL: dex_arbitrum_base_trades.sql
🟠 Modified by:
🔧 PR: #4832, Add arbswap to
dex.trades_beta🧙 Author: @tomfutago on 2023-11-30
📝 Summary: The model added a reference to 'arbswap_arbitrum_base_trades' in addition to the existing references.
🔧 PR: #4832, Add airswap to
dex.trades_beta🧙 Author: @tomfutago on 2023-11-27
📝 Summary: In this diff, the following models were added to the
base_modelslist:airswap_arbitrum_base_trades.🔧 PR: #4832, Add sushiswap to
dex.trades_beta🧙 Author: @tomfutago on 2023-11-27
📝 Summary: In this diff, three new models (
sushiswap_v1_arbitrum_base_trades,sushiswap_v2_arbitrum_base_trades) were added to thebase_modelslist. These models are then used in a common table expression calledbase_union.MODEL: arbswap_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #4869, Add arbswap to
dex.trades_beta🧙 Author: @tomfutago on 2023-11-30
📝 Summary: This SQL model creates a table that combines data from two different sources related to the Arbswap project on the Arbitrum blockchain. It includes information about trades made on an AMM and a Stableswap, such as block number, block time, token amounts bought and sold, addresses of tokens involved in the trade, taker and maker addresses, project contract address, transaction hash,and event index. This model enables data analysts to analyze trading activity on Arbswap using this combined dataset.
MODEL: rabbithole_polygon_rewards.sql
🟠 Modified by:
🔧 PR: #4889, referrals bugfix for polygon native token
🧙 Author: @0xRobin on 2023-11-30
📝 Summary: In this SQL model, a new parameter called 'native_currency_contract' was added with the value '0x00000000000000000000000...'. This parameter is used in the rabbithole_referral_rewards model along with other existing parameters like 'blockchain' and 'QuestFactory_evt_MintFeePaid'.
MODEL: mintfun_base_rewards.sql
🟢 Added by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: This SQL model creates a table called 'mintfun_referral_rewards' that enables data analysts to track and analyze referral rewards in the Mint Fun application. The table is populated with data from the 'MintPayout_evt_MintDeposit' source table in the 'mint_fun_base' database.
MODEL: mintfun_ethereum_rewards.sql
🟢 Added by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: This SQL model creates a table called 'mintfun_referral_rewards' that enables data analysts to track and analyze referral rewards in the Ethereum blockchain. The data for this analysis is sourced from the 'MintPayout_evt_MintDeposit' table in the 'mint_fun_ethereum' database.
MODEL: mintfun_optimism_rewards.sql
🟢 Added by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: This SQL model creates a table called 'mintfun_referral_rewards' that enables data analysts to track and analyze referral rewards in the Mint Fun application on the Optimism blockchain. The data for this table is sourced from the 'MintPayout_evt_MintDeposit' event in the 'mint_fun_optimism' database.
MODEL: mintfun_zora_rewards.sql
🟢 Added by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: This SQL model creates a table called 'mintfun_referral_rewards' that enables data analysts to track and analyze referral rewards in the Zora blockchain. The data for this analysis is sourced from the 'MintPayout_evt_MintDeposit' table in the 'mint_fun_zora' database.
MODEL: referral_rewards.sql
🟠 Modified by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: The main logic added in this diff is the inclusion of a CI counter to include the model in a CI run. Additionally, there is an enrichment of referral rewards using another model called 'referral_staging_rewards'.
MODEL: referral_staging_rewards.sql
🟠 Modified by:
🔧 PR: #4888, Add mint.fun on ethereum, optimism, zora & base to the referral rewards spell
🧙 Author: @datadanne on 2023-11-30
📝 Summary: In this SQL model, several references to other models were added and one reference was removed. The added references include 'slugs_optimism_rewards', 'mintfun_ethereum_rewards', 'mintfun_optimism_rewards', 'mintfun_base_rewards', and 'mintfun_zora_rewards'. The main logic of the model is to select all columns from these referenced models.
MODEL: tokens_polygon_base_transfers.sql
🟢 Added by:
🔧 PR: #4909, Add polygon transfers
🧙 Author: @aalan3 on 2023-11-30
📝 Summary: This dbt SQL model creates a union of two datasets: transfers_base and transfers_base_wrapped_token. It enables data analysts to analyze and track blockchain transactions, traces, ERC20 transfers, wrapped token deposits, and withdrawals on the Polygon network.
MODEL: tokens_polygon_transfers.sql
🟢 Added by:
🔧 PR: #4909, Add polygon transfers
🧙 Author: @aalan3 on 2023-11-30
📝 Summary: This SQL model creates and enables data analysts to enrich the transfers data from the Polygon blockchain by adding additional information. It uses a base table called 'tokens_polygon_base_transfers' and specifies that the native symbol is 'MATIC'. The enrichment process allows for more comprehensive analysis of transfers on the Polygon blockchain.
MODEL: zora_base_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model creates a Zora mints table that enables data analysts to track the minting of ERC721 and ERC1155 tokens on the Zora platform. It uses transaction data from the base blockchain and specific event sources to populate this table.
MODEL: zora_ethereum_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model creates a Zora Mints table that enables data analysts to track and analyze the mints of ERC721 and ERC1155 tokens on the Ethereum blockchain. It uses specific event sources for each token type, as well as transaction data from the Ethereum blockchain.
MODEL: zora_goerli_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model enables data analysts to create a Zora mints table by merging data from various sources. It includes information about blockchain, wrapped native token address, ERC721 mints, ERC1155 mints, and transactions.
MODEL: zora_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model combines multiple Zora mints tables and selects various columns related to blockchain transactions, including block time, token standard, token ID, quantity, total price in different currencies (USD), recipient information, transaction hash and more. It enables data analysts to easily query and analyze minting activities across different Zora platforms.
MODEL: zora_optimism_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model creates a Zora mints table for the Optimism blockchain. It enables data analysts to track and analyze ERC721 and ERC1155 token mints on the Optimism network by pulling data from specific sources such as 'ERC721Drop_evt_Sale', 'ZoraCreator1155Impl_evt_Purchased', and 'transactions'.
MODEL: zora_zora_mints.sql
🟢 Added by:
🔧 PR: #4147, Create
zora.mintsincl. Ethereum, Zora Network, Optimism, Base & Goerli🧙 Author: @hildobby on 2023-11-30
📝 Summary: This SQL model creates a dataset that combines information from two different sources related to NFT transfers on the Zora blockchain. It includes details such as block time, block number, contract address, creator, token standard, token ID, quantity of tokens transferred, total price in ETH and USD equivalents for each transfer. The model also joins with a reference table for USD prices and filters the data based on specific conditions like incremental updates and sender address.
MODEL: nft_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nft_ethereum_base_trades.sql was renamed.
MODEL: _schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model _schema.yml was renamed.
MODEL: _sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model _sources.yml was renamed.
MODEL: archipelago_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model archipelago_ethereum_base_trades.sql was renamed.
MODEL: blur_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model blur_ethereum_base_trades.sql was renamed.
MODEL: blur_seaport_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model blur_seaport_ethereum_base_trades.sql was renamed.
MODEL: blur_v2_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model blur_v2_ethereum_base_trades.sql was renamed.
MODEL: collectionswap_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model collectionswap_ethereum_base_trades.sql was renamed.
MODEL: cryptopunks_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model cryptopunks_ethereum_base_trades.sql was renamed.
MODEL: element_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_ethereum_base_trades.sql was renamed.
MODEL: foundation_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model foundation_ethereum_base_trades.sql was renamed.
MODEL: looksrare_seaport_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model looksrare_seaport_ethereum_base_trades.sql was renamed.
MODEL: looksrare_v1_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model looksrare_v1_ethereum_base_trades.sql was renamed.
MODEL: looksrare_v2_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model looksrare_v2_ethereum_base_trades.sql was renamed.
MODEL: sudoswap_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model sudoswap_ethereum_base_trades.sql was renamed.
MODEL: superrare_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model superrare_ethereum_base_trades.sql was renamed.
MODEL: x2y2_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model x2y2_ethereum_base_trades.sql was renamed.
MODEL: zora_v1_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model zora_v1_ethereum_base_trades.sql was renamed.
MODEL: zora_v2_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model zora_v2_ethereum_base_trades.sql was renamed.
MODEL: zora_v3_ethereum_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model zora_v3_ethereum_base_trades.sql was renamed.
MODEL: nft_old_base_trades.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nft_old_base_trades.sql was renamed.
MODEL: aavegotchi_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model aavegotchi_polygon_events.sql was renamed.
MODEL: decentraland_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model decentraland_polygon_events.sql was renamed.
MODEL: decentraland_polygon_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model decentraland_polygon_schema.yml was renamed.
MODEL: decentraland_polygon_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model decentraland_polygon_sources.yml was renamed.
MODEL: element_avalanche_c_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_avalanche_c_events.sql was renamed.
MODEL: element_bnb_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_bnb_events.sql was renamed.
MODEL: element_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_polygon_events.sql was renamed.
MODEL: element_polygon_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_polygon_schema.yml was renamed.
MODEL: element_polygon_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model element_polygon_sources.yml was renamed.
MODEL: fractal_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model fractal_polygon_events.sql was renamed.
MODEL: fractal_polygon_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model fractal_polygon_schema.yml was renamed.
MODEL: fractal_polygon_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model fractal_polygon_sources.yml was renamed.
MODEL: liquidifty_bnb_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_bnb_events.sql was renamed.
MODEL: liquidifty_bnb_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_bnb_schema.yml was renamed.
MODEL: liquidifty_bnb_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_bnb_sources.yml was renamed.
MODEL: liquidifty_ethereum_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_ethereum_events.sql was renamed.
MODEL: liquidifty_ethereum_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_ethereum_schema.yml was renamed.
MODEL: liquidifty_ethereum_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model liquidifty_ethereum_sources.yml was renamed.
MODEL: magiceden_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model magiceden_polygon_events.sql was renamed.
MODEL: magiceden_polygon_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model magiceden_polygon_schema.yml was renamed.
MODEL: magiceden_solana_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model magiceden_solana_events.sql was renamed.
MODEL: magiceden_solana_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model magiceden_solana_schema.yml was renamed.
MODEL: mooar_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model mooar_polygon_events.sql was renamed.
MODEL: nftb_bnb_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftb_bnb_events.sql was renamed.
MODEL: nftb_bnb_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftb_bnb_schema.yml was renamed.
MODEL: nftb_bnb_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftb_bnb_sources.yml was renamed.
MODEL: nftearth_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftearth_optimism_events.sql was renamed.
MODEL: nftrade_bnb_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftrade_bnb_events.sql was renamed.
MODEL: nftrade_bnb_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftrade_bnb_schema.yml was renamed.
MODEL: nftrade_bnb_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model nftrade_bnb_sources.yml was renamed.
MODEL: oneplanet_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model oneplanet_polygon_events.sql was renamed.
MODEL: opensea_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model opensea_events.sql was renamed.
MODEL: opensea_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model opensea_schema.yml was renamed.
MODEL: pancakeswap_bnb_nft_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model pancakeswap_bnb_nft_events.sql was renamed.
MODEL: quix_optimism_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_optimism_schema.yml was renamed.
MODEL: quix_optimism_sources.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_optimism_sources.yml was renamed.
MODEL: quix_seaport_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_seaport_optimism_events.sql was renamed.
MODEL: quix_v1_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_v1_optimism_events.sql was renamed.
MODEL: quix_v2_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_v2_optimism_events.sql was renamed.
MODEL: quix_v3_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_v3_optimism_events.sql was renamed.
MODEL: quix_v4_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_v4_optimism_events.sql was renamed.
MODEL: quix_v5_optimism_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model quix_v5_optimism_events.sql was renamed.
MODEL: rarible_polygon_events.sql
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model rarible_polygon_events.sql was renamed.
MODEL: rarible_polygon_schema.yml
🟠 Modified by:
🔧 PR: #4897, [nft.trades] chains directory
🧙 Author: @0xRobin on 2023-11-29
📝 Summary: [changes too large] The model rarible_polygon_schem
Beta Was this translation helpful? Give feedback.
All reactions