> 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-protected-launch-infrastructure/liquidity-commitment-and-protected-market-infrastructure.md). # Liquidity Commitment & Protected Market Infrastructure Protecting the Market After the Sale; Making Liquidity a Launch Requirement, Not a Post-Sale Decision One of the fundamental problems surrounding token launches is the disconnect between capital raised and liquidity provided to the market. In Veloriz Ecosystem, Projects will not be allowed to raise capital through public sale and then decide what happens afterwards. A project can successfully complete a presale or public sale, collect substantial capital from participants, and subsequently enter the market with insufficient liquidity. When trading begins, relatively small sell pressure can cause significant price declines, potentially resulting in a token being traded below its original pre-sale price almost immediately. Veloriz System is designed to approach this problem differently. Under the **Veloriz Protected Launch Infrastructure**, liquidity is treated as a fundamental component of the launch rather than an asset that project owners are free to withdraw, redirect, or manage entirely at their discretion after raising public capital. **Liquidity Under Veloriz Control** Projects participating in the Veloriz Public Sale System will be required to commit a significant portion of the designated launch liquidity to the Veloriz liquidity infrastructure. The committed liquidity will be placed under a verifiable smart-contract structure, with the applicable terms established before the public sale begins. The project therefore cannot simply complete its sale and subsequently remove the liquidity that supports the market. The purpose is straightforward: > Public capital should not be raised first and liquidity decisions made afterward. The liquidity commitment forms part of the project's launch obligations from the beginning. *** **Ten-Year Liquidity Commitment** For projects accepted into the applicable Veloriz Protected Launch framework, the committed liquidity is intended to remain locked for 10 years through a verifiable on-chain contract. The lock is designed to create long-term alignment between the project, its token holders and the market in which the token trades. During the commitment period, the liquidity cannot be freely withdrawn by the project team. At the expiration of the defined lock period, any eligible liquidity or associated assets subject to the agreement may be released according to a predefined vesting and release mechanism established in the project's launch terms. Where applicable, the release may be distributed progressively to the project team rather than becoming immediately withdrawable upon expiration. This structure is intended to ensure that liquidity remains a long-term commitment rather than a temporary launch instrument. *** **Why Veloriz Controls the Liquidity** The purpose of Veloriz controlling the designated liquidity immediately after sale is not to take ownership of the project. It is to separate project development capital from market-support capital. Once liquidity has been committed to the protected launch infrastructure, the project team cannot unilaterally determine that those funds should be redirected toward marketing, operations, treasury expenditure, personal withdrawals, or other purposes. This creates a clear boundary: Project Capital → Available according to the project's disclosed structure. Committed Liquidity → Protected under the Veloriz launch framework. This separation is central to the protection model. A project seeking to raise capital from the public should understand that participating in Veloriz means accepting restrictions designed to protect the market created by that public participation. *** **Controlled Market Activation** Veloriz intends to operate the initial trading environment for projects launched through the Protected Launch Infrastructure through its own exchange infrastructure. Rather than allowing a newly launched token to immediately enter an uncontrolled liquidity environment, Veloriz can coordinate the transition from public sale into trading through its protected market structure. The intended model is for trading to become active at a launch price above the public-sale price, subject to the project's approved launch parameters and market conditions. The objective is to prevent the structural situation in which participants purchase during a public sale and immediately encounter an opening market price below what they paid. However, the launch price should not be interpreted as a permanent price guarantee. Once trading begins, market prices can fluctuate based on supply, demand and broader market conditions. Veloriz's role is to establish the initial market structure—not just to eliminate market risk. *** **Buyback Commitment** Where appropriate, Veloriz may require participating projects to commit a defined percentage of eligible trading or ecosystem fees toward a project-controlled token buyback mechanism. Such a commitment would be established before the public sale and disclosed as part of the project's launch terms. The purpose is to create an additional source of demand generated by the project's own economic activity rather than relying entirely on new buyers entering the market. Buybacks, however, will remain subject to applicable laws, technical conditions and the project's approved framework. They are not therefore represented as a guarantee of token appreciation. *** **Protected Launch Clause** Participation in the Veloriz Protected Launch Infrastructure requires the project and its responsible parties to acknowledge and accept the applicable liquidity commitments before the public sale begins. Once the designated liquidity has been committed under the protected contract, the project team shall not have unilateral authority to withdraw, redirect, encumber, or otherwise dispose of the protected liquidity during the applicable commitment period, except where expressly permitted by the governing smart contract and launch agreement. The project must also disclose the applicable liquidity commitment, lock period, release conditions and any permitted exceptions before participants enter the public sale. Any material attempt to circumvent these commitments, manipulate the protected liquidity structure, or misrepresent the project's obligations may constitute grounds for suspension of the project's Veloriz privileges and activation of applicable protective or enforcement measures. The precise legal, technical and enforcement framework will be established in the applicable project agreement and smart contracts. *** **Alignment Between Veloriz and Project Owners** Veloriz recognizes that legitimate projects need capital to build. The purpose of the liquidity commitment is therefore not to prevent project development. It is to ensure that development capital and market liquidity are treated as two different responsibilities. A project that genuinely intends to build for the long term should understand why liquidity protection is necessary. If a team is unwilling to commit liquidity, accept transparent restrictions, or allow the public to verify those commitments on-chain, that unwillingness itself becomes relevant information for prospective participants. Veloriz therefore establishes a simple standard: > Projects seeking public trust must be willing to accept public accountability. The liquidity commitment is one of the mechanisms through which that accountability becomes technically enforceable. *** **The Objective of the Infrastructure** Veloriz cannot guarantee that an investment will never lose value, nor can any legitimate market infrastructure guarantee that a token will permanently trade above its public-sale price. What Veloriz can do is address a specific structural problem: A project should not be able to raise public capital, control the market's liquidity immediately afterward, and leave participants exposed to an avoidable liquidity vacuum. By committing liquidity for the long term, placing it under verifiable contractual control, establishing controlled market activation, and potentially incorporating project-funded buyback mechanisms, Veloriz seeks to create a stronger transition between public fundraising and open-market trading. The principle is simple: > Raise responsibly. Commit liquidity. Protect the market structure. Build for the long term. Veloriz Protected Launch Infrastructure is just where liquidity becomes a commitment rather than a promise. --- # 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-protected-launch-infrastructure/liquidity-commitment-and-protected-market-infrastructure.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.