-
Notifications
You must be signed in to change notification settings - Fork 66
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
refactor(blue): use single oracle #202
Conversation
Rubilmax
commented
Jul 31, 2023
- Fixes Use only one oracle #197
16110ff
@Rubilmax to update |
1a3bb68
I think that we should not expect the scale as an output of the oracle and rather should choose a coherent fixed scale. Yes, there can always be a well chosen asset pair that are unusable given a fixed scale. But it's still not worth the added complexity in Blue and oracles to me. To verify but 10e36 feels largely enough (the decimal difference is below 18 99% of the time, and if the price ratio is above 10e-14 you still have 0.01% precision). Edit:
actually it does not really complexifies the code, but more the framework and the work required to do an oracle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that we agree on this ⬆️
Let's postpone this choice |
Signed-off-by: Romain Milon <[email protected]>
5bbbe77