# nToken Returns

nTokens provide all the liquidity to Notional's liquidity pools. This means that nTokens are the counterparty to all fixed rate lends and borrows on Notional's liquidity pools. When a user borrows fixed, nTokens lend fixed. When a user lends fixed, nTokens borrow fixed.&#x20;

In return for providing liquidity to Notional's fixed rate liquidity pools, nTokens earn returns in three ways:

* **Interest accrual:** nTokens hold their cash in Prime Cash, and they earn interest from their Prime Cash. nTokens also hold fCash positions which earn interest if the fCash position is positive, or pay interest if the position is negative.
* **Transaction Fees:** nTokens [earn a fee](/notional-v3/trading-fcash/transaction-fees.md) anytime an end user borrows or lends. Transaction fee returns are driven by volume - the more borrowing and lending, the more fees generated.
* **NOTE Incentives:** nToken holders are directly incentivized with Notional’s governance token, the NOTE. nToken holders accrue NOTE rewards proportional to their share of the total nTokens.

### Returns example

Here is an example breakdown of return drivers for nUSDC.

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

In this example, most of the nUSDC cash is held in Prime USDC which is earning 1.44% APY. nUSDC also has net fCash positions in each maturity. It has a net lending position in the March maturity earning 4.981%, and it has small net borrowing positions in June and December.&#x20;

The total interest accrual APY in this example is 2.077%. Trading fees are earning 0.201% APY and NOTE incentives are earning 15.354% APY.


---

# 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.notional.finance/notional-v3/ntokens/ntoken-returns.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.
