Proposal: ensure symmetric ratios for orderbook #1766
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We want to avoid issues with asymmetric prices, ensuring we only work internally on-chain with symmetric prices.
This is a simple proposal to achieve this while maintaing the Oracle requirement:
How it works:
Order book will only look for ratios when the first currency argument is "less" than the second currency argument. It means the currency value compared by
PartialOrd
is less than the second one. If the asking price is the inverse, then orderbook will compute the reciprocal ratio. It means that feeders must feed using first the currency with "less" value in theConversionRatio(CurrencyId, CurrencyId)
type in order to be a valid ratio used in orderbook.Possible problems:
currency_a
<currency_b
?