> For the complete documentation index, see [llms.txt](https://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/veloriz-core-systems/veloriz-centralized-exchange.md). # Veloriz Centralized Exchange Sustainable Market Access A token private or public sale should not be the end of a project's journey. It should be the beginning of its transition into an active market. The Veloriz Centralized Exchange (VCEX) is designed to complete this transition by providing an integrated trading environment for projects launched through the Veloriz Sale System. The fundamental purpose of the exchange is therefore closely connected to the broader Veloriz vision: to create an ecosystem where projects can be evaluated, launched, supported, discovered and traded within a structured environment. Rather than separating the fundraising process from the trading environment, Veloriz intends to connect both stages through a unified infrastructure. **From Sale to Market** Every project approved and successfully launched through the Veloriz Private/Public Sale System will be eligible for listing and trading on the Veloriz Exchange, subject to the applicable listing, technical and compliance requirements. This creates a defined pathway: Project Verification → Token Sale → Protected Launch → Exchange Listing → Market Access Participants who acquire tokens through a Veloriz public/private sale will therefore have an established trading venue within the Veloriz ecosystem where the token can become accessible for secondary-market trading after the applicable launch conditions have been satisfied. The objective is to remove the uncertainty that often exists between completing a token sale and obtaining a viable trading environment. **A Controlled Transition Into Trading** Veloriz intends to coordinate the transition from public fundraising to exchange trading through its Protected Launch Infrastructure. Before trading becomes active, the project's approved launch conditions including applicable liquidity commitments, token distribution and release schedules—must be satisfied. The exchange then provides the infrastructure through which the token can enter an organized trading environment. This approach allows Veloriz to maintain a closer relationship between the conditions under which a project raises capital and the conditions under which its token enters the market. **A Marketplace for Veloriz Projects** The Veloriz Exchange will not simply function as an independent trading platform. It will become the market layer of the broader Veloriz ecosystem. Users can discover projects through Veloriz, evaluate their available information, participate in eligible sales, and subsequently access the market through the exchange. Projects, meanwhile, gain a continuous ecosystem pathway from fundraising to market visibility and trading. This creates a unified project lifecycle: > Build → Verify → Raise → Launch → List → Grow. **Built Around the Veloriz Standard** Listing on the Veloriz Exchange is intended to represent more than simply paying for market access. Projects entering the Veloriz ecosystem are expected to operate within the standards established by the Veloriz Sale and Launch Protection frameworks. The exchange will therefore serve as the continuation of a project's relationship with Veloriz rather than an isolated listing destination. Veloriz's long-term objective is to create an environment where capital formation, market access, project discovery and ecosystem utility exist within one connected infrastructure. > Veloriz is building more than a place to sell tokens. It is building the path from project creation to public participation and ultimately to an active market. The Veloriz Exchange becomes the market where the Veloriz launch ecosystem continues to live. --- # 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://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/veloriz-core-systems/veloriz-centralized-exchange.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.