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.

Sign up for GitHub

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

feat: update AC FTCO-001 and 005 #2244

Merged
merged 4 commits into from
Apr 17, 2024
Merged

feat: update AC FTCO-001 and 005 #2244

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c6a9927
feat: update AC FTCO-001 and 005
Jiajia-Cui Apr 15, 2024
90ed3ce
feat: address comment
Jiajia-Cui Apr 17, 2024
98b6a81
feat: tidy up
Jiajia-Cui Apr 17, 2024
46d3cfd
Merge branch 'colosseo' into FTCO-005
Jiajia-Cui Apr 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions protocol/0065-FTCO-floating_point_consensus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,10 +94,12 @@ This section outlines floating-point quantities `vega` currently relies on:
- Up: 10%,
- Down: 10%.
- Upon market enactment risk factors get calculated (their values change from defaults).
- When the opening auction sees uncrossing price for the first time (there are two overlapping orders from buy and sell side on the order book) price monitoring bounds and probability of trading get calculated (their values change from defaults).
- When the opening auction ends (choose uncrossing price that's different from first indicative uncrossing price) price monitoring bounds and probability of trading get recalculated.
- When the market goes into price monitoring auction the state variables stay the same as prior to its' start, when that auction concludes (choose a price that's not been traded at before) price monitoring bounds and probability of trading get recalculated again and the time-based trigger countdown gets reset.
- When the time-based trigger elapses price monitoring bounds and probability of trading get recalculated.
- When the opening auction sees uncrossing price for the first time (there are two overlapping orders from buy and sell side on the order book) price monitoring bounds get calculated (their values change from defaults).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add that there may be a delay of a few blocks to this because it has to go via consensus.

- When the opening auction ends (choose uncrossing price that's different from first indicative uncrossing price) price monitoring bounds get recalculated.
- When the market goes into price monitoring auction the state variables stay the same as prior to its' start, when that auction concludes (choose a price that's not been traded at before) price monitoring bounds get recalculated again and the time-based trigger countdown gets reset.
- When the time-based trigger elapses price monitoring bounds get recalculated.
- When mark price is updated, probability of trading get recalculated.
- All of the recalculations on price monitoring bounds and probability of trading will happen with a possible delay of a few blocks because they have to go via consensus.

1. Event announcing diverging values gets emitted (<a name="0065-FTCO-004" href="#0065-FTCO-004">0065-FTCO-004</a>). For product spot: (<a name="0065-FTCO-006" href="#0065-FTCO-006">0065-FTCO-006</a>)
- For all the state variables nodes submit candidate values that differ by up to half the tolerance.
Expand Down
Loading