> For the complete documentation index, see [llms.txt](https://docs.lpeth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lpeth.xyz/overview/the-stake-wars.md).

# The Stake Wars

The amount of available liquidity for an LST/LRT is directly correlated to their market size. More liquidity is a significant signal, as there's more immediate exit capacity available, reducing risk. Building up sufficient liquidity as a new LST or LRT, or even maintaining your existing position in the liquidity market, is challenging and costly.

With lpETH, bootstrapping your own pools is a thing of the past. Protocols giving better bribes can receive lower fees or interest rates for their users versus their competitors. New LSTs/LRTs can tap into available liquidity without bootstrapping their own pools and bribe their way to success.

Equally, protocols could acquire their own governance tokens to vote on their fee gauges while remaining long-term aligned with the pool.  Ultimately, the amount of liquidity that can exist to service the LST/LRT market is finite. Protocols will have to find the most optimal ways to most efficiently provide liquidity for their user base, lpETH simplifies that.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lpeth.xyz/overview/the-stake-wars.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.