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

[Bug]: With new mark price methodology some configurations allow mtm to happen without protective price monitoring auction being triggered #10402

Closed
gordsport opened this issue Jan 15, 2024 · 1 comment

Comments

@gordsport
Copy link
Contributor

gordsport commented Jan 15, 2024

Problem encountered

With the current mark-to-market methodology mark price only ever gets updated after triggers for price monitoring auctions are evaluated. In particular a large move in mark price is guaranteed to not happen unless it triggered a price monitoring auction first (which may result in a different mark price - and one that is more “appropriate”). In particular people holding positions were protected against large price swings caused e.g. by trader or algorithmic errors submitting completely spurious orders that would lead to a trade outside the price monitoring bounds.
New mark price methodology allows various different ways of setting up the mark price; some of the allowed configurations do not need trades to update mark price which means that there may be mark price updates outside the price monitoring bounds under some market configurations.
A suggested solution is offered in this spec pull request which may or may not be incorporated into vega core in future releases under the following issue

Software version affected

0.74.0

@gordsport gordsport added the bug label Jan 15, 2024
@gordsport gordsport self-assigned this Jan 15, 2024
@gordsport gordsport added this to the 🌌 Nebula milestone Jan 15, 2024
@gordsport gordsport moved this to Todo in Core Kanban Jan 15, 2024
@github-project-automation github-project-automation bot moved this to Known Issues in Known Issues Board Jan 15, 2024
@gordsport gordsport removed their assignment Jan 24, 2024
@gordsport
Copy link
Contributor Author

Closing as a duplicate of: #10392

@gordsport gordsport closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
@github-project-automation github-project-automation bot moved this from Todo to Merged in Core Kanban Jan 31, 2024
@github-project-automation github-project-automation bot moved this from Known Issues to In Testing in Known Issues Board Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Status: In Testing
Development

No branches or pull requests

1 participant