# Ecosystem Infrastructure ### Overview The 0Fx ecosystem is structured around a set of operational components (“building blocks”), each designed to play a specific role within the protocol and its long-term strategy. These components are intentionally modular: the ecosystem can expand over time while maintaining a coherent product strategy centered around long-term market exposure. *** ### 1) 0Fx Protocol (Core Infrastructure) The **0Fx Protocol** is the core technical foundation of the ecosystem. It includes the full technical and financial infrastructure required to operate: * on-chain protocol components (token, liquidity infrastructure, multisigs, contracts), * operational tooling (off-chain agents supporting monitoring, pricing, and ecosystem operations), * and the security model required for long-term reliability. This layer provides the execution and infrastructure base for all ecosystem products. *** ### 2) 0Fx Capital (Primary Product Layer) **0Fx Capital** is the primary user-facing product layer of the ecosystem. It is designed to provide **structured long-term market exposure** through investment products built on top of on-chain infrastructure. The objective is to offer users access to long-term exposures across multiple categories, with: * index-like product structures, * on-chain transparency, * and an ecosystem designed to improve long-term efficiency and execution quality. 0Fx Capital represents the main entry point for most users. *** ### 3) 0Fx DAO (Governance & Transparency Layer — Upcoming) The **0Fx DAO** is an upcoming ecosystem component designed to provide: * transparent visibility over ecosystem operations, * structured decision-making mechanisms, * and progressive community control over protocol evolution. As governance matures, the DAO is expected to play an increasing role in: * ecosystem priorities, * treasury/resource allocation, * and approval of strategic initiatives. ### 4) 0Fx Venture (R\&D & Application Development Layer) **0Fx Venture is the R\&D and application development branch of the 0Fx ecosystem.**\ Its role is to design, build, and ship the ecosystem’s applications and supporting protocol utilities. 0Fx Venture is not intended to provide a standalone user product.\ Even when a dedicated Venture interface/website exists, its purpose will mainly be to: * present ongoing R\&D, * document ecosystem applications, * track releases and priorities, * and explain how ecosystem development is structured. #### Venture Applications (Examples) Applications such as **Inner**, **Duo**, and **Aurex** are Venture-built ecosystem components.\ They are developed to support the main product layer (**0Fx Capital**) by providing essential utilities such as: * swap & execution tooling, * long-term collateralization primitives, * and additional services needed for long-term exposure strategies. ### Ecosystem Strategy (Summary) The ecosystem is intentionally designed around a clear structure: * **Protocol** = infrastructure foundation * **Capital** = flagship product (structured long-term exposure) * **DAO** = transparency + governance (progressive decentralization) * **Venture** = R\&D + ecosystem expansion --- # Agent Instructions: 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: ``` GET https://0fx-protocol-1.gitbook.io/0fx-protocol-docs/protocol/ecosystem-infrastructure.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.