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.
Closes: #132
OracleAggregator
Requirements
Design draft: The following sections outline ideas that are still being designed.
Aggregate price
To avoid the complexity of calculating a median, we instead use a trimmed mean: removing the maximum and minimum values to protect against "oracle jitter."
Oracle spread
A Pessimistic Relative Spread calculation is used. This measures the distance between the most extreme values in the oracles ($Price_{max}$ and $Price_{min}$ ) relative to the lowest value.
A price set is considered Coherent only if the calculated spread is within the configured tolerance ($\tau$ ):
Short-term volatility
The oracle maintains a ring buffer of the last
naggregated prices with timestamps,respecting
minTimeDeltaandmaxTimeDelta.Prices are collected on calls to
price().If multiple updates occur within the same
minTimeDelta, only the most recent price is retained.The pessimistic relative price move is:
The price history is considered Stable only if the move is below the configured
maximum allowed move.