-
Notifications
You must be signed in to change notification settings - Fork 607
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
x/gamm: Add check to ensure JoinPoolNoSwap cannot be called with arbitrary denoms #1930
Conversation
LGTM once a test case is added |
Done! |
Awesome! Can you add a changelog entry under bug fix, and then merge this? |
Ready to merge! (not authorized to merge myself) |
Err can you fix your markdown editor locally, to not overwrite all the bulletpoints 😅 I'll commit to this branch to get this changelog change through |
This reverts commit fa33bf7.
Closes: #1929
What is the purpose of the change
Our current implementation of JoinPoolNoSwap only checks for whether the input set of tokens includes the tokens in the pool, but does not have any check that prevents someone from putting in an arbitrary number of arbitrary tokens. Since this is a no-swap/all-asset join, there are no other immediate checks so an invalid input can make it directly to the state-changing JoinPool function.
Brief Changelog
Testing and Verifying
This change is already covered by existing tests in our GAMM module
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? (no)