V13

[jonator]

• Closes v13: Support reduced OSMO swap fee #745
• Closes Stableswap #980

Testing

• Joining pool with multiple assets
• Swapping through weighted pool
• Swapping through stableswap pool (perhaps slippage setting needs to be higher)
• Multihop swap through OSMO pools, with fee discount (ION->FOO on swap page)
• Creating pool

[arispech]

• Joining pool with multiple assets
• Removing liquidity from pool
• Swapping through weighted pool
• Multihop swap through OSMO pools, with fee discount (ION->FOO on swap page)
  • ⚠️ Issue: FOO not available, not sure how to replicate multihop.
• Creating pool
• Creating stable pool
• Swapping through stableswap pool (perhaps slippage setting needs to be higher)

[delivan]

@jonator typescript can generate .d.ts file automatically when build .ts file. In tsconfig.json, remove "declarationDir": "./types" and build. Then .d.ts files are going to be generated. So I think we don't need to manage .d.ts manually.

[jonator]

@arispech

Multihop swap through OSMO pools, with fee discount (ION->FOO on swap page)

• ⚠️ Issue: FOO not available, not sure how to replicate multihop.

We should be able to use the create pool UI to create pools with IBC tokens that don't have an OSMO pair yet, and use that to test fee discount.

For multihop through stableswap pools, we can also use the create pool UI to create (low liquidity) stableswap pools for pairs that don't exist yet, then we can make sure they're included in the swap router (send me DM when pools are created).

Also, I've done brief testing on the OSMO swap fee discount, as well as multihop through stableswap pools, as well as swapping through individual pools. Did not run into issues (aside from slippage setting issues since the created pools were low liquidity).

[jonator]

@jonator typescript can generate .d.ts file automatically when build .ts file. In tsconfig.json, remove "declarationDir": "./types"and build. Then.d.tsfiles are going to be generated. So I think we don't need to manage.d.ts` manually.

Yeah I talked to dan and it seems the tradeoff is by publishing type files in packages, type defs are immediately available to the IDE after running yarn install, otherwise, yarn build needs to run first for language servers in IDEs to get type definitions. I agree though, this isn't worth it for complicated our fe devs committing process, and making PRs bigger. I'll remove types folders.