> For the complete documentation index, see [llms.txt](https://fxprotocol.gitbook.io/fx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fxprotocol.gitbook.io/fx-docs/more/f-x-protocol-1.0/leverage.md).

# Leverage

### **Where Does the Leverage Come From?**

Leverage in f(x) Protocol originates from the innovative design of fTokens and xTokens, which split the price volatility of BaseTokens into stable and leveraged components. This allows users to balance between stability and risk, creating flexible investment strategies.

### Key Features

**fTokens (e.g., fETH, fxUSD, btcUSD):**

* Fully decentralized and native to Ethereum, Bitcoin, and Convex ecosystems.
* Minimize volatility while maintaining slight market exposure (0% volatility for most fTokens, except fETH at 10%).
* Support instant creation and trading to meet stablecoin demands.

**xTokens (e.g., xETH, xeETH, xwBTC):**

* Perpetual long tokens for ETH, BTC, and CVX with built-in leverage.
* Fully on-chain, composable, and highly liquid.
* Offer low liquidation risk, providing a safer alternative for leveraged positions.

### **How It Works**

#### Depositing BaseTokens:

* Users deposit BaseTokens (e.g., wBTC for btcUSD and xwBTC) into the protocol.

#### Splitting Price Volatility:

The protocol splits the price volatility of collateral into two components:

* fTokens: Absorb no market volatility (0% allocation, except 10% for fETH).
* xTokens: Amplify leverage (100% allocation, except 90% for xETH).

#### Diversified Exposure:

* This split enables users to diversify BaseToken exposure by balancing between stability (fTokens) and leverage (xTokens).

#### Minting and Redemption Fees:

* fTokens: 0–0.25% fee.
* xTokens: 1.5–2.5% fee.
* Users can avoid these fees by trading tokens on secondary markets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://fxprotocol.gitbook.io/fx-docs/more/f-x-protocol-1.0/leverage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.