-
Notifications
You must be signed in to change notification settings - Fork 609
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
[stableswap]: Add max pool asset check to ValidateBasic() #2860
Comments
@AlpinYukseloglu As I read in the description, we don't allow pool with 3 assets right? |
I don't see why we wouldn't? Anything between 2 and the cap we set is fair game, although I think we should hold off on this until we finish bounding the rest of stableswap inputs and come to a conclusion on a reasonable maxNumAssets |
Alright I got a little misunderstanding here. We don't have a conclusion about the specific cap yet, right? |
Yes we haven't finalized it yet! It will come down to a number of factors tied to current open issues/PRs (not a major decision just one I'd prefer not to spend too much time reverting/changing) |
Closes: #2860 ## What is the purpose of the change > Add max pool asset check to ValidateBasic() > Add tests to check the new condition
Background
Even with scaling factors and increased decimal precision, we still need to have a cap on the number of assets we can support in multi-asset pools.
This number should be somewhere between 4 and 8 assets per multi-asset pool and can be enforced by adding checks at pool creation. The simplest check we can add is in ValidateBasic(), although we should enforce this at lower levels as well as a guardrail.
Suggested Design
Acceptance Criteria
The text was updated successfully, but these errors were encountered: