Future schema upgrades

[this-username-is-taken]

• Add strategy entity and harvest events to yield aggregators.
• Add underlying tokens to input tokens in yield aggregators.
• Add more reward token types (in Aave-v3, reward emissions are per token: aToken/stableDebtToken/variableDebtToken).
• Add gas-related data to all events
• Tracking slippage in swaps
• Include both borrower position and lender position in Liquidate entity in lending subgraphs: https://github.com/messari/subgraphs/pull/686#discussion_r934097812
• convert pricePerShare to BigInt

[steegecs]

• Add number of days or hours since unix timestamp as a field for entities that concatenate them to some prefix in the id (i.e. LiquidityPoolDailySnapshots).

[melotik]

• Lending protocol: add positionCounts to snapshots (market/usage)

[tnkrxyz]

Make these two fields of the Market entity in the lending protocol optional, outputToken is already optional.

• outputTokenSupply
• outputTokenPriceUSD

[steegecs]

Yield Aggregatort

• outputTokenSupply is not required in the Vault entity but required in the Vault snapshots
• UsageMetricsDaily snapshot has totalPoolCount but the hourly snapshot does not. Do we want to consider changing the interface to remove this value and add totalVaultCount to the YieldAggregator type? Then keep totalPoolCount in the LiquidityPool type.

[melotik]

• transaction counts on a market-level
• user/unique user counts on market-level

[melotik]

• add a field at the protocol level called "protocol" to store the name without any versions. ie, "aave" instead of "aave-v2"

[melotik]

yield ags

• specify if withdraw.amount / amountUSD should include withdrawal fee if applicable.
• In that light we should also include a new optional field withdraw.feesUSD

Based on convo with @bye43

[this-username-is-taken]

add oracle to lending protocols

[this-username-is-taken]

add aggregated token data info in dex subgraphs (similar to uniswap)

[melotik]

Consider allowing multiple input tokens in lending protocols. For the case of Compound V3 markets

[melotik]

Consider having rewards on the protocol level. In the case of TrueFi that is what is happening. @corerouter feel free to add any other comments or notes on this front! Thanks for bringing it up

[melotik]

How can we show variable vs stable debt in lending positions? prolly by separating the two into different positions, but we need schema changes to allow for this i think

[steegecs]

• For DEXs, does it make sense to have from and to fields in the swaps? A user should always be swapping with a pool, though, they may interact with a Router as a proxy. So I am thinking about removing from and to and just having user, pool, and maybe router in the case of swaps. I think this is more clear.

[melotik]

Should positiion.liquidationCount increment when collateral is transferred to the liquidator, and specify this in schema.

[melotik]

Consider adding an asset field to the position entity. In the case of abracadabra the borrows are always in MIM no matter what market you are in. Without this the whale watcher data app will have to have unique logic for abracadabra.

[steegecs]

• Are schema and protocol type one to one? If not, should we consider adding schema into the protocol entity?

[tnkrxyz]

Rename PositionSide.LENDER to PositionSide.Collateral or Depositor in extended lending schema? Protocols like makerdao do not lend collaterals (only DAI); it is a bit odd to call them the lender side.

[tnkrxyz]

Make the liquidate.position field a list in the extended lending schema, because multiple positions will be changed by a liquidation (lender and borrower side).

[melotik]

Integrate flash loans into lenfing schema. Otherwise a new schema for it. Could make for some cool data apps 😉

[melotik]

How do we classify position token (ie, aToken / cToken) transfer? Should this be a new position, should it count as a withdraw / deposit?

[this-username-is-taken]

How do we classify position token (ie, aToken / cToken) transfer? Should this be a new position, should it count as a withdraw / deposit?

That's correct. These is a fairly long discussion on this in the Discord if you try searching through

[melotik]

use immutable where possible per #964

[melotik]

Add native token balances where possible, this would include borrow balances in native unit. Per discussion with @yulesa (feel free to add more detail if necessary here)

• add borrow balance in markets in native amounts
• add daily snapshot amounts in native amount, ie. native borrows/day /hour deposits etc.

[yulesa]

Let me give examples of where this is useful. Imagine you're analyzing a pool and it's TVL went down, but that's only beacuse the price tanked, in native terms the pool is only went up. Native terms remove price fluctuations but you can't combine different pools.

[melotik]

yeild ags should have isActive on the vaults, beefy finance has deprecated vaults for example

[this-username-is-taken]

Add entity count to make fetching large number of paginated entities easier (instead of blindly fetching until the end of pagination)