# LSteak FAQ

Quick answers, no hype.

New here? Start with [Start here](/lsteak-protocol-docs/overview/start-here.md).

Start with the overview: [LSteak Front Facing Explainer](/lsteak-protocol-docs/overview/lsteak-explainer.md).\
Use the full spec: [LSteak Whitepaper v2.2](/lsteak-protocol-docs/lsteak-whitepaper-v2.2/overview.md).

### Key terms

* **LSTEAK**: The liquid token.
* **Backing**: Assets held by the protocol’s yield engine (yield-generating bonds + a diversified hedge).
* **BPT (Backing Per Token)**: Backing divided by effective supply. This is an internal accounting metric.
* **Effective supply**: The supply used in backing math (excludes protocol-owned non-circulating balances and any non-redeemable accounting-only representations).
* **POL (Protocol-Owned Liquidity)**: Liquidity owned by the protocol.
* **xl-LSTEAK**: Optional long-term accumulation / exit layer for LSTEAK.
* **RR (Redemption Ratio)**: LSTEAK redeemable per unit of xl-LSTEAK. Under normal operation, it cannot decrease.
* **LSaaS**: Isolated deployments of the same mechanics for partner tokens.

### Basics

<details>

<summary>What is LSteak?</summary>

LSteak is a liquid staking system that grows value without printing new tokens.

Each LSTEAK represents a proportional claim on protocol backing.\
New tokens are only minted when new backing value is added.

</details>

<details>

<summary>How is LSteak different from other liquid staking tokens?</summary>

Most liquid staking systems pay rewards by inflating supply.

LSteak does not. Rewards come only from real value the protocol earns.

</details>

<details>

<summary>Does LSteak use emissions or rebasing?</summary>

No. There are no emissions and no rebasing.

Balances change only when you choose to interact.

</details>

<details>

<summary>If balances don’t rebase, how do I benefit?</summary>

You benefit through **value density**, not automatic balance increases.

Backing can grow from yield. Effective supply can shrink from burns.\
Both raise BPT over time, which can support higher market value per token.

</details>

<details>

<summary>Where does the yield come from?</summary>

Yield comes from the protocol’s backing assets, not token inflation.

The primary source is **Bernard Bonds (DexFi)**, which earns yield from real market activity (trading fees + liquidity management) across a diversified CLP vault portfolio.\
A secondary hedge (BTC / ETH / XAUT) is used to reduce drawdowns and smooth backing volatility.

No emissions. No “printed yield”.

</details>

<details>

<summary>How is yield allocated?</summary>

Yield is routed through fixed minimum “sinks” before anything discretionary.

Minimum allocations:

* **Backing (BPT) increase**: ≥ 30%
* **xl-LSTEAK RR increase**: ≥ 25%
* **Protocol-Owned Liquidity (POL)**: ≥ 10%
* **Supply reduction (burn)**: ≥ 5%
* **Treasury**: fixed 5%

Up to 25% can be policy-controlled, but it is still bounded by guardrails.\
Full details are in [Yield Sources and Allocation Logic](/lsteak-protocol-docs/lsteak-whitepaper-v2.2/6.-yield-sources-and-allocation-logic.md).

</details>

### Price, internal value, and market conditions

<details>

<summary>Is LSTEAK pegged to a price?</summary>

No. Market price is allowed to move freely.

The system does not defend a peg.

</details>

<details>

<summary>If price can move, what does the system actually track?</summary>

Internally, LSteak tracks **Backing Per Token (BPT)**.

BPT measures how much backing supports each unit of effective supply.\
It is not a redeemable price.

</details>

<details>

<summary>How is BPT calculated?</summary>

At a high level:

**BPT = Backing ÷ Effective supply**

Backing is the protocol’s backing assets.\
Effective supply is the supply used for backing math.

</details>

<details>

<summary>What is “effective supply” and why not use total supply?</summary>

Effective supply is the portion of supply that should count in backing math.

It excludes specific balances that are not economically “circulating claims.”\
This avoids double-counting and keeps BPT meaningful.

</details>

<details>

<summary>What happens if markets are quiet or boring?</summary>

Quiet markets aren’t a problem.

When inflows slow, value accrues across a more stable effective supply.\
Value per token can grow faster.

</details>

<details>

<summary>What happens when markets are volatile?</summary>

The protocol follows fixed rules that respond automatically.

If price is low, discounted tokens can be absorbed and supply pressure can reduce.\
If price is high, reserves and liquidity can be strengthened.

</details>

<details>

<summary>Can the rules change during a crash?</summary>

No. Core rules cannot be changed quickly.

They cannot be overridden during market stress.

</details>

### Exiting and redemption

<details>

<summary>Can I redeem LSTEAK for the backing assets?</summary>

No. Backing is not redeemable during normal operation.

This prevents “bank-run” style backing drains.

</details>

<details>

<summary>How do I exit LSTEAK?</summary>

You exit by selling LSTEAK through available liquidity venues.

Price and slippage depend on market conditions.\
There is no protocol redemption to a fixed value.

</details>

### xl-LSTEAK (optional long-term layer)

<details>

<summary>What is xl-LSTEAK?</summary>

xl-LSTEAK is an optional long-term version of LSTEAK.

Each xl-LSTEAK can always be redeemed for LSTEAK.\
Over time, it redeems for the same or more LSTEAK. Never less.

</details>

<details>

<summary>Can xl-LSTEAK ever go backwards?</summary>

Under normal operation, no. The redemption rate (RR) can stay the same or increase.

It cannot decrease outside liquidation scenarios.

</details>

<details>

<summary>Is xl-LSTEAK a price guarantee?</summary>

No. It guarantees token accumulation.

It does not guarantee a market price.

</details>

<details>

<summary>Who should use xl-LSTEAK?</summary>

People who want certainty over excitement.

It is designed for long-term participation, not trading.

</details>

### LSaaS (partner deployments)

<details>

<summary>What is LSaaS?</summary>

LSaaS lets other projects use LSteak’s mechanics while staying fully isolated.

A partner’s failure cannot affect LSteak or other partners.

</details>

<details>

<summary>Do I need to understand LSaaS to use LSteak?</summary>

No. LSaaS is separate.

It is an advanced system.

</details>

### Governance and emergency controls

<details>

<summary>Who controls LSteak?</summary>

Governance powers are intentionally limited.

Changes are delayed and constrained. No one can override core rules.

</details>

<details>

<summary>Is there an emergency shutdown?</summary>

Yes, but only for catastrophic failures like exploits.

Market conditions alone are not a trigger.

</details>

<details>

<summary>What happens if the system cannot recover?</summary>

Assets are distributed fairly and mechanically.

There is no discretion and no preferential treatment.

</details>

### Fit and expectations

<details>

<summary>Who is LSteak for?</summary>

LSteak is for people who want a system that:

* still makes sense in bad markets
* does not depend on hype
* does not change rules under pressure
* prioritizes durability over excitement

</details>

<details>

<summary>Who is LSteak not for?</summary>

* Day traders
* Leverage seekers
* Yield chasers
* Anyone who needs constant excitement

</details>

<details>

<summary>What risks should I understand?</summary>

LSteak removes emissions risk.

It does not remove market risk.

Key risks:

* **Price volatility**: LSTEAK is not pegged.
* **Liquidity and slippage**: exit quality varies by market conditions.
* **Smart contract risk**: on-chain code can fail or be exploited.
* **Strategy/backing risk**: backing performance can vary across regimes.

</details>

<details>

<summary>What is the simplest way to describe LSteak?</summary>

A liquid staking system that quietly compounds value.

It is designed not to break when markets stop cooperating.

</details>


---

# 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/overview/lsteak-faq.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.