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

# Supply assets

Supplying an asset to Vena deposits it into a shared pool and starts accruing interest. The supply balance grows in real time as interest compounds.

## Supply flow

<figure><img src="https://2045251926-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlGhMLUzgZnHbEcM0Hi8R%2Fuploads%2FF2BKorJ3sx0SAtFZtTNC%2Fimage.png?alt=media&amp;token=bb790f6e-e670-441c-8d6f-7267980459f2" alt=""><figcaption></figcaption></figure>

1. Open the Vena dapp and connect your wallet. See [Connect your wallet](/for-users/connect-wallet.md).
2. From the **Markets** view, click **Supply** next to the asset to supply.

<figure><img src="https://2045251926-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlGhMLUzgZnHbEcM0Hi8R%2Fuploads%2FPn8ZwncbZlNoL3W0TXyL%2Fimage.png?alt=media&amp;token=48861bf3-7e1c-44d8-976f-051db4391e01" alt=""><figcaption></figcaption></figure>

3. Enter an amount. The **Transaction Overview** shows the projected Supply APY and the asset's collateralisation status.
4. Approve the token spend (first time per asset) and confirm the supply transaction.

Once confirmed, the supply balance appears on the dashboard. Interest compounds continuously.

## Understanding your APY

The rate shown for a supplied asset includes multiple streams:

| Component             | What it is                                                                                                                                   |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Base supply APY**   | Interest paid by borrowers of the asset, varying with pool utilisation                                                                       |
| **$BLEND incentives** | Rewards distributed via Merkl on eligible markets. See [$BLEND incentives](/points-and-incentives/blend-incentives.md)                       |
| **Vena Points**       | Vena's internal points, accruing while a position is open. See [Earning Vena Points](/points-and-incentives/earning-vena-points.md)          |
| **Partner points**    | Third-party programs on eligible markets, set and claimed by each partner. See [Overview](/points-and-incentives/overview.md#partner-points) |

Base supply APY moves with utilisation: as more of the supplied pool is borrowed, the rate rises. $BLEND, Vena Points, and partner points accrue independently and don't replace or reduce the base rate — they stack on top.

## Enable as collateral

Supplied assets count as collateral by default on every market. Each reserve page shows a **Collateral usage** flag in Supply Info — `Can be collateral` means the asset is eligible.

See [Parameter reference](/asset-parameters/parameter-reference.md) for per-asset collateral flags.

## Withdraw

Supplied assets can be withdrawn to the wallet at any time, subject to two conditions:

* **Pool liquidity.** If most of the supplied pool is out on loan, withdrawals may be partial or delayed until borrowers repay. This is unusual but can happen at high utilisation.
* **Health factor.** If the supply is in use as collateral for an open borrow, withdrawing reduces collateral and lowers the health factor. Vena blocks withdrawals that would push the health factor below 1.

To withdraw:

1. From the dashboard, click **Withdraw** next to the supplied asset.
2. Enter an amount (or **Max**) and confirm.


---

# 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://docs.vena.finance/for-users/supply-assets.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.
