# Introduction

As we were designing <mark style="color:blue;">**Noon**</mark>, at every step, we asked ourselves one question: *“How can we maximise value to our users?”* We broke this up into two problems:

1. How do we generate as much value (returns) as possible?
2. How do we ensure that as much of it is distributed to our users?

This led us to our mission.

## <mark style="color:orange;">**Noon aims to be the**</mark>**&#x20;**<mark style="color:$info;">**highest yielding**</mark><mark style="color:orange;">**,**</mark>**&#x20;**<mark style="color:$info;">**safest**</mark><mark style="color:orange;">**, and**</mark>**&#x20;**<mark style="color:$info;">**most long-term oriented**</mark>**&#x20;**<mark style="color:orange;">**stablecoin in web3.**</mark>

### <mark style="color:orange;">**Highest yielding**</mark><mark style="color:orange;">:</mark> With a dynamic allocation strategy and a strong governance token design, <mark style="color:blue;">**Noon**</mark> aims to have the highest stable yields possible for a stablecoin.

We aim to be the stablecoin with the <mark style="color:orange;">**highest through-cycle returns**</mark> by dynamically and intelligently allocating capital across a basket of delta-neutral strategies. We also aim to have the most robust, rewarding tokenomics model, to maximise the real utility of our governance token.

{% content-ref url="../built-for-high-yields" %}
[built-for-high-yields](https://docs.noon.capital/built-for-high-yields)
{% endcontent-ref %}

### <mark style="color:orange;">**Safest**</mark><mark style="color:orange;">:</mark> With a thorough, multi-faceted security framework, <mark style="color:blue;">Noon</mark> aims to be the safest stablecoin in web3.

We have developed a detailed, comprehensive approach to security, which covers topics from custody and infrastructure to yield sources and operational integrity. Each of these come together to form the most complete security framework in digital assets, allowing us to offer the safest end-to-end user experience in the stablecoin space.

{% content-ref url="../built-for-safety" %}
[built-for-safety](https://docs.noon.capital/built-for-safety)
{% endcontent-ref %}

### <mark style="color:orange;">**Long-term oriented**</mark><mark style="color:orange;">:</mark> With an unflinching focus on sustainability and long-term success, <mark style="color:blue;">Noon</mark> aims to build a stablecoin for the future.

We have built every element of our stablecoin to make it sustainable in the long term - from our raw yields, our governance rewards and even our team continuity. By building for the long term, we aspire to create a protocol that sustains value in the long term, and attracts partners, users, and team members who are similarly motivated.

## <mark style="color:orange;">So,</mark> <mark style="color:orange;"></mark>*<mark style="color:orange;">how can we</mark> <mark style="color:$info;">maximise</mark> <mark style="color:orange;">value to our users?</mark>*

We hope we have answered this in numerous ways throughout our protocol - and we hope you see our answers as you read on and as you start using <mark style="color:blue;">**Noon**</mark> yourself. Rest assured - we will continue to improve upon our answers in the coming weeks, months, and years to create more value for our every day.

If you have any comments or suggestions, feel free to [reach out](https://docs.noon.capital/additional-resources/contact-us) - we look forward to building together.


---

# Agent Instructions: 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://docs.noon.capital/noon-the-basics/introduction.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.