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.
gm llama sirs,
a small update on the oracle section of Jupiter perps
Jupiter perps currently leverages their own oracle (built with Edge) to update prices and open/close positions
However, Jupiter perps still relies on Pyth oracle:
In other words, if e.g. Jupiter's oracle price deviates too much from the Pyth oracle, there will be no trades executed on their perps
This signifies that the Pyth oracle is still a critical part of the Jupiter perps infrastructure as a supporting oracle
https://station.jup.ag/guides/perpetual-exchange/how-it-works#oracle