> For the complete documentation index, see [llms.txt](https://coreszn.gitbook.io/coreszn-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coreszn.gitbook.io/coreszn-docs/overview.md). # Overview CORESZN is a community-driven project on Core Chain. ## The return of retail to Bitcoin ### About CORESZN CORESZN is a community-driven project built on Core Chain. It supports the broader goal of expanding Bitcoin's role in decentralized finance. Bitcoin's financial ecosystem continues to evolve. Core connects Bitcoin with decentralized applications. This creates new ways to participate in on-chain finance. CORESZN brings this vision to its community. It focuses on retail participation, token-based incentives, and liquidity provision across the Core ecosystem. ### Utility and ecosystem CORESZN supports community participation through decentralized farming and staking. The project allocates CORESZN rewards to liquidity providers and eligible participants. Participants can earn rewards by locking assets in designated farming and staking protocols. This incentive structure encourages liquidity provision and supports market depth. It also strengthens participation in the CORESZN ecosystem. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://coreszn.gitbook.io/coreszn-docs/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.