> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/use-cases/balances-that-earn.md).

# Balances that earn while they wait

**For:** wallets, exchanges and stablecoin payment apps.

## The problem

Apps that hold stablecoins keep large balances that do nothing between deposits and payments.

## How it works

1. The app connects its idle stablecoin balances to the [Yield Engine](/modules/yield-engine.md).
2. The balances earn while they sit, and stay available for spending through the [Treasury](/modules/treasury-engine.md) and [Settlement](/modules/settlement-engine.md) modules.
3. The app chooses who keeps the earnings: the app, its users, or both.

## Modules used

Yield, Treasury, Settlement.

## Things to know

* Earnings are variable and can be zero. The strategy can lose money.
* The app stays responsible for what it tells its own users and for the rules that apply to it.

## Status

In development.


---

# 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.zirodelta.com/use-cases/balances-that-earn.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.