> For the complete documentation index, see [llms.txt](https://vincechain.gitbook.io/vince-chain-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vincechain.gitbook.io/vince-chain-documentation/2.-vince-chain-x-developers/developer-kit/contract-verification.md). # Contract Verification Contract verification refers to auditing or verifying smart contract codes before deploying them on the blockchain. This process helps to prevent users or developers from accessing malicious or insecure projects or contracts. Contract verifiers (or auditors) usually verify and analyze contract codes thoroughly for potential bugs or vulnerabilities which could hamper the project in the future. Users can also verify contract codes to avoid falling for phished projects. Contract verification could be done with automated tools, independent auditors, or cybersecurity experts. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://vincechain.gitbook.io/vince-chain-documentation/2.-vince-chain-x-developers/developer-kit/contract-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.