Skip to content
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

Add liquidation kick support to bots #492

Open
4 tasks
yghazi opened this issue Oct 10, 2022 · 2 comments
Open
4 tasks

Add liquidation kick support to bots #492

yghazi opened this issue Oct 10, 2022 · 2 comments

Comments

@yghazi
Copy link
Contributor

yghazi commented Oct 10, 2022

Goal

Add liquidation kick support to bots, such that it will bark at under collateralized urns automatically instead of waiting for the Bark event.

Context

I need to create a keeper that will a, initiate liquidations and b, participate in said liquidations (with or without arbitrage opportunities). I've been looking at other keepers and this one seems like a good fit. Well-maintained, as it is. If there is such a keeper out of the box, I'd like to know.

Assets

bots

Tasks

  • Design
  • Develop
  • Test
  • Release
@LukSteib
Copy link
Contributor

hey @yghazi,
thanks for opening the issue.

The current keeper implementation supports detection and participation in collateral (flip), surplus (flap) and debt (flop) auctions. Auction initialisation (aka kicking of underwater vaults) is not yet included in the feature-set.
In case you want to test auction participation of your keeper instance you can
a) do so on goerli where there are auctions that just need to be restarted
b) run one of our auction simulations on a hardhat fork and test your keeper instance there

We've recently extended the UI with the functionality to kick underwater vaults (see: https://unified-auctions.makerdao.com/vaults?network=mainnet). So will definitely take a look into extending the keeper functionality in the similar direction and keep you posted.

In case you have any related questions, feel free to raise them here in the issue.

@yghazi
Copy link
Contributor Author

yghazi commented Oct 11, 2022

Appreciate the help. I'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants