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

# Size of the Opportunity

Providing a crypto-native synthetic dollar and the first "internet bond" is not only the largest challenge in the space but the largest opportunity.

The reward-bearing digital dollar sector currently accounts for approximately 5-6% of the total stablecoin market capitalization.

With various forecasts predicting a compound annual growth rate (CAGR) of over 50% for stablecoin supply during the next decade, the total market is projected to exceed $2 trillion by 2032.

> *"I believe that stablecoin legislation backed by U.S. treasuries or T-bills will create a market that will expand U.S. dollar usage via these stablecoins all around the world. I think that  $2 trillion is a very reasonable number, and I could see it greatly exceeding that."*&#x20;
>
> *- Scott Bessent, U.S Treasury Secretary*


---

# 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.ethena.fi/overview/size-of-the-opportunity.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.
