# 6. Yield Sources and Allocation Logic

[Back to whitepaper overview](/lsteak-protocol-docs/lsteak-whitepaper-v2.2/overview.md)

LSteak’s yield does not come from token emissions or inflationary mechanics. It is generated from productive assets and distributed according to fixed rules that prioritize long‑term system health.

### 6.1 Primary Yield Source: Bernard Bonds (DexFi)

The primary yield engine of LSteak is Bernard Bonds, a white-label implementation of DexFi Treasury Bonds.

Bernard Bonds routes capital into a widely diversified portfolio of concentrated‑liquidity positions, managed through DexFi’s advanced AI-driven Liquidity Management (AiLM) vault system. This portfolio spans 60+ independent CLP vaults (and growing), rather than relying on a single yield source.

Yield generated by Bernard Bonds comes from real market activity — trading fees, range optimisation, and liquidity efficiency — not token inflation or emissions.

This structure provides:

* Broad diversification across vaults and strategies
* Reduced dependence on any single market or asset
* Historically resilient yield across bull, bear, and sideways regimes

Crucially, Bernard Bond yield exists independently of LSTEAK token demand and does not require continuous inflows to remain productive.

### 6.2 Secondary Stabiliser: The Hedge

Alongside bonds, LSteak maintains a diversified hedge composed of BTC, ETH, and XAUT.

The hedge is not designed to outperform bonds in all conditions.

It exists to:

* Reduce drawdowns during adverse markets
* Smooth backing volatility
* Preserve value density during extended sideways periods

Hedge composition follows predefined market-mode weightings and is adjusted only through new allocations, not active rebalancing.

### 6.3 Yield Allocation Priorities

All bond-generated yield is allocated through a bounded, deterministic framework.

These allocations must sum to 100% and respect minimum thresholds:

* Backing (BPT) Increase: ≥ 30%
* xl-LSTEAK Redemption Ratio Increase: ≥ 25%
* Protocol-Owned Liquidity (POL): ≥ 10%
* Supply Reduction (Burn): ≥ 5%
* Treasury: fixed 5%

The remaining allocation (up to 25%) is policy-controlled, but still bounded by the same guardrails and sinks.

This structure ensures that yield simultaneously strengthens backing, improves exit quality, deepens liquidity, and funds protocol operations.

### 6.4 Treasury Handling and System Reinforcement

Treasury inflows are processed through a priority handler:

1. Debt repayment and operating costs
2. Savings/runway accumulation
3. Excess routing (policy‑controlled)

When enabled, excess treasury inflows may be routed into backing growth, POL expansion, or additional burns.

### 6.5 Yield Without Growth Dependence

Yield distribution does not assume continuous inflows.

When new capital enters the system, backing and supply expand proportionally. When inflows slow, yield concentrates on a stable supply base, accelerating BPT and redemption‑ratio growth.


---

# 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://lsteak-protocol.gitbook.io/lsteak-protocol-docs/lsteak-whitepaper-v2.2/6.-yield-sources-and-allocation-logic.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.