fix(perps): enforce stale oracle gate on liquidation#138
Draft
rndrntwrk wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR fixes the stale-oracle liquidation bypass in the EVM perps engines. Liquidation now uses the same max-oracle-delay gate as normal perps oracle sync instead of entering a special liquidation context that allowed stale-but-still-oracle-readable prices.
Security invariant
A liquidation must not execute from an oracle price older than the market engine maxOracleDelay, even if the underlying SkillOracle has a longer max delay.
Changes
Validation
Notes
Draft until owner/security review is complete. This branch targets main as the effective PR path; the same commit will be replayed into enoomian staging separately for deployment testing.