miguelmtz
miguelmtz
@The-3D basically on-hold since this contract was about to be rebuilt. Anycase, good to have in mind for the new version of it I assume
Agree with the second point. This requirement has caused some issues for integrators where users positions are aggregated into one single account.
> good to know. I am curious why you would disagree with the first point though :) I assume was initially designed to prevent free loans of 1 block duration,...
@IoanSolovastru Last version of aave core in npm is 1.13.1 You can check the available versions here: https://www.npmjs.com/package/@aave/core-v3
@jkrivine How would you give allowance to someone to withdraw on your behalf?
Thanks for the issue @patitonar . The actual backed amount by the `backUnbacked` call could be calculated taking the before and after `unbacked` amounts of the reserve. However, I agree...
Trafeoffs of this approach: - The price check is only made in 1 single asset (the borrowed asset on borrow, the debt asset on liquidation) - The price fetch is...
Alternative: create a keeper function at `PriceOracleSentinel` that checks price stability of all the reserves. ``` function keeper() external { address[] memory reserveList = IPool(ADDRESSES_PROVIDER.getPool()).getReservesList(); uint256 i = 0; uint256...
> I think it makes more sense to enable separately after the reserve is added - this would be consistent with making something borrowable, or enabled as collateral. > >...