Closed gkaracha closed 3 years ago
A few ideas to start with:
Also, we probably need to be able to find all slices / last slice sent to the auction queue, originating from a given burrow. Otherwise I don't know how would we be able to call entrypoint_cancel_liquidation_slice
.
As far as I can tell, our current view exposes all basic information for interacting with the current liquidation auction:
val view_current_liquidation_auction_details: (unit * checker) -> view_current_liquidation_auction_details_result
type view_current_liquidation_auction_details_result =
{ auction_id: liquidation_auction_id
; collateral: tok
; minimum_bid: kit
; current_bid: bid option
; remaining_blocks: Ligo.int option
; remaining_seconds: Ligo.int option
}
So, I think we can close this one.
The only thing that is missing now is a view for identifying slices whose liquidation can be cancelled (see my comment above), but that is not for participants in liquidation auctions, but rather for burrow owners. Let's open a separate issue for that (still low priority).
Perhaps the Web UI will not offer functionality around liquidation auctions, but I think we could (and perhaps should) offer some off-chain views to assist users interacting with liquidation auctions. Let's discuss ideas about views that might be useful for users in this issue.