> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/1.-introduction-to-frequency-x-chain-frecx-developer-documentation/1.4-who-should-use-this-guide.md). # 1.4 Who Should Use This Guide This guide is intended for: * Developers new to blockchain who want to understand and build decentralized applications * Web2 developers transitioning into Web3 * Experienced blockchain developers exploring FreCx-specific capabilities * Infrastructure providers and node operators * Enterprises integrating blockchain into real-world systems FreCx is designed as a developer-centric blockchain, where infrastructure, tools, and economic models are aligned to support real-world application development. By combining familiarity with innovation, it enables developers to build systems that are both technically robust and practically relevant. With this foundation in place, the next step is to understand the Architecture of the protocol and how to develop and deploy smart contracts on the FreCx network. --- # 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.frequencychain.org/1.-introduction-to-frequency-x-chain-frecx-developer-documentation/1.4-who-should-use-this-guide.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.