-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rebase with upstream main #3
Conversation
Add pool name to extensions
Add CreateVToken event
Fix/inflation fee v3
Add support for pragma twaps
Update debt_caps to be pair specific
Skip pair collateralization check if max_ltv == 0
vendor::erc20::{IERC20MetadataDispatcher, IERC20MetadataDispatcherTrait}, | ||
vendor::erc20::{ERC20ABIDispatcher as IERC20Dispatcher, ERC20ABIDispatcherTrait}, units::INFLATION_FEE, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reverted back to ERC20ABIDispatcher because that is already now used for token approvals.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing there weren't any conflicts so I'm optimistically approving.
Yes! I will open a PR against the main repo to check the CI. |
The Ekubo tests are passing locally. There is just one thing to highlight in the comment below. We can open the PR against the upstream once this is merged.
In the earlier PR, I suggested:
Thinking about this again today, I think it might not be an issue. Let's say the quote asset is USDC, collateral asset is USDC, and borrow asset is STRK. Assuming the threshold for STRK is 80%, then even though the price of 1 USDC is always 1 USDC, but we can still liquidate this position if STRK's price > 0.8 USDC. Maybe we can do away with this requirement first, and raise it in the upstream PR?