-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Oracle API standardizations #1916
Comments
I copied in what was in the doc that we worked on. Happy to add more if needed. @Chris-Hibbert does this match what you have implemented in the call spread? |
I didn't have a timer in the call, and my result doesn't include a timeStamp in the PriceQuote. Those are easy enough to add. Otherwise, compatible. assetAmount can't default to 1 unit unless we have other mechanism for specifying the brand. |
For the priceQuote, the properties shouldn't be capitalized because they aren't keywords: |
Agreed. Let's not make it optional |
Also, the value must be an array if it's MathKind.SET |
I've updated the above API with the type definitions I understood from our conversation. Please update the issue description if you have changes, with a new comment to draw attention to them. |
Pivot the naming from 'asset' and 'price' to be more general ('amountIn', 'amountOut' and 'Quote'). |
Remove |
Update for |
Closed by #1952 |
What is the Problem Being Solved?
The oracle aggregator contract should present a standard API for querying aggregated prices without exposing the individual oracle identities or query parameters.
Description of the Design
Type declarations for the current design:
Security Considerations
Test Plan
The text was updated successfully, but these errors were encountered: