-
Notifications
You must be signed in to change notification settings - Fork 305
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
auction: TxV/TxP
support to populate the views
#4219
Comments
## Describe your changes This PR: - adds an action plan for withdrawing DA auctions - plugs in `GasCost` and `IsAction` impls - add basic TxV/TxP support/definitions ## Issue ticket number and link Part of #4212 + #4219 ## Checklist before requesting a review - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > Consensus breaking
All the scaffolding exists to make this happen, we just need to connect do the plumbing so that the views get populated. This is somewhat lower priority, but if anyone wants to pick it up feel free to. |
## Describe your changes This PR adds `ActionDutchAuctionScheduleView` and `ActionDutchAuctionWithdrawView` to the `ActionView` message, it also replaces the `IsAction` perspective impls with concrete implementation. Populating a view for the withdraw action without extending the `TxP` structure has proven squirrelly, and it will require a follow-up, although the data is "here" in the view server so I don't think it will be too complicated. ## Issue ticket number and link Part of #4219 ## Checklist before requesting a review - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > Breaking changes are made to `ActionView`: the `action_dutch_auction_schedule` and `action_dutch_auction_withdraw` fields have had their types changes from `ActionDutchAuctionSchedule` and `ActionDutchAuctionWithdraw` to `ActionDutchAuctionScheduleView` and `ActionDutchAuctionWithdrawView`, respectively.
We stubbed the withdraw view, this needs some addition to transaction perspectives, so leaving this open, until I replace it with a more detailed plan of action. |
Shelved for now, this turns out to be a bit more subtle than we realized, and also requires a bit of a different processing scheme than other views. Basically, unlike other views, we need access to the historical value of the auction reserves at the time the withdrawal happens, which is unlike how the rest of the view services are designed. We could add this in the future with the addition of an event for withdrawing actions, and then indexing those events to populate the view of withdrawal actions appropriately. |
This will make it easy to fill in withdrawal views later, since we'll have an event with the exact state of the auction at that time. ## Describe your changes This adds a new proto event for when an auction is withdrawn, including the state of the auction at that time. ## Issue ticket number and link This can be seen as laying the groundwork for #4219 once we're able to link events in the view services we implement. ## Checklist before requesting a review - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > This just adds a new event, without changing existing protos.
As of
v0.75.0
, there's not enough data in the currentTransactionPerspective
s to generateActionDutchAuctionWithdrawView
s that are useful to clients. The view exists but its content is hardcoded to have zero reserves and no positions. Instead, we should record extended metadata during scanning so that it's possible to cross-reference openings to note commitments with auction reserves. This also offers an opportunity to lay the groundwork so that we can add position views.The text was updated successfully, but these errors were encountered: