You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Align single-asset join portion of joinPoolSharesInternal with all-asset portion (update error messages, variable names, and error return value)
Update error message for max stableswap numAssets (currently says 2 instead of 8)
Add comment to maxIterations that says to keep above 256 for it to converge
(Code hygiene) JoinPool error check
(Code hygiene) Move exit pool state update into updatePoolLiquidityForExit
New error message to be used in validateScalingFactors
Validate pool liquidity after reordering in scaledSortedPoolReserves
(Code hygiene) Use p.GetTotalPoolLiquidity() instead of raw p.PoolLiquidity in getLiquidityIndexMap
Update cfmmConstantMultiNoV comment to reflect that we no longer use v term
(Code hygiene) Switch uses of vSumSquares to wSumSquares in cfmmConstantMulti and cfmmConstantMultiNoV
Ensure calculated output leads to valid pool state in SwapOutAmtGivenIn
Locally defined pool update function in calcSingleAssetJoinShares uses tokenIn instead of its passed in newLiquidity parameter (which is remains unused)
Add "purpose" line under each function in report as docs
The text was updated successfully, but these errors were encountered:
Full Report: https://hackmd.io/juU2yglrRTyYJKJF2Tt8Pw
This tracking issue covers the list of issues that came up during our end-to-end internal review of the stableswap package in preparation for v13.
Release blocking (safety issues):
No safety risk but either completeness issue or odd behavior:
Minor/code hygiene:
joinPoolSharesInternal
with all-asset portion (update error messages, variable names, and error return value)maxIterations
that says to keep above 256 for it to convergeupdatePoolLiquidityForExit
validateScalingFactors
scaledSortedPoolReserves
p.GetTotalPoolLiquidity()
instead of rawp.PoolLiquidity
ingetLiquidityIndexMap
cfmmConstantMultiNoV
comment to reflect that we no longer usev
termvSumSquares
towSumSquares
incfmmConstantMulti
andcfmmConstantMultiNoV
SwapOutAmtGivenIn
calcSingleAssetJoinShares
usestokenIn
instead of its passed innewLiquidity
parameter (which is remains unused)The text was updated successfully, but these errors were encountered: