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

# The Spirit of double2win

**Double** is being selected as the project name due to the simple fact that the project doubles ROI for capital providers. The tagline "**double2win**" is selected because:

* Double enables a win-win collaboration between capital size and token side. Capital cares about trading fees, yields and APY, and token cares about the depth of its liquidity pool. They have non-conflicting goals. More importantly, each side is harder to achieve its goals by itself, and only we collaborate, they will both achieve their goals easier. "**double2win**" beautifully reflects this spirit.
* Crypto is all about trustless coordination among different entities using cryptonomic incentives to achieve amazing things. The core of Double's design is to use economics to incentive two groups of entities - capital providers and token projects, to coordinate in a trustless way to achieve things they could not achieve alone. "**double2win**" vividly demonstrates this crypto ethos.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.double2win.xyz/introduction/the-spirit-of-double2win.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.