fix(oracle): clamp upscaled price to uint32-safe bounds#311
Open
0xCardiE wants to merge 1 commit into
Open
Conversation
Cast before upscaling and clamp to [minimum, MAX] so currentPrice() cannot truncate or disagree with currentPriceUpScaled.
0xCardiE
added a commit
that referenced
this pull request
May 22, 2026
Move oracle clamp/cast fixes to #311; keep harness expectations aligned with master PriceOracle until that PR lands.
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
1 participant
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
uint64before upscaling insetPriceto avoid overflow/truncation when shifting.MAX_CURRENT_PRICE_UPSCALEDand_clampPriceUpscaledsocurrentPrice()cannot disagree withcurrentPriceUpScaledor under-report vsminimumPrice().Test plan
setPriceand round adjustment clamp to[minimumPriceUpscaled, MAX_CURRENT_PRICE_UPSCALED]currentPrice()matchescurrentPriceUpScaled >> 10at boundary values