> 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/points-and-incentives/blend-incentives.md).

# $BLEND incentives

$BLEND is Fluent's native token. A portion of $BLEND emissions is directed to Vena users on eligible markets and distributed via Merkl. For most users on day one, $BLEND incentives are the largest dollar-value stream stacked on a position — they boost the effective APY on top of the base supply rate, or cut the effective cost on a subsidised borrow.

For $BLEND tokenomics and the network-wide emissions schedule, see the [Fluent docs](https://docs.fluent.xyz/).

## Month 1 allocation

Confirmed for Month 1: Vena's share of Fluent's $BLEND program is **1,500,000 $BLEND**, distributed over a **four-week window** starting **25 April 2026, 13:00 UTC**.

| Market | Action | $BLEND (Month 1) |
| ------ | ------ | ---------------- |
| sUSDnr | Supply | 450,000          |
| USDnr  | Supply | 750,000          |
| USDnr  | Borrow | 300,000          |

Per-market allocations for Month 2 and beyond are set by Fluent and are not yet final — see the [Fluent docs](https://docs.fluent.xyz/) for the network-wide schedule as it's published.

## Same-asset positions don't accrue rewards

Merkl nets your supply against your borrow on a per-asset basis. If you supply USDnr and borrow USDnr in the same wallet, the netted portion earns nothing on either side. Cross-asset loops (e.g., supplying sUSDnr to borrow USDnr) are unaffected — those are different reserves and accrue on both legs.

## How rewards accrue and are claimed

$BLEND rewards accrue continuously off-chain against on-chain aToken and debt-token balances. Merkl's engine snapshots those balances every two hours and pushes a new merkle root on-chain roughly every eight hours — rewards typically appear as claimable in the Merkl dashboard about eight hours after a position is opened.

To claim:

1. Navigate to [app.merkl.xyz](https://app.merkl.xyz/) and connect the same wallet that holds the Vena position.
2. Open the user dashboard at `app.merkl.xyz/users/{your-address}` to see accumulated rewards.
3. Claim all rewards on Fluent in a single batched transaction to save gas.

Claims are non-custodial — $BLEND is transferred directly to the connected wallet. Merkl rewards expire one year after they become claimable, so claim before then.

## Stacking with partner programs

When a partner protocol routes user capital into a Vena market, that capital earns Vena's $BLEND boost on the underlying supply market **in addition to** any incentives the partner runs on its own side. The routed deposit registers as a Vena supply balance for Merkl's snapshot, so the same capital earns on both surfaces — it's additive, not split.


---

# 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/points-and-incentives/blend-incentives.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.