> For the complete documentation index, see [llms.txt](https://ample-2.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ample-2.gitbook.io/docs/research/why-ample.md).

# Why We Built Ample

Before Ample was a product, it was a question we couldn't put down.&#x20;

Why does saving money feel like nothing?

Run the numbers and the problem shows itself. A savings account paying 4% on a $1,000 balance produces about eleven cents a day.

$$\frac{$1{,}000 \times 0.04}{365} \approx $0.11 \text{ per day}$$

The experience is empty. \
\
Nobody opens an app to watch eleven cents arrive, nobody mentions it at dinner, and nobody saves more because of it. Interest works on a spreadsheet and disappears in a life.

Crypto's first answer was to make the number bigger, and in doing so it quietly swapped the product. Chasing yield onchain means strategies to evaluate, positions to manage, bridges to trust, and principal genuinely exposed to the trade. The returns may be more but it stops being saving. It becomes a hobby with drawdowns, and most people don't want a hobby. They want their money safe and their saving to feel like it's going somewhere.

So the world offers two defaults. Keep your principal safe and feel nothing, or chase returns and carry real risk plus a part-time job. The product that belongs between them, principal kept safe while the experience becomes worth having, mostly didn't exist.

It did exist in one place. Since 1956 the UK has run a savings product that pays no interest at all, pools what the interest would have been, and distributes it as monthly prizes. Twenty million people hold over £100 billion in it. The model, prize-linked savings, kept principal intact and made saving something people genuinely look forward to, for seventy years straight. The whole story is on the [next page](/docs/research/history.md).

<figure><img src="/files/ALOp8R75nppwGfpBW07m" alt=""><figcaption></figcaption></figure>

What kept that model from going global was never the idea.&#x20;

* Regulators treated private prize draws as lotteries, leaving the model to governments.&#x20;
* A decade of near-zero rates starved the prize fund of its raw material, since a $50M pool at 0.5% generates under $5,000 a week.&#x20;
* And prize economics need scale, while regional products start small, which kept every attempt local.

Onchain rails answer all three at once.&#x20;

* Lending markets generate real, programmable yield that pools itself. Stablecoins put the same dollar in every saver's hands worldwide, so the pool aggregates globally from day one.&#x20;
* And cryptographic proofs let a private operator demonstrate fairness instead of asking for faith in it, with draws committed onchain where no one can quietly rewrite them.

That intersection is **Ample**, the most proven savings mechanism of the last century running on the first rails that can take it everywhere. One line from our earliest notes survived every rewrite since, and it remains the best statement of intent we have.

{% hint style="success" icon="money-bills" %}

### Make the safest balance in your life the most interesting one to hold

{% endhint %}


---

# 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:

```
GET https://ample-2.gitbook.io/docs/research/why-ample.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.
