You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once users are able to deploy their own vaults, we will need to update the home page. We will still show the official pitch lake deployed vaults, but will also show the vaults the user has deployed (and/or favorited).
Pt 2
Now there will be multiple vaults that are deployed, so we should consider adding some logic for sorting/filtering. There still needs to be discussion for filtering which Vaults our indexer will monitor (unless the goal is to constantly track every single vault deployed from the factory).
We might consider only monitoring vaults deployed using our factory and impose restrictions for the factory:
Can only deploy if k is within specific bounds
Can only deploy if a is within specific bounds
Can only deploy for a “fee” (the fee for us to constantly monitor this vault with our services) (maybe)
After we know which vaults we will be showing on the home page, we should should add sorting and filtering. These might include:
Sort by highest/lowest k
Filter X <= k ≤ Y
Can sort by either k as a percentage or the strike price of the current rounds
Sort by highest/lowest a
Filter X <= a <= y
Filter based on current round’s state (Open | Auctioning | Running)
Sort by highest/lowest current round’s cap level
Can sort by either cap as a percentage or the actual capped price of the current round
Sort by most/least rounds
Sort by highest/lowest TVL
Etc.
The text was updated successfully, but these errors were encountered:
Refer #89
Pt 1
Once users are able to deploy their own vaults, we will need to update the home page. We will still show the official pitch lake deployed vaults, but will also show the vaults the user has deployed (and/or favorited).
Pt 2
Now there will be multiple vaults that are deployed, so we should consider adding some logic for sorting/filtering. There still needs to be discussion for filtering which Vaults our indexer will monitor (unless the goal is to constantly track every single vault deployed from the factory).
k
is within specific boundsa
is within specific boundsAfter we know which vaults we will be showing on the home page, we should should add sorting and filtering. These might include:
k
X <= k ≤ Y
a
X <= a <= y
The text was updated successfully, but these errors were encountered: