> 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/history.md).
# A Savings Idea Older Than Computers
In 1956, the British government faced a problem every fintech founder would recognize. People weren't saving, and telling them to wasn't working. Post-war inflation was eating wages, and the Treasury needed households to build savings voluntarily, at national scale.
The instrument they launched looked strange on paper. **Premium Bonds** paid no interest at all. Instead, the interest the entire bond pool would have earned was gathered into a monthly prize fund and distributed by draw, in a spread running from small consolations to a headline jackpot. A bond was always redeemable at face value. You could never lose your stake. You could only stop waiting.
Critics called it a lottery in a savings costume. The public bought it anyway, in enormous numbers, and the monthly draws, run by a random number generator the nation came to know as ERNIE, became a fixture of British life. Seventy years later, more than **20 million people hold Premium Bonds, with over £100 billion in the system**. It stands among the most widely held savings products in the United Kingdom, chosen year after year over accounts paying ordinary interest at comparable rates.
### Why it worked
People respond to possibility far more than to basis points. Behavioral economists have measured this for decades, and every lottery on earth runs on it. Premium Bonds pointed the same instinct at saving instead of spending, and the stake survived the ride.
The downside mattered just as much. A month without a win didn't register as a loss, because nothing was lost. The floor of a Premium Bond is a savings account at zero interest, which most people experience as a pause rather than a defeat. And a neighbor winning £1,000 started conversations that recruited new savers for decades, marketing that interest payments have never produced.
The idea also travels well. When Michigan credit unions launched **Save to Win** in 2009, prize-linked accounts pulled in deposits heavily from people who hadn't been saving at all, and the model spread across dozens of states, with US federal law clearing the way for banks in 2014. The earliest known ancestor, Britain's "Million Adventure" lottery loan, dates to **1694**. This is one of the oldest reliably working mechanisms in consumer finance, three centuries old and still converting non-savers into savers wherever it appears.
What it lacked, until now, was infrastructure equal to the idea. Premium Bonds needed a government to run the fund, a national brand to reach scale, and public trust in an unseen machine. Ample's answer to all three is the chain itself. Programmable yield fills the pool, a global dollar gathers it, and the draws are checkable by anyone. [Why We Built Ample](/docs/research/why-ample.md) connects the history to the product.
{% hint style="info" %}
Premium Bonds and Save to Win appear here as research context. Ample is unaffiliated with NS\&I and with any credit union program, and differs in important ways, including that Premium Bonds carry a government guarantee and Ample deposits do not. The comparison is about the savings mechanism, not the risk profile.
{% 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/history.md?ask=
```
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.