# ZilSwap V2.0

## Our Motivation

As the gateway to Zilliqa, ZilSwap will continue to evolve and cater to the needs of our users. The ZilSwap V2.0 will see new features while making use of the existing ZilSwap design system. The major upgrades will aim to achieve the following goals: 

1. Mitigate users' exposure to [**Impermanent Loss**](/how-to/provide-liquidity/impermanent-loss.md) risks through single-side liquidity 
2. Integrated new features requested by the community 
3. Create a stronger support for all liquidity pools 

## 2023 Roadmap

<table><thead><tr><th width="253">Feature</th><th>Details</th></tr></thead><tbody><tr><td><strong>Amplified Liquidity Pools</strong> <br><em>Less tokens needed for higher liquidity</em></td><td><ul><li>Addition of a <strong>Programmable Price Curve</strong> which enables liquidity pool creators to set a suitable price curve and create amplified pools in advance.</li><li>Achieve a <strong>much higher capital efficiency</strong> for providers and better slippage for users compared to AMMs.</li></ul></td></tr><tr><td><p><strong>Arbitrary Token Pairs</strong></p><p><em>Any ZRC2 token can be pooled directly with any other ZRC2 token</em><br></p></td><td><ul><li>Useful for liquidity providers as they can <strong>maintain more diverse ZRC2 token denominated positions</strong> (including tokens paired with stable assets).</li><li>If pool does not exist, a router contract can still be used to optimise between direct and multi-step swaps.</li><li>A <strong>whitelisting process</strong> will need to take place.</li></ul></td></tr><tr><td><strong>Dynamic Fees</strong><br><em>Trading fees are adjusted dynamically according to on-chain market conditions</em></td><td><ul><li>Dynamic fees will be introduced, where LP fees will be adjusted based on market conditions (such as trading volume and price volatility). This will entail an optimal potential return for liquidity providers.</li><li><strong>Higher earnings potential</strong> - In a volatile market (higher than usual volume), fees automatically increase to an optimal level, reducing the impact of impermanent loss. In periods of low volatility, fees decrease to encourage more trading and total fees collected.</li></ul></td></tr><tr><td><strong>Staking</strong><br><em>Earn $ZWAP rewards &#x26; voting power</em></td><td><ul><li><strong>Earn additional commission</strong> based on the amount of tokens locked relative to the weight of staking. The longer you lock your $ZWAP tokens, the more rewards you'll receive.</li><li>Vote locking entails voting power in governance, reward boosts and a portion of trading fees. </li></ul></td></tr><tr><td><strong>Rewards</strong><br><em>Real time reward distribution &#x26; claiming + community-driven reward distribution</em></td><td><ul><li><strong>Auto compounding</strong> — Real time distribution and claiming of rewards, eliminating epochs. </li><li><p><strong>Updated tracking and display</strong> of the following information:</p><ul><li>Pool contribution</li><li>Rewards accumulated</li><li>Expected Rewards</li><li>Entry/Exit Date</li></ul></li><li><strong>Community-driven LP rewards</strong> - Community members will be able to stake your LP tokens to receive rewards.</li></ul></td></tr><tr><td><strong>On-chain Price Oracle</strong></td><td><ul><li><strong>Fetch price information</strong> about any asset on our new highly decentralised and manipulation-resistant on-chain price oracles.</li></ul></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.zilswap.io/roadmap/zilswap-v2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.