> For the complete documentation index, see [llms.txt](https://ottochains-organization.gitbook.io/ottochain-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ottochains-organization.gitbook.io/ottochain-documentation/value-proposition.md).

# Value Proposition

Ottochain's value propositions exist in its commitment to interoperability, security, community-driven governance, vibrant community ecosystem, and developer-friendly environment. As a Cosmos chain supporting [Tips](https://docs.cosmos.network/main/core/tips) messages, it is one of the only places EVM smart contract developers can receive rewards per usage of their dapps. This will allow Ottochain to send non-native tokens like OCT or wrapped NEAR from the appchain once the feature is developed further through interchain communication.<br>

Ottochain is the first appchain to leverage the restaking mechanism integrated into NEAR Protocol via Octopus Network. Therefore, while having its own consensus, it will also derive economic security from NEAR Protocol by directly linking it’s economy to multiple NEAR Protocol validators through Octopus Network restaking contracts.


---

# 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://ottochains-organization.gitbook.io/ottochain-documentation/value-proposition.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.