> For the complete documentation index, see [llms.txt](https://docs.smoothy.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smoothy.finance/introduction/background.md).

# Introduction

Due to the explosive growth of DeFi, multiple assets were introduced into the Ethereum network as anchor coins, such as BTC, USD, and GOLD. At present, there are more than 20 asset-backed tokens in the current market, multiple among which are backed by the same assets. In the future, more tokens that are effectively backed by the same underlying assets are expected to be introduced into the network. Theoretically, the swap ratio between these tokens should be 1:1 given that they are effectively backed by the same underlying assets. However, for the current DEX in the market, this fundamental point was not fully considered when designing the exchange protocol, thereby causing unnecessary high costs for users because of the slippage. Thus, a better-designed product that specializes in the assets that are effectively backed by the same underlying assets is urgently needed in the market.

Curve.fi and mStable are the two representative products that are dedicated to swapping tokens effectively backed by the same underlying assets (such as stablecoins). Curve.fi uses StableSwap protocol utilizing an invariant as a combination of constant-product (Uniswap) and constant-sum invariants.  It achieves great success by providing low-slippage swap compared to Uniswap.  However, due to the mathematical complication of StableSwap curves, a pool in curve.fi supports only up to 4 assets - meaning that to support more assets, it has to open more pools (10+ pools) with some assets spreading over multiple pools (such as DAI, USDC).  The disperse of the asset in multiple pools greatly reduces liquidity and thus increases slippage.

![A list of stablecoin pools in Curve.fi.](https://lh3.googleusercontent.com/Kd0Um3TC5lsMFRpDNZw5rieLwqQyRHbqELaCQeH8i8i77n4EkLA8-BRqK9t2INKKUQQHCWY8t1XTccDNYxOIUjJZcBpIMIdVrU1YwUmrj-ATHKKOfCjC17o444vcgSHwMHEpKTc)

mStable offers a single pool solution and offers 1:1 swap as long as the percentages of the tokens are below the predefined weights.  However, it lacks flexibility, where a swap is prohibited a percentage of token exceeds a predefined weight.  Further, it incurs a high cost for swapping mainly because of the high gas fee by withdrawing/depositing tokens in the underlying interest-earning protocols (Compound/AAVE).

![An example of percentage and weight of each token in mStable.](https://lh6.googleusercontent.com/ef44ZyVBlilaCULAQJT2Qt9UCsavCQer-WqKBainVEtsJivaYcKVYTniZYrC-mSPRq5DVZFLMmJ6rZ15AgRZ14LIQSWi5ROIkopBkDdWsU_8Sks2BrddCnHOkbD5_fGWhFkD6-Y)

Smoothy has been developed from scratch to address the issues of existing protocols.  Smoothy's goal is to offer one pool to swap all tokens with

* Simple and smooth swap
* Extremely low gas fee
* Flexibility to add/remove any stablecoins
* Better liquidity/lower slippage and better LP token incentives


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.smoothy.finance/introduction/background.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.