add a failing test for planning add_liquidity on curve.fi #34
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.
While trying to port this code to python, I came across what I am pretty sure is a bug planning
add_liquidity
for 0xbEbc44782C7dB0a1A60Cb6fe97d0b483032FF1C7.Function signature:
add_liquidity(amounts: uint256[3], min_mint_amount: uint256)
It looks like it sees
uint256[3]
as a dynamic type, so it cuts the first 32 bytes off. Normally that would be the length, but since this type has a known size, that is actual data.I'm not sure what the right fix is.