You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain DeFi Protocols (e.g. Compound, Aave), let a user use their deposited assets as collateral in order to take out loans (borrow). The user must enable this on a per asset basis. Since there is thus a differentiation between deposited assets and deposited assets enabled as collateral, it would be nice if this information was exposed in the protocolBalances calls. Since this property isn't common across all protocols perhaps it would go into something like an extendedInformation property within the metadata for the token.
Certain DeFi Protocols (e.g. Compound, Aave), let a user use their deposited assets as collateral in order to take out loans (borrow). The user must enable this on a per asset basis. Since there is thus a differentiation between deposited assets and deposited assets enabled as collateral, it would be nice if this information was exposed in the protocolBalances calls. Since this property isn't common across all protocols perhaps it would go into something like an
extendedInformation
property within themetadata
for the token.As an example, here is one of the Aave methods that exposes this information: https://docs.aave.com/developers/developing-on-aave/the-protocol/lendingpool#getuserreservedata (see
usageAsCollateralEnabled
).The text was updated successfully, but these errors were encountered: