-
Notifications
You must be signed in to change notification settings - Fork 1
Use interest filler #41
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
Conversation
Ryang-21
left a comment
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.
Couple questions but looks good otherwise
| APP_CONFIG.interestFillerAddress !== undefined && | ||
| APP_CONFIG.interestFillerAddress !== '' && | ||
| auctionBid.auctionEntry.auction_type == AuctionType.Interest && | ||
| fill.percent === 100 |
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.
is there a reason to fill using the interest filler contract when its a 100 percent fill?
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.
yep, still allows us to fill with USDC directly. Also prevents sim/fill block difference from causing failures
| try { | ||
| logger.info( | ||
| `Scanning ${users.length} users for liquidations in pool: ${poolConfig.poolAddress}` | ||
| ); | ||
| } catch (e) { | ||
| const errorLog = `Error scanning for liquidations: ${poolConfig.poolAddress}\nError: ${e}`; | ||
| logger.error(errorLog); | ||
| sendNotification(errorLog); | ||
| } |
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.
This try catch meant to be around the logging?
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.
no, thx for catching
No description provided.