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

# Get to know OOFP

**OOFP is a project within the Bitcoin ecosystem that provides value-added services for assets like inscriptions, runes, and NFTs.** 

**It combines a vault pool for mining with strategies like hodling, staking, and DeFi to enhance asset appreciation and growth. OOFP aims to create a vibrant ecosystem where participants can benefit from the increased value of their assets.**

**The project operates on the principle of creating a vibrant ecosystem in which assets within the Bitcoin network can thrive. By offering value-added services and opportunities for asset appreciation, OOFP aims to attract and engage participants, contributing to the overall development and success of the Bitcoin ecosystem.**

<br>

<br>


---

# 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://odfi.gitbook.io/oofp/get-to-know-oofp.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.