> For the complete documentation index, see [llms.txt](https://osean.gitbook.io/oseandao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osean.gitbook.io/oseandao/osean-token-usdosean/staking.md).

# Staking

The OSEAN DAO´s staking platform is a key feature of the OSEAN protocol. The staking platform has been developed and deployed by the OSEAN DAO to incentivize members of the OSEAN community to secure the long term success of the OSEAN protocol. &#x20;

$OSEAN holders can stake any amount of their $OSEAN tokens on the staking platform and receive a variable % APY reward proportional to the staked $OSEAN amount. Staked tokens are not subject to a locking period and may be freely unstaked at any time at the discretion of the $OSEAN holder.&#x20;

As the DAO and its members execute its vision and expand its fleet of tokenized yacht assets, stakers will be rewarded for their commitment!


---

# 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://osean.gitbook.io/oseandao/osean-token-usdosean/staking.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.
