security: order route checks before effects#139
Open
webmirroring wants to merge 1 commit into
Open
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
compute_route_feeso registered-pair, amount bounds, liquidity sufficiency, and cooldown checks all pass before route state is written or events are emitted.PairLiquidity, pair route count, pair volume, last-route timestamp,liq_usedevents, androuteevents are unchanged.SECURITY.md.Closes #128.
Security notes
The cooldown guard now runs in the read-only CHECKS phase, before liquidity debit, counter/timestamp updates, and
liq_used/routeemission. A route rejected byRouteCooldownActivedoes not leak observable route business effects.Validation
cargo fmt -- --checkpassesgit diff --checkpassescargo test test_cooldown_blocked_route_has_no_business_side_effects -- --nocaptureis blocked locally before project compilation because the available Cargo is 1.84.0 and cannot parsebase64ct v1.8.3's edition2024 manifest: