> 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/project-due-diligence-and-verification.md). # Project Due Diligence & Verification Verifying What the Project Is Before Public Capital Is Accepted An undeniable fact that knowing the founders is only the first step toward building a trustworthy public sale. The next is establishing that the project itself is legitimate, sufficiently documented, and prepared to enter the public market. Before a project is permitted to conduct a public sale through the Veloriz Ecosystem, it will undergo a structured due diligence and verification process designed to assess the information presented by the project and identify material issues that may be relevant to prospective participants. Veloriz will examine the project's underlying structure, stated purpose, development progress, documentation, operational model, token role, and other relevant information necessary to understand what the project is building and how it intends to operate. Where applicable, claims relating to partnerships, funding, technology, or other material aspects of the project may also be subject to verification. The purpose of this process is not to predict whether a project will succeed or to eliminate the risks associated with digital assets. No due diligence process can provide such a guarantee. Instead, Veloriz seeks to ensure that projects entering its public sale system have been subjected to a consistent standard of review and that material information is presented transparently before public participation begins. Projects that fail to satisfy the applicable requirements may be required to provide additional information, address identified concerns, or may not be approved for a Veloriz Public Sale. This establishes an important distinction between being listed for sale and being admitted to the Veloriz Public Sale System. Access to public capital through Veloriz is conditional on meeting the platform's established standards. Veloriz's approach is simple: > Before the public is asked to support a project, the project must first be willing to open itself to reasonable scrutiny. The objective is to reduce information asymmetry, strengthen accountability, and give participants a clearer basis on which to evaluate the opportunity for themselves. Veloriz does not ask participants to trust blindly. It builds a process through which trust can be informed by verification. --- # 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/project-due-diligence-and-verification.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.