liquidity accounting detector for solidity contracts - #116
Open
Jumongweb 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
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.
Closes #86
Summary
Add a dedicated AMM invariant, slippage, and liquidity accounting detector for Solidity contracts.
This change introduces a new AMM analysis pipeline with explicit rule IDs for:
reserve and balance drift
zero-liquidity initialization
fee ordering issues
rounding bias
donation-based invariant manipulation
slippage and deadline gaps
callback settlement omissions
flash-swap repayment validation gaps
invariant drift
low-liquidity boundary risk
What changed
Added AMM analysis types, config handling, and public exports in the core package
Implemented AMM model extraction and transition classification
Added deterministic AMM analyzer logic and serialization support
Added vulnerable and secure AMM fixtures for regression coverage
Wired the new detector into the public API surface
Validation
Targeted AMM regression tests were added and exercised
Secure AMM fixture remains clean
Vulnerable fixture is expected to trigger all AMM rule IDs, with the final invariant rule currently being tightened for the remaining red-path assertion