> For the complete documentation index, see [llms.txt](https://xave-finance.gitbook.io/general/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xave-finance.gitbook.io/general/product-overview/fxpools/pool-operator-faqs.md).

# Pool Operator FAQs

### Why doesn't my FXPool rebalance to a 50:50 LP ratio?

FXPools don't need to stay at the 50:50 ratio in order to offer FX rates. In practice, an FXPool facilitates FX accurate trades anywhere between the 24:76 and 74:26 ratios. This conceptually is a different design compared to constant product or constant sum invariants where the market expects the "true price" to be at the 50:50 ratio or elsewhere, however FXPools operate in a *range* rather than a single point on the price curve.

### Will my FXPool rebalance automatically or should I rebalance it manually?

<figure><img src="/files/MWFoVHTKmduB9KFZMNTz" alt=""><figcaption></figcaption></figure>

FXPools are designed to amplify arbitrage incentives beyond the beta region (outside the blue region, segments I:H and J:K). This means that the further traders bring the LP ratio beyond the beta region (currently 24:76 or 76:24 at the time of writing), they will be charged a dynamically increasing fee (or "penalty"). However, if a trader brings the LP ratio back towards the beta region, they will be paid a subsidy for helping to rebalance the pool (taken from the pool liquidity). The penalty will always be higher than the subsidy paid, so the pool will always remain solvent while earning increased fees for LPs.&#x20;

To see this "rebalancing" behavior in action, refer to some historical charts of a few of our FXPools that have been live since the start of 2023.&#x20;

<figure><img src="/files/Cn2OPeBN600odRd4Cj6P" alt=""><figcaption><p>VCHF:USDC Avalanche LP Ratio Over Time: <a href="https://dune.com/xavefinance/vchf-usdc-pool-avalanche">https://dune.com/xavefinance/vchf-usdc-pool-avalanche</a></p></figcaption></figure>

<figure><img src="/files/eepunNSyzwSgV8oUII3G" alt=""><figcaption><p>EURC:USDC Avalanche LP Ratio Over Time: <a href="https://dune.com/xavefinance/euroc-usdc-pool-avalanche">https://dune.com/xavefinance/euroc-usdc-pool-avalanche</a></p></figcaption></figure>

<figure><img src="/files/vRXNL8QYlHYsrCSZSRKK" alt=""><figcaption><p>EURS:USDC Ethereum LP Ratio Over Time: <a href="https://dune.com/xavefinance/eurs-usdc-pool-ethereum">https://dune.com/xavefinance/eurs-usdc-pool-ethereum</a></p></figcaption></figure>

{% hint style="info" %}
This rebalancing mechanic is of course not "magic" nor "instantaneous". The idea is that arbitrageurs will eventually find a profitable opportunity to either buy a token from the FXPool low and sell high elsewhere or vice versa
{% endhint %}

### Should I rebalance my FXPool when it goes beyond the 24:76 and 76:24 ratios?

We generally advise pool operators not to manually rebalance FXPools, unless absolutely required. Rather than manually rebalancing, we advise seeding liquidity between an FXPool and its' external pools to ensure that arbitrageurs are incentivized to carry out this "self rebalancing". As a pool operator, you may also consider running your own arbitrage bot to rebalance an FXPool, but make some money while doing it. This also helps to ensure that your FXPool remains attractive to traders.​​


---

# 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://xave-finance.gitbook.io/general/product-overview/fxpools/pool-operator-faqs.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.