> For the complete documentation index, see [llms.txt](https://docs.afx.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.afx.xyz/about-afx/core-contributors.md). # Core contributors The growth of AFX has been supported by a wide range of experienced native crypto participants operating in the industry since 2018. The collective experience of these contributors ranges from DeFi, to centralised exchanges, fiat on-ramps, and traditional finance. Perpetual DEXes represent one of the most actively developing sectors in crypto. This is why AFX was built from the ground up: to deliver a comprehensive and highly rewarding trading experience for traders who want to join and grow alongside a novel protocol from its earliest stages. The decision to build a dedicated decentralized Layer 1 with a native order book DEX was informed by the observed limitations of existing L1s in areas such as business models, scalability, and security. AFX's users play an important role in shaping the platform's development.. Core contributors engage with traders daily, actively reviewing suggestions and feedback. You are welcome to join the [Discord Server](https://discord.com/invite/mUeDkWYENJ). AFX is fully self-funded and remains free from external investor pressure regarding product direction or scaling decisions. --- # 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://docs.afx.xyz/about-afx/core-contributors.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.