-
Notifications
You must be signed in to change notification settings - Fork 9
fix: harden proxy view fee previews #446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
carrion256
wants to merge
4
commits into
audit/fee-anchor-lifecycle-spec
from
audit/fee-preview-and-proxy-view-truthfulness
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a5d52bb
fix: report proxy fee growth cap (#FIND-085 Nexus 86ddc60c-b4d9-4e2e-…
carrion256 4978611
fix: check proxy fee snapshot conversions (#FIND-077 Nexus 082f9cb2-f…
carrion256 dcb55f2
fix: bound proxy max deposit and mint by conversion headroom (#FIND-0…
carrion256 3118c26
fix: fail fee previews on supply overflow (#FIND-080 Nexus 4460259b-1…
carrion256 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the fee config has no
max_total_assets_growth_rate(the default uncapped mode), this maps it to0, which is indistinguishable from a configuredSome(Wad::zero()). Those two states are materially different becausetotal_assets_for_fee_accrualtreatsNoneas uncapped growth butSome(0)as no growth beyond the anchor, and governance currently acceptsSome(0). Downstream consumers of the new fee snapshot cannot reconstruct the actual fee policy and may simulate fee accrual incorrectly; return a presence flag/optional encoding or another unambiguous sentinel instead of collapsingNoneto zero.Useful? React with 👍 / 👎.