📰 2023-12-15: Weekly Prophet!

[andrewhong5297]

This is your weekly summary of 36 PRs merged from 11 wizards. Great job everyone! 🎉
We had 182 added models 🟢 and 67 modified models 🟠 for 11 Sectors.

Sector	🔧 # PRs	🟢 # Added	🟠 # Modified	🧙 # Authors
dex	2	4	3	2
labels	3	0	4	3
tokens	2	1	5	2
prices	1	0	1	1
_sector	19	41	37	5
chainlink	1	134	1	1
rollup_economics	4	0	8	3
oneinch	4	2	5	2
zeroex	1	0	1	1
evms	1	0	1	1
solana_utils	1	0	1	1

SECTOR: dex

toggle to see all model updates

MODEL: dex_celo_sandwiched.sql

🟢 Added by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: This SQL model creates and enables data analysts to analyze transactions in the Celo blockchain. It uses a function called 'dex_sandwiched' that takes in the Celo blockchain, transaction data, and sandwich data as inputs. The model allows for further analysis of transactions within the Celo blockchain ecosystem.

MODEL: dex_celo_sandwiches.sql

🟢 Added by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: This SQL model creates and enables a new table called 'dex_sandwiches' for data analysts. It takes in the blockchain name as a parameter and retrieves transactions from the specified blockchain source. The purpose of this model is not explicitly stated, but it likely provides insights or analysis related to sandwich attacks in decentralized exchanges on the Celo blockchain.

MODEL: dex_zksync_sandwiched.sql

🟢 Added by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: This SQL model creates and enables a sandwiched view for a specified blockchain (in this case, 'zksync'). It takes in transactions data from the specified blockchain and combines it with an existing reference table called 'dex_zksync_sandwiches'. This allows data analysts to easily analyze and query the sandwiched view of transactions on the specified blockchain.

MODEL: dex_zksync_sandwiches.sql

🟢 Added by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: This SQL model creates and enables a new table called 'dex_sandwiches' for data analysts. It takes in the blockchain name (in this case, 'zksync') and transaction data as inputs to populate the table. The purpose or specific details of the 'dex_sandwiches' table are not provided in this summary.

MODEL: dex_sandwiched.sql

🟠 Modified by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: In this diff, two references ('dex_celo_sandwiched' and 'dex_zksync_sandwiched') were added to the SQL model. These references are then included in the SELECT statement along with other existing references.

MODEL: dex_sandwiches.sql

🟠 Modified by:

🔧 PR: #4984, Add Celo & zkSync to dex.[sandwiches, sandwiched]
🧙 Author: @hildobby on 2023-12-13
📝 Summary: In this diff, two references to SQL models ('dex_celo_sandwiches' and 'dex_zksync_sandwiches') were added to the existing list of references. The SELECT statement remains unchanged.

MODEL: dex_info.sql

🟠 Modified by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this SQL model, two rows were added to the temporary table. The rows represent projects named 'Mummy Finance' and 'Carbonhood'. Each row includes additional information such as the project name, marketplace type, and x_username.

SECTOR: labels

toggle to see all model updates

MODEL: labels_infrastructure.sql

🟠 Modified by:

🔧 PR: #4983, labels.infrastructure remove duplicates
🧙 Author: @jeff-dude on 2023-12-12
📝 Summary: The main logic that was added in this SQL model is the exclusion of a specific reference ('labels_eth_stakers') due to duplicates. Additionally, there are several references that were removed and replaced with new ones in the 'infrastructure_models' set. The SELECT statement remains unchanged.

MODEL: labels_bridges_ethereum.sql

🟠 Modified by:

🔧 PR: #4973, adding bridges addresses
🧙 Author: @ppclunghe on 2023-12-12
📝 Summary: In the given SQL model, several rows were added to a table. Each row represents a bridge in the Ethereum blockchain and includes information such as address, name, category, contributor, source, created_at date and updated_at date. The new rows were added by different contributors and have different addresses and names for each bridge.

MODEL: labels_op_chains_likely_bot_addresses.sql

🟠 Modified by:

🔧 PR: #4935, Reinit Likely Bot Labels OP
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: The main logic added in this SQL model is related to transaction frequency and sender concentration. It calculates various metrics such as the number of transactions involving ERC20 transfers, NFT transfers, token transfers, DEX trades, perpetual trades, and NFT trades for each sender on different blockchains. Additionally, it calculates metrics like maximum weekly transactions (wk_txs), maximum hourly transactions (max_hr_txs), average weekly transactions (avg_wk_txs), minimum block time (min_block_time), and maximum block time (max_block_time) for each sender.

MODEL: labels_op_chains_likely_bot_contracts.sql

🟠 Modified by:

🔧 PR: #4935, Reinit Likely Bot Labels OP
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: In this SQL model, the logic for detecting potential bot activity is being added. The main criteria for identifying bots include transaction frequency and sender concentration. The model calculates various metrics such as the number of ERC20 transfer transactions, NFT transfer transactions, token transfer transactions, DEX trade transactions, perpetual trade transactions, and NFT trade transactions. It also calculates the number of senders and average number of transactions per sender. Based on these metrics, different thresholds are applied to identify early bots (high transaction rate), established bots (low sender count), and wider distribution bots (high transaction rate with multiple senders).

SECTOR: tokens

toggle to see all model updates

MODEL: tokens_base_erc20.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: The added token symbols are: cbXEN, Fren Pet, FRIEND, BaseX, hETH, STG,
GROK, crvUSD , ALB , SCALE , CAROL , BDRIP ,
wstETH,eUSD,TAG,wUSDR,
MAV MAI WELL OG Points PYTH
BTRST KNC SDEX SOFI DEUS ECO EDG R

MODEL: tokens_base_nft_curated.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: The diff of the SQL model shows that several rows were added to the temporary table. The new rows include contract addresses, names, and symbols for different entities such as Base is for Builders, Omnichain Adventures (Part 2), Frenpet NFT, Merkly ONFT, l2telegraph.xyz, and L2Marathon.

MODEL: tokens_optimism_erc20_curated.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: In this SQL model, several rows were added to the 'raw_token_list' CTE. These rows include contract addresses, symbols, decimals, and token types for various tokens such as 'opXEN', 'BULL', 'USDV', 'MO', 'MERK', and others. One row with the symbol 'mooBIFI' was also added with a token type of 'receipt'.

MODEL: tokens_optimism_nft_curated.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: In this SQL model, several contract addresses and their corresponding names are added to a temporary table. The contract addresses and names include 'Omnichain Adventures', 'Forget About Time (2023)', 'Dream Travel', 'Mercy ROguE', 'Embrace the Chaos', and 'Omni Ax Adventures'.

MODEL: tokens_zora_nft_curated.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: The SQL model added several rows to the result set. The new rows include contract addresses, names, and symbols for various tokens such as 'Serene Lake Twilight', 'sqr(16)', 'Allure', and more. These additional rows were inserted into a temporary table called 'temp_table'.

MODEL: tokens_solana_transfers.sql

🟢 Added by:

🔧 PR: #4954, Solana transfers: it's time to finally add the beast
🧙 Author: @andrewhong5297 on 2023-12-11
📝 Summary: This SQL model creates a dataset that combines information from multiple tables related to token transfers and minting/burning actions in the Solana blockchain. It includes details such as block time, date, slot, action type (transfer/mint/burn), amount transferred/minted/burned, token addresses and balances for both source and destination accounts, transaction signer information, transaction ID, instruction indexes,and executing account. The model also allows for incremental updates based on the call_block_time field.

SECTOR: prices

toggle to see all model updates

MODEL: prices_optimism_tokens_curated.sql

🟠 Modified by:

🔧 PR: #4993, adding VELO price (Optimism)
🧙 Author: @ppclunghe on 2023-12-14
📝 Summary: In this diff, a line was removed that had the token name 'VELO' and an address associated with it. A new line was added with the same token name 'VELO', but with a different address associated with it.

SECTOR: _sector

toggle to see all model updates

MODEL: tokens_transfers.sql

🟢 Added by:

🔧 PR: #4987, add crosschain tokens.transfers
🧙 Author: @jeff-dude on 2023-12-15
📝 Summary: This SQL model creates a union of multiple token transfer tables from different blockchains. It combines the data from these tables into a single table, allowing data analysts to easily analyze and compare token transfers across different blockchains. The resulting table includes information such as unique key, blockchain, block date and time, transaction hash and index, event index, trace address, token standard, sender and receiver addresses (both raw and formatted), contract addresss symbol of the transferred tokens amount in both raw format and USD value.

🔧 PR: #4987, add crosschain tokens.transfers
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a union of multiple token transfer tables from different blockchains. It combines the data from these tables into a single table, allowing data analysts to easily analyze and compare token transfers across different blockchains. The resulting table includes information such as unique key, blockchain, block date and time, transaction hash, sender and receiver addresses, token symbol and amount transferred in both raw format and USD value.

MODEL: contracts_arbitrum_base_iterated_creators.sql

🟢 Added by:

🔧 PR: #4985, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze and query information about creators of contracts on the Arbitrum blockchain.

🔧 PR: #4985, Contracts - Add Arbitrum One
🧙 Author: @MSilb7 on 2023-12-13
📝 Summary: This SQL model creates a table called 'contracts_base_iterated_creators' that enables data analysts to analyze and query contract creators on the Arbitrum blockchain.

MODEL: contracts_arbitrum_base_starting_level.sql

🟢 Added by:

🔧 PR: #4985, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' with data specific to the 'arbitrum' blockchain. It enables data analysts to analyze and query information related to contracts on the arbitrum chain.

🔧 PR: #4985, Contracts - Add Arbitrum One
🧙 Author: @MSilb7 on 2023-12-13
📝 Summary: This SQL model creates a table called 'contracts_base_starting_level' with data specific to the 'arbitrum' blockchain. It enables data analysts to analyze and query information related to contracts on the arbitrum chain.

MODEL: contracts_arbitrum_contract_mapping.sql

🟢 Added by:

🔧 PR: #4985, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a contract mapping table for the 'arbitrum' blockchain. It enables data analysts to easily access and analyze information related to contracts on the arbitrum chain.

🔧 PR: #4985, Contracts - Add Arbitrum One
🧙 Author: @MSilb7 on 2023-12-13
📝 Summary: This SQL model creates a contract mapping table for the 'arbitrum' blockchain. It enables data analysts to easily access and analyze information related to contracts on the arbitrum chain.

MODEL: contracts_arbitrum_find_self_destruct_contracts.sql

🟢 Added by:

🔧 PR: #4985, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Arbitrum blockchain.

🔧 PR: #4985, Contracts - Add Arbitrum One
🧙 Author: @MSilb7 on 2023-12-13
📝 Summary: This SQL model creates a query called 'find_self_destruct_contracts' that enables data analysts to search for self-destruct contracts on the Arbitrum blockchain.

MODEL: contracts_contract_mapping.sql

🟠 Modified by:

🔧 PR: #4985, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: In this SQL model, a reference to the contracts_arbitrum_contract_mapping table was added. The comment suggests that chains for all EVMs in Dune should be added as well.

🔧 PR: #4985, Revert 'add (#4985)'
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: In this diff, the reference to the 'contracts_arbitrum_contract_mapping' model was removed. The comment suggests that chains for all EVMs in Dune should be added as a future task.

🔧 PR: #4985, Contracts - Add Arbitrum One
🧙 Author: @MSilb7 on 2023-12-13
📝 Summary: In this diff, a reference to the contracts_arbitrum_contract_mapping model was added. This means that the SQL model now includes a dependency on the contracts_arbitrum_contract_mapping model. Additionally, there is a comment indicating that chains for all EVMs in Dune should be added in the future.

MODEL: dex_gnosis_base_trades.sql

🟠 Modified by:

🔧 PR: #4940, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: In this diff, a reference to the 'honeyswap_v2_gnosis_base_trades' table was added to the SQL model. This table is now included in the base_union common table expression (CTE).

🔧 PR: #4940, Revert 'Add honeyswap to dex.trades_beta (#4928)'
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: The line ref('honeyswap_v2_gnosis_base_trades') was removed from the SQL model.

🔧 PR: #4940, Add honeyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: The model added a reference to 'honeyswap_v2_gnosis_base_trades' in addition to the existing references to 'sushiswap_v1_gnosis_base_trades', 'sushiswap_v2_gnosis_base_trades', and 'balancer_v2_gnosis_base_trades'.

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, two base models were removed (sushiswap_v1_gnosis_base_trades and sushiswap_v2_gnosis_base_trades) and one new base model was added (balancer_v2_gnosis_base_trades). The base_models variable now includes all three models.

MODEL: honeyswap_v2_gnosis_base_trades.sql

🟢 Added by:

🔧 PR: #4928, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Honeyswap decentralized exchange. It pulls data from two sources, 'UniswapV2Pair_evt_Swap' and 'UniswapV2Factory_evt_PairCreated', both from the Gnosis blockchain project. The model is compatible with Uniswap version 2.

🔧 PR: #4928, Add honeyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Honeyswap decentralized exchange. It pulls data from two sources, 'UniswapV2Pair_evt_Swap' and 'UniswapV2Factory_evt_PairCreated', both from the Gnosis blockchain project. The model is compatible with Uniswap version 2.

MODEL: dex_polygon_base_trades.sql

🟠 Modified by:

🔧 PR: #4866, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: In this diff, a reference to the 'honeyswap_v2_polygon_base_trades' table was added to the SQL model.

🔧 PR: #4866, Revert 'Add honeyswap to dex.trades_beta (#4928)'
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: The line ref('honeyswap_v2_polygon_base_trades') was removed from the SQL model.

🔧 PR: #4866, Add honeyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, a reference to the 'honeyswap_v2_polygon_base_trades' table was added to the SQL model.

🔧 PR: #4866, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, a reference to the balancer_v2_polygon_base_trades table was added. This reference is included in a list of other tables (sushiswap_v2_polygon_base_trades, quickswap_v2_polygon_base_trades, and quickswap_v3_polygon_base_trades) that are used to create a common table expression called base_union.

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: In this diff, the model 'apeswap_polygon_base_trades' was added to the list of base models.

MODEL: honeyswap_v2_polygon_base_trades.sql

🟢 Added by:

🔧 PR: #4928, Add back arbitrum contract mapping & honeyswap dex
🧙 Author: @jeff-dude on 2023-12-14
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Honeyswap decentralized exchange on the Polygon blockchain. It sources data from two events, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', and provides information about trades compatible with Uniswap version 2.

🔧 PR: #4928, Add honeyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Honeyswap decentralized exchange on the Polygon blockchain. It sources data from two events, 'Pair_evt_Swap' and 'Factory_evt_PairCreated'.

MODEL: dex_bnb_base_trades.sql

🟠 Modified by:

🔧 PR: #4866, Add biswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: In this diff, two references to SQL models were added: 'biswap_v2_bnb_base_trades' and 'biswap_v3_bnb_base_trades'. These models were included alongside existing references to 'trader_joe_v2_1_bnb_base_trades', 'pancakeswap_v2_bnb_base_trades', and 'pancakeswap_v3_bnb_base_trades'. The reference to the model named 'babyswap_bnb_base_trades' remains unchanged.

🔧 PR: #4866, Add babyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: In this diff, a reference to the model 'babyswap_bnb_base_trades' was added. This reference is included in a list of other models ('trader_joe_v2_1_bnb_base_trades', 'pancakeswap_v2_bnb_base_trades', and 'pancakeswap_v3_bnb_base_trades') within a WITH statement called base_union.

🔧 PR: #4866, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, two references to tables were added: 'pancakeswap_v2_bnb_base_trades' and 'pancakeswap_v3_bnb_base_trades'. These references are included in a WITH statement called base_union.

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: In this diff, the model 'apeswap_bnb_base_trades' was added to the list of base models.

MODEL: biswap_v2_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4924, Add biswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Biswap platform. It pulls data from two sources, 'BiswapPair_evt_Swap' and 'BiswapFactory_evt_PairCreated', and filters it based on the blockchain being 'bnb', project being 'biswap', and version being '2'.

MODEL: biswap_v3_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4924, Add biswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: This SQL model creates a table that extracts data from the BiswapPoolV3_evt_Swap and BiswapFactoryV3_evt_NewPool tables. It includes information such as block number, block time, token amounts bought and sold, addresses involved in the transaction, project contract address, transaction hash, and event index. This model enables data analysts to analyze trading activity on the Binance Smart Chain using Biswap protocol version 3.

MODEL: dex_fantom_base_trades.sql

🟠 Modified by:

🔧 PR: #4931, Add spookyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: The model added a reference to 'spookyswap_fantom_base_trades' in addition to the existing references to 'sushiswap_v1_fantom_base_trades', 'sushiswap_v2_fantom_base_trades', and 'spiritswap_fantom_base_trades'.

🔧 PR: #4931, Add spiritswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-12
📝 Summary: In this diff, two base models (sushiswap_v1_fantom_base_trades and sushiswap_v2_fantom_base_trades) were removed, and three new base models (sushiswap_v1_fantom_base_trades, sushiswap_v2_fantom_base_trades, and spiritswap_fantom_base_trades) were added to the set of base_models.

MODEL: spookyswap_fantom_base_trades.sql

🟢 Added by:

🔧 PR: #4930, Add spookyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade data from the SpookySwap project on the Fantom blockchain. It uses two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', to gather relevant information for analysis.

MODEL: babyswap_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4923, Add babyswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the BabySwap platform. It pulls data from two sources, 'BabyPair_evt_Swap' and 'BabyFactory_evt_PairCreated', and filters it based on the specified blockchain, project, and version parameters.

MODEL: dex_ethereum_base_trades.sql

🟠 Modified by:

🔧 PR: #4866, Add bancor to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: The model added a reference to 'bancor_ethereum_base_trades' in addition to the existing references to 'shibaswap_v1_ethereum_base_trades', 'balancer_v1_ethereum_base_trades', and 'balancer_v2_ethereum_base_trades'.

🔧 PR: #4866, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this SQL model, two references to tables have been added: 'pancakeswap_v2_ethereum_base_trades' and 'pancakeswap_v3_ethereum_base_trades'. These tables are now included along with the existing referenced tables in the model.

🔧 PR: #4866, Add shibaswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, a reference to the model 'shibaswap_v1_ethereum_base_trades' was added. This means that the SQL model now includes data from Shibaswap V1 Ethereum base trades in addition to Airswap, Sushiswap V1 and V2, Balancer V1 and V2 Ethereum base trades.

🔧 PR: #4866, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, two references to SQL models were added: 'balancer_v1_ethereum_base_trades' and 'balancer_v2_ethereum_base_trades'. These models are now included in the base_union common table expression.

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: In this diff, a reference to the 'apeswap_ethereum_base_trades' table was added to the SQL model.

MODEL: bancor_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4972, Add bancor to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-14
📝 Summary: This SQL model creates a table that combines data from two different sources, 'BancorNetwork_v' and 'BancorNetwork_evt_TokensTraded'. It retrieves information such as block number, block time, trader addresses, token amounts bought and sold, token addresses for buying and selling tokens, project contract address, transaction hash,and event index. This model enables data analysts to analyze trading activity on the Bancor network by providing a consolidated view of relevant data.

MODEL: dex_arbitrum_base_trades.sql

🟠 Modified by:

🔧 PR: #4940, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, two references to the arbitrum_base_trades table were added: pancakeswap_v2_arbitrum_base_trades and pancakeswap_v3_arbitrum_base_trades. These references were included in a list of other tables that are being referenced in the SQL model.

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: The model added a reference to 'balancer_v2_arbitrum_base_trades' in addition to the existing references.

MODEL: pancakeswap_v2_arbitrum_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the PancakeSwap project on the Arbitrum blockchain. It includes information about swaps made in version 2 of PancakeSwap, sourced from two specific events: 'PancakePair_evt_Swap' and 'PancakeFactory_evt_PairCreated'.

MODEL: pancakeswap_v3_arbitrum_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the PancakeSwap decentralized exchange. The table includes information about trades made on the Arbitrum blockchain using version 3 of the PancakeSwap protocol. It sources data from two events: 'PancakeV3Pool_evt_Swap' and 'PancakeV3Factory_evt_PoolCreated'.

MODEL: dex_base_base_trades.sql

🟠 Modified by:

🔧 PR: #4940, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this SQL model, two references to 'pancakeswap' base trades were added. The rest of the code remains unchanged.

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, a reference to the SQL model 'balancer_v2_base_base_trades' was added. This reference is included in a list of other models that are being referenced.

MODEL: pancakeswap_v2_base_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the PancakeSwap platform. It pulls data from two sources, 'PancakePair_evt_Swap' and 'PancakeFactory_evt_PairCreated', and is specifically designed for version 2 of the PancakeSwap protocol.

MODEL: pancakeswap_v3_base_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the PancakeSwap platform. It pulls data from two sources, 'PancakeV3Pool_evt_Swap' and 'PancakeV3Factory_evt_PoolCreated', and focuses on version 3 of the PancakeSwap protocol.

MODEL: pancakeswap_v2_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a view that combines data from PancakeSwap v2 trades and stableswap events. It includes information such as blockchain, project, version, block time and number, token amounts bought and sold, addresses of the tokens involved in the trade, taker and maker addresses, project contract addresss,and transaction hash. This view enables data analysts to analyze trading activity on PancakeSwap v2 for both regular swaps and stableswaps.

MODEL: pancakeswap_v3_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the PancakeSwap decentralized exchange. It specifically focuses on version 3 of the PancakeSwap protocol and uses events from the Binance Smart Chain blockchain. The table includes information about swap events and pool creation events in order to provide insights into trading activity on PancakeSwap.

MODEL: dex_base_trades.sql

🟠 Modified by:

🔧 PR: #4940, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: A reference to the dex_polygon_base_trades model was added. A common table expression (CTE) named base_union was also added, which selects all columns from an unspecified table.

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: The main logic of the changes is that a base_union CTE (Common Table Expression) was added to the SQL model. The CTE selects all columns from an existing table called base_union.

MODEL: pancakeswap_v2_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table that combines data from PancakeSwap v2 trades and the PancakeSwap v2 MMPool. It includes information such as blockchain, project, version, block number and time, token amounts bought and sold, addresses of tokens bought and sold, taker and maker addresses, project contract address,and transaction hash. This enables data analysts to analyze trading activity on PancakeSwap v2 including volume traded by token pairs.

MODEL: pancakeswap_v3_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4921, Add pancakeswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze trades on the PancakeSwap platform. It specifically focuses on version 3 of the PancakeSwap protocol in the Ethereum blockchain. The table is populated with data from two sources: 'PancakeV3Pool_evt_Swap' and 'PancakeV3Factory_evt_PoolCreated'.

MODEL: shibaswap_v1_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4925, Add shibaswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the Shibaswap project on the Ethereum blockchain. It uses two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', to gather the necessary data for analysis.

MODEL: balancer_v2_arbitrum_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer protocol version 2 on the Arbitrum blockchain. It enables data analysts to analyze and query trade data specific to this version of the Balancer protocol on Arbitrum.

MODEL: dex_avalanche_c_base_trades.sql

🟠 Modified by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: In this diff, a new reference to the model 'balancer_v2_avalanche_c_base_trades' was added. This reference is included in a list of other models that are being referenced. The rest of the code remains unchanged.

MODEL: balancer_v2_avalanche_c_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer project version 2 on the Avalanche blockchain. It enables data analysts to analyze and query trade data specific to this version of Balancer on Avalanche.

MODEL: balancer_v2_base_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that enables data analysts to analyze trades on the Balancer protocol version 2 in the base blockchain.

MODEL: dex_trades_beta.sql

🟠 Modified by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: The diff of the SQL model shows that two models, 'tokens_erc20_model' and 'prices_model', were added. The 'tokens_erc20_model' is referenced from another model called 'tokens_erc20'. The 'prices_model' is sourced from a table named 'prices' with a column named 'usd'.

MODEL: balancer_v1_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v1_trades' that stores trade data from the Balancer project on the Ethereum blockchain. It enables data analysts to analyze and query trade information specifically for version 1 of the Balancer protocol.

MODEL: balancer_v2_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that enables data analysts to analyze trades on the Balancer protocol version 2 in the Ethereum blockchain.

MODEL: balancer_v2_gnosis_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer project version 2 on the Gnosis blockchain. It enables data analysts to analyze and query trade data specific to this version of Balancer.

MODEL: dex_optimism_base_trades.sql

🟠 Modified by:

🔧 PR: #4932, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: The model added a reference to 'balancer_v2_optimism_base_trades' in addition to the existing references to 'sushiswap_v1_optimism_base_trades', 'sushiswap_v2_optimism_base_trades', and 'zipswap_optimism_base_trades'.

🔧 PR: #4932, Add zipswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-12
📝 Summary: The model added a reference to 'zipswap_optimism_base_trades' in addition to the existing references to 'mummy_finance_optimism_base_trades', 'sushiswap_v1_optimism_base_trades', and 'sushiswap_v2_optimism_base_trades'. The rest of the code remains unchanged.

MODEL: balancer_v2_optimism_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer protocol version 2 on the Optimism blockchain. It enables data analysts to analyze and query trade data specific to this version of the Balancer protocol.

MODEL: balancer_v2_polygon_base_trades.sql

🟢 Added by:

🔧 PR: #4940, Add balancer to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-13
📝 Summary: This SQL model creates a table called 'balancer_compatible_v2_trades' that is compatible with the Balancer protocol version 2 on the Polygon blockchain. It enables data analysts to analyze and query trade data specific to the Balancer project on Polygon.

MODEL: contracts_contract_creator_address_list.sql

🟠 Modified by:

🔧 PR: #4887, [EASY]Adding new addresses to contract_creator_list
🧙 Author: @chuxinh on 2023-12-12
📝 Summary: In this SQL model, several addresses and corresponding names are added to the 'curated_list' CTE. The addresses and names include 'Candide', 'Etherspot', 'ZeroDev' (twice). These additions expand the curated list of addresses in the model.

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: [changes too large] The model contracts_contract_creator_address_list.sql was modified.

MODEL: apeswap_bnb_base_trades.sql

🟢 Added by:

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Apeswap project in the Binance Smart Chain (bnb). It includes information from two sources: 'ApePair_evt_Swap' and 'ApeFactory_evt_PairCreated'.

MODEL: apeswap_ethereum_base_trades.sql

🟢 Added by:

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Apeswap platform in Ethereum. It sources data from two events: 'ApePair_evt_Swap' and 'ApeFactory_evt_PairCreated'.

MODEL: apeswap_polygon_base_trades.sql

🟢 Added by:

🔧 PR: #4866, Add apeswap_*_base_trades
🧙 Author: @Hosuke on 2023-12-12
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Apeswap project in the Polygon blockchain. It sources data from two events, 'ApePair_evt_Swap' and 'ApeFactory_evt_PairCreated'.

MODEL: contracts_contract_overrides.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: In this SQL model, a new contract label for 'OpenSea' with the address 0x00005EA00Ac477B1030CE78506496e8C2dE24bf5 and name 'SeaDrop 1.0' was added.

MODEL: contracts_project_name_mappings.sql

🟠 Modified by:

🔧 PR: #4887, Static Contract Metadata Updates
🧙 Author: @MSilb7 on 2023-12-12
📝 Summary: In this SQL model, two rows were added to the temporary table. The first row represents a mapping for 'synthetix_futuresmarket' with the name 'Synthetix', and the second row represents a mapping for 'synapsefees' with the name 'Synapse'.

MODEL: zipswap_optimism_base_trades.sql

🟢 Added by:

🔧 PR: #4932, Add zipswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-12
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze trades on the Uniswap V2 protocol. The trades are specific to the Optimism blockchain and the Zipswap project, version 1. The data sources used for this analysis are 'UniswapV2Pair_evt_Swap' from the 'zipswap_optimism' source and 'UniswapV2Factory_evt_PairCreated' also from the same source.

MODEL: spiritswap_fantom_base_trades.sql

🟢 Added by:

🔧 PR: #4931, Add spiritswap to dex.trades_beta
🧙 Author: @tomfutago on 2023-12-12
📝 Summary: This dbt SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query trade events from the Spiritswap project on the Fantom blockchain. It uses two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', to gather the necessary data for analysis.

SECTOR: chainlink

toggle to see all model updates

MODEL: chainlink_arbitrum_ccip_admin_meta.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table that includes the blockchain name, admin address, and operator name for various entities. It enables data analysts to easily access and analyze information related to different blockchain operators.

MODEL: chainlink_arbitrum_ccip_fulfilled_transactions.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a view called 'ccip_fulfilled_transactions' that combines data from the 'arbitrum' database and the 'chainlink_arbitrum_ccip_send_traces' table. It calculates various metrics such as token amount and USD amount for each transaction, grouping them by hash, index, and sender address. The final query selects specific columns from this view to display information about blockchain transactions in Arbitrum.

MODEL: chainlink_arbitrum_ccip_gas_daily.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table called 'ccip_gas_daily' that calculates daily gas usage metrics for the Arbitrum blockchain. It includes data such as fulfilled and reverted token amounts, USD amounts, total token amount, and total USD amount. The model also joins this data with operator metadata from another table called 'chainlink_arbitrum_ccip_operator_meta'. This enables data analysts to analyze gas usage trends on the Arbitrum blockchain by date, node address, and operator name.

MODEL: chainlink_arbitrum_ccip_nop_paid_logs.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a query that retrieves data from the 'arbitrum' blockchain logs table. It selects various columns including block hash, contract address, data, topics, transaction hash and more. It also applies some transformations to extract specific information from the data column. The query filters the results based on a specific topic0 value related to NopPaid events. This model enables analysts to analyze and gain insights from Arbitrum blockchain logs specifically for NopPaid events.

MODEL: chainlink_arbitrum_ccip_nop_reward_daily.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table that calculates the daily rewards in USD for operators on the Arbitrum blockchain. It retrieves data from two tables, 'link_usd_daily' and 'nop_paid', and joins them to calculate the USD amount based on token amounts. The resulting table includes columns for blockchain, date start, date month, operator name, NOP address, token amount, and USD amount. This model enables data analysts to analyze daily rewards earned by operators on Arbitrum in terms of both tokens and USD value.

MODEL: chainlink_arbitrum_ccip_operator_meta.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table that includes the blockchain name, node address, and operator name for various nodes. It enables data analysts to easily access and analyze information about different nodes in the specified blockchains.

MODEL: chainlink_arbitrum_ccip_request_daily.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table called 'ccip_request_daily' that provides daily metrics for fulfilled, reverted, and total requests on the Arbitrum blockchain. It calculates these metrics by joining data from two tables: 'chainlink_arbitrum_ccip_fulfilled_transactions' and 'chainlink_arbitrum_ccip_reverted_transactions'. The model also includes an optional incremental mode that filters the data based on a specified interval. The resulting table includes columns for blockchain type, start date of each day, month of each day's start date, and the request counts.

MODEL: chainlink_arbitrum_ccip_reverted_transactions.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table that combines data from multiple sources to provide information on reverted transactions in the Arbitrum blockchain. It includes details such as the block time, date month, node address, token amount, USD amount, and transaction hash for each reverted transaction. This model enables data analysts to analyze and understand the impact of reverted transactions in Arbitrum.

MODEL: chainlink_arbitrum_ccip_reward_daily.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a table that calculates daily and monthly rewards in token and USD amounts for a specific blockchain. It joins data from two tables, one containing token metadata and the other containing price data. The model also includes an optional incremental feature to only calculate rewards for recent dates. The resulting table includes columns for the blockchain name, start date, month date, token amount, USD amount, and token symbol.

MODEL: chainlink_arbitrum_ccip_send_requested.sql

🟢 Added by:

🔧 PR: #4926, Chainlink CCIP Metrics
🧙 Author: @AnonJon on 2023-12-15
📝 Summary: This SQL model creates a query that retrieves various aggregated data from multiple tables. It enables data analysts to analyze blockchain transactions related to the Chainlink Arbitrum CCIP protocol, including information such as the blockchain used, block time, fee amount in a specific token, destination chain selector and destination blockchain. The query also includes conditions for filtering the results based on token contracts and locked tokens. The final result is grouped by transaction hash.

MODEL: [chainlink_arbitrum_ccip_send_requested_daily