📰 2024-02-02: Weekly Prophet! #5284
andrewhong5297
announced in
Prophet (Weekly Updates)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is your weekly summary of 17 PRs merged from 12 wizards. Great job everyone! 🎉
We had 22 added models 🟢 and 742 modified models 🟠 for 190 Sectors.
SECTOR: dex
toggle to see all model updates
MODEL: dex_info.sql
🟠 Modified by:
🔧 PR: #5177, Added woofi , kyberswap and velocimeter dexes on base
🧙 Author: @Jason4276 on 2024-01-26
📝 Summary: In the given SQL model, a new row has been added to the temporary table. The row represents a project named 'Velocimeter' with corresponding values for name, marketplace_type, and x_username.
🔧 PR: #5177, Added chainhop optimism dexes
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: The model added a new row to the existing list of values. The new row represents a platform called 'ChainHop' with the attributes 'Direct' and 'ChainHopDEX'.
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: In this diff, the model is being updated to add three new rows and remove one row. The rows being added are for 'oasisswap', 'smardex', and 'swaap'. The row being removed is for 'smardex'.
MODEL: dex_prices.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the model 'dex_trades' is being modified. The LEFT JOIN condition is changed from joining with a reference model 'tokens_erc20' to joining with a source named 'tokens' and schema named 'erc20'. Additionally, the join condition is updated to match on the token_sold_address column instead of token_bought_address. The WHERE clause remains unchanged, filtering for records where amount_usd > 0.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v1_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In the given diff of the dbt SQL model, a change was made in the JOIN statement. The previous join reference
ref('tokens_ethereum_erc20')
was replaced withsource('tokens_ethereum', 'erc20')
. This indicates that there was a modification in how the tokens from Ethereum ERC20 were being joined to the state_with_gaps table.MODEL: labels_balancer_v2_pools_arbitrum.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_pools_avalanche_c.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_pools_base.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_pools_ethereum.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this SQL model, a table called 'settings' is being created. The model includes a left join between the 'pools' table and the 'tokens_erc20' table (which was changed to use the source macro instead of ref). The selected columns from this join are p.symbol and p.pool_type, which are then assigned as pool_symbol and pool_type in the settings table.
MODEL: labels_balancer_v2_pools_gnosis.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_pools_optimism.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_pools_polygon.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_beethoven_x_pools_fantom.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this diff, the reference to the
tokens_erc20
table is replaced with a source calledtokens
and schema namederc20
. This change affects the left join in the SQL model. The rest of the code remains unchanged.MODEL: labels_balancer_v2_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_balancer_v2_sources.yml was renamed.
MODEL: labels_beethoven_x_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_beethoven_x_sources.yml was renamed.
MODEL: labels_op_attestationstation_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_op_attestationstation_sources.yml was renamed.
MODEL: labels_op_governance_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_op_governance_sources.yml was renamed.
MODEL: labels_op_bridge_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_op_bridge_sources.yml was renamed.
MODEL: labels_flashbots_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_flashbots_sources.yml was renamed.
MODEL: labels_op_nft_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_op_nft_sources.yml was renamed.
MODEL: labels_lens_poster_frequencies_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model labels_lens_poster_frequencies_sources.yml was renamed.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_optimism_erc20_stablecoins.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The main logic added in this SQL model is the change in the source reference. The previous inner join was referencing a dbt model named 'tokens_optimism_erc20', but it has been changed to reference a source named 'tokens_optimism' with schema 'erc20'. Additionally, there is a condition added to ensure that only tokens counted in TVL (Total Value Locked) are included.
MODEL: tokens_optimism_source.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model tokens_optimism_source.yml was renamed.
SECTOR: prices
toggle to see all model updates
MODEL: prices_arbitrum_tokens.sql
🟠 Modified by:
🔧 PR: #5273, Adding frxETH to prices_arbitrum_tokens.sql
🧙 Author: @discochuck on 2024-02-01
📝 Summary: The token symbols that were added are: frxETH The token symbols that were removed are: None
MODEL: prices_optimism_tokens_bridged.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The diff shows that the reference to
tokens_optimism_erc20_bridged_mapping
has been changed to a source calledtokens_optimism
with the aliaserc20_bridged_mapping
. The join condition remains the same, joining on the contract address between this source and another reference calledprices_ethereum_tokens
.MODEL: prices_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model prices_sources.yml was renamed.
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #5245, Drop another price token
🧙 Author: @aalan3 on 2024-01-29
📝 Summary: The token symbols that were added or removed are: GMT, TBTC
🔧 PR: #5245, Add GYD token to prices.usd
🧙 Author: @fmarrr on 2024-01-26
📝 Summary: The token symbols that were added or removed are: GYD
MODEL: prices_bnb_tokens.sql
🟠 Modified by:
🔧 PR: #5255, Drop token fuse
🧙 Author: @aalan3 on 2024-01-29
📝 Summary: The token symbols that were added or removed are: DOGE, COW, TIME, FUSE
MODEL: prices_avalanche_c_tokens.sql
🟠 Modified by:
🔧 PR: #5232, Update prices_avalanche_c_tokens.sql
🧙 Author: @chefcronje on 2024-01-26
📝 Summary: The token symbols that were added or removed are: EGS
SECTOR: _sector
toggle to see all model updates
MODEL: dex_base_base_trades.sql
🟠 Modified by:
🔧 PR: #5182, Added woofi , kyberswap and velocimeter dexes on base
🧙 Author: @Jason4276 on 2024-01-26
📝 Summary: In this diff, three references to existing tables (
rubicon_base_base_trades
,baseswap_base_base_trades
, andscale_base_base_trades
) were added. Additionally, three new references to tables (kyberswap_base_base_trades
, `woofi_MODEL: velocimeter_v2_base_base_trades.sql
🟢 Added by:
🔧 PR: #5182, Added woofi , kyberswap and velocimeter dexes on base
🧙 Author: @Jason4276 on 2024-01-26
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v2_trades' that enables data analysts to analyze and query Uniswap V2 trades. It pulls data from two sources, 'Pair_evt_Swap' and 'Factory_evt_PairCreated', in the basevelocimeter_base project on the blockchain.
MODEL: dex_trades_beta.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The main logic of the changes in this SQL model is that the reference to the 'tokens_erc20' model has been replaced with a source called 'tokens' and schema called 'erc20'. This change suggests that instead of referencing a pre-defined dbt model, data is now being sourced directly from an external database table or view.
MODEL: synthetix_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The main logic added in this SQL model is the replacement of a reference to a dbt source called 'tokens_erc20' with a new source called 'tokens' for the left joins. The join conditions remain the same, checking if the symbol matches and if blockchain is 'optimism'.
MODEL: lending_arbitrum_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models. For each model, it selects specific columns from the table and appends them to the result set using UNION ALL. The resulting query combines data from multiple tables into one unified output.
MODEL: lending_avalanche_c_base_borrow.sql
🟠 Modified by:
🔧 PR: #5244, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: This SQL model selects data from multiple tables (
aave_v2_avalanche_c_base_borrow
,aave_v3_avalanche_c_base_borrow
, andbenqi_avalanche_c_base_borrow
) using a union all operation. The selected columns include blockchain, project, version, transaction_type, loan_type, token_address, borrower, repayer,liquidator,
amount,
block_month,
block_time,
block_number,
tx_hash,and evt_index.
🔧 PR: #5244, Add benqi_finance to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: In this diff, a new reference to the model 'benqi_avalanche_c_base_borrow' was added.
MODEL: lending_base_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models. For each model, it selects specific columns from the table and appends them to the result set using UNION ALL. The resulting query combines data from multiple models into one unified output.
MODEL: lending_celo_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models. For each model, it selects various columns from the table specified by the model name. If there are more models to process, it appends a 'union all' statement to combine the results of all selected tables into one result set.
MODEL: lending_ethereum_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: This diff adds a SQL model that selects data from multiple tables using a union all operation. The model iterates over a list of models and selects specific columns from each table, including blockchain, project, version, transaction type, loan type, token address, borrower information (address), repayer information (address), liquidator information (address), amount of the transaction/loan repayment/liquidation etc., block month/year/time/number details for the transaction event index and hash.
MODEL: lending_fantom_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models. For each model, it selects various columns from the table specified by the model name. The selected columns include blockchain, project, version, transaction_type, loan_type, token_address, borrower,
repayer,
liquidator,
amount,
block_month,
block_time,
block_number,
tx_hash and evt_index.
If there are multiple models in the list of models being iterated over (except for the last one), it adds a 'union all' statement to combine the results of each select query into one result set.
MODEL: lending_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: This diff adds a SQL model that selects data from multiple tables using a union all statement. The model retrieves columns such as blockchain, project, version, transaction_type, loan_type, token_address and more from various lending tables. Each table is referenced using the ref() function and the resulting data is combined using the union all operator.
MODEL: lending_optimism_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models and performs a select statement on each model. The select statement retrieves various columns from the specified model, including blockchain, project, version, transaction_type, loan_type, token_address, borrower,
repayer,
liquidator,
amount,
block_month,
block_time,
block_number,
tx_hash,and evt_index. The results from each select statement are then combined using the union all operator.
MODEL: lending_polygon_base_borrow.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The added logic in this SQL model is a loop that iterates over a list of models. For each model, it selects various columns from the table specified by the model name. The selected columns include blockchain, project, version, transaction_type, loan_type, token_address, borrower,
repayer,
liquidator,
amount,
block_month,
block_time,
block_number,
tx_hash and evt_index.
The results from each iteration are combined using UNION ALL to create a single result set.
MODEL: element_avalanche_c_events.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: In this SQL model, a new left join was added to the 'ava_erc20_tokens' table from the 'tokens' source. The previous left join with the 'tokens_erc20' table from a reference was removed. The rest of the logic remains unchanged, including joins with other tables and concatenation of columns to create a unique trade ID.
MODEL: zonic_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: The main logic added in this diff is the replacement of a reference to
tokens_erc20
with a source calledtokens
and schema callederc20
. This change filters the data from the source based on a condition where blockchain equals 'optimism'.MODEL: _sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model _sources.yml was renamed.
MODEL: quix_optimism_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model quix_optimism_sources.yml was renamed.
MODEL: balances_sources.yml
🟠 Modified by:
🔧 PR: #5260, Tokens Subproject
🧙 Author: @couralex6 on 2024-01-30
📝 Summary: [changes too large] The model balances_sources.yml was renamed.
MODEL: dex_optimism_base_trades.sql
🟠 Modified by:
🔧 PR: #5137, Added chainhop optimism dexes
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: In this diff, a reference to the model 'chainhop_optimism_base_trades' was added.
MODEL: chainhop_optimism_base_trades.sql
🟢 Added by:
🔧 PR: #5137, Added chainhop optimism dexes
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: This SQL model creates a table that combines trade data from the 'TransferSwapper_evt_DirectSwap' table in the 'chainhop_optimism' schema. It includes information such as block time, taker and maker addresses, token amounts bought and sold, contract addresses, transaction hashes, and more. This model enables data analysts to analyze trade activity on the Optimism blockchain for the Chainhop project.
MODEL: dex_arbitrum_base_trades.sql
🟠 Modified by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: In this diff, several references to different dbt SQL models were added. The models being referenced are 'apeswap_arbitrum_base_trades', 'oasisswap_arbitrum_base_trades', 'smardex_arbitrum_base_trades', 'swaap_v2_arbitrum_base_trades', and 'woofi_arbitrum_base_trades'. These references were added within a larger block of code that includes other model references.
MODEL: apeswap_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 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 Apeswap project on the Arbitrum blockchain. It sources data from two tables: 'ApePair_evt_Swap' for swap events and 'ApeFactory_evt_PairCreated' for pair creation events.
MODEL: oasisswap_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 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 OasisSwap decentralized exchange on the Arbitrum blockchain. It sources data from two tables: 'OasisSwapPair_evt_Swap' for swap events and 'OasisSwapFactory_evt_PairCreated' for pair creation events.
MODEL: smardex_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: This SQL model creates a table called 'uniswap_compatible_v3_trades' that enables data analysts to analyze and query trade data from the Smardex project on the Arbitrum blockchain. The table includes columns for taker, maker, pair, and other optional information related to trades.
MODEL: swaap_v2_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: This SQL model creates a table that extracts data from the 'Vault_evt_Swap' table in the 'swaap_v2_arbitrum' database. It selects specific columns and renames them, and also adds additional columns like blockchain, project, version, block_month, block_date. This model enables data analysts to analyze swap events on the Swaap platform in Arbitrum by providing relevant information such as token amounts bought/sold, addresses involved in the transaction, contract details etc.
MODEL: woofi_arbitrum_base_trades.sql
🟢 Added by:
🔧 PR: #5177, Added Apeswap, OasisSwap, Swaap_v2, Woofi, Smardex to dex.trades
🧙 Author: @ARDev097 on 2024-01-26
📝 Summary: This SQL model creates a table that extracts data from the 'woofi_swap_arbitrum' source. It includes information such as block number, block time, token amounts, addresses of tokens bought and sold, taker and maker addresses, project contract address, transaction hash and event index. This model enables data analysts to analyze trading activity on the Arbitrum blockchain for the Woofi project.
MODEL: lending_avalanche_c_base_supply.sql
🟠 Modified by:
🔧 PR: #5244, Add benqi_finance to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: In this diff, a new reference to the model 'benqi_avalanche_c_base_supply' was added.
MODEL: lending_zksync_base_borrow.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This dbt SQL model creates a union of data from the 'zerolend_zksync_base_borrow' table. It selects various columns related to blockchain transactions, including blockchain type, project details, transaction type, loan type, token address, borrower and repayer information. Additionally it includes details such as liquidator info and amount involved in the transaction. The model also provides block-related information like month of the block creation along with its time stamp and number. Finally it includes transaction hash and event index for each record in the resulting dataset.
MODEL: zerolend_zksync_base_borrow.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_borrow' that is compatible with the Aave v3 lending protocol. It specifies the blockchain as 'zksync', project as 'zerolend', version as '1', and project_decoded_as as 'zerolend'. This model enables data analysts to analyze borrowing data from the ZeroLend project on the ZkSync blockchain using Aave v3 compatibility.
MODEL: lending_zksync_base_flashloans.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This SQL model creates a union of data from the 'zerolend_zksync_base_flashloans' table. It selects various columns related to blockchain transactions such as blockchain, project, version, recipient, amount, fee, token address and more. This model enables data analysts to analyze and query information about flash loans in the ZeroLend ZkSync base.
MODEL: zerolend_zksync_base_flashloans.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_flashloans' that is compatible with Aave v3 flash loans on the Zksync blockchain. It enables data analysts to analyze and work with flash loan data from the ZeroLend project, version 1.
MODEL: lending_base_supply.sql
🟠 Modified by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: In this diff, the model is updated to include a new reference to 'lending_zksync_base_supply' while removing the reference to 'lending_gnosis_base_supply'.
MODEL: lending_zksync_base_supply.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This SQL model creates a union of data from the 'zerolend_zksync_base_supply' table. It selects various columns related to blockchain transactions such as blockchain, project, version, transaction type, token address, depositor information, withdrawal details and more. This model enables data analysts to analyze and query this combined dataset for further analysis or reporting purposes.
MODEL: zerolend_zksync_base_supply.sql
🟢 Added by:
🔧 PR: #5242, Add zerolend (zksync) to lending
🧙 Author: @tomfutago on 2024-01-26
📝 Summary: This SQL model creates a table called 'lending_aave_v3_compatible_supply' that is compatible with Aave v3 lending protocol. It enables data analysts to analyze and track the supply of assets on the Zksync blockchain for the ZeroLend project. The version and project details are also included in this model.
SECTOR: basemax_finance
toggle to see all model updates
MODEL: basemax_finance_base_perpetual_trades.sql
🟢 Added by:
🔧 PR: #5225, Added basemax_finance, xena_finance, mummy_finance, voodoo_trade, bmx and meridian to perpetual_trades
🧙 Author: @ARDev097 on 2024-01-31
📝 Summary: This SQL model creates a table that combines data from multiple sources to track trading events in the 'basemax_finance' project. It includes information such as block time, trade type, trader, volume, fee, margin, and transaction details. The model enables data analysts to analyze and understand the trading activity within the project.
SECTOR: [
Beta Was this translation helpful? Give feedback.
All reactions