> For the complete documentation index, see [llms.txt](https://docs.earnpark.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earnpark.com/business-whitepaper/vision-and-strategy/strategy-as-a-service.md). # Strategy-as-a-Service Looking ahead, we plan to implement "Strategy-as-a-Service" through smart contracts. In this approach, the platform will act as a proxy for decentralized strategies, enabling users to participate in complex strategies with a low entry threshold, managed through contracts. Trust management via DeFi is one of our key goals. To achieve this, we need to scale volumes and establish strategic partnerships that will support this process. Blockchain mechanisms will ensure transparency and ownership guarantees in the relationship between managers and investors, allowing users to always feel confident in the safety and use of their assets. We continue to move towards decentralization, with a focus on market development and technological integration. --- # 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.earnpark.com/business-whitepaper/vision-and-strategy/strategy-as-a-service.md?ask=&goal= ``` `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.