> For the complete documentation index, see [llms.txt](https://vorachain.gitbook.io/vorachain-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vorachain.gitbook.io/vorachain-docs/reference/audit.md). # Audit www\.vorachain.com ## 🛡️VORA Smart Contract Audit Security and transparency are important priorities for the Vorachain ecosystem. The VORA Smart Contract Audit process is intended to assess the security, reliability, and operational design of VORA-related smart contracts before or during their use within the ecosystem. An audit is a structured technical review of smart-contract code. Its purpose is to identify potential vulnerabilities, logical errors, access-control risks, incorrect fee calculations, unsafe token handling, reentrancy issues, and other conditions that could affect users, assets, or protocol operations. The review may also examine whether the smart contract behaves according to its documented functions and intended design. The VORA audit scope may include the native token infrastructure, Wrapped VORA (WVORA), staking and vault contracts, decentralized exchange contracts, liquidity-management contracts, bridge contracts, validator-related functions, and other supported applications deployed within the Vorachain ecosystem. During the audit process, security reviewers analyze critical functions such as token minting and burning, ownership permissions, administrative roles, transaction fees, emergency pause controls, upgrade mechanisms, asset withdrawal functions, and interactions with external contracts. Particular attention should be given to functions that can move user funds, change important settings, or grant privileged access. An audit report provides users, developers, partners, and community members with more visibility into the technical status of the reviewed contracts. It may include the audit scope, contract addresses, code versions, methodology, identified findings, severity classifications, remediation status, and final conclusions. Where issues are identified, the development team can review, fix, retest, and redeploy the contracts when necessary. However, an audit does not guarantee that a smart contract is completely free from risk. Blockchain technology, third-party integrations, market conditions, user actions, and future software changes can create risks that may not be identified during a specific review. Users should always verify official contract addresses, carefully review transaction approvals, and use only trusted Vorachain links and applications. Vorachain is committed to improving security standards through transparent development, responsible access controls, ongoing monitoring, and independent technical review where applicable. The audit information is made available to help the community understand the security measures applied to the VORA ecosystem. ## 📖Read the VORA Audit Report {% embed url="" %} *** ## **☎️Need Help?** Reach out to us for support, suggest improvements, or file a ticket using the [**Support**](mailto:support@vorachain.com) on Telegram. Our team is here to assist you! * [**Telegram**](https://t.me/VORA_Chain): Join our developer community * [**Twitter**](https://x.com/VORAChainHQ): information VoraChain --- # 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://vorachain.gitbook.io/vorachain-docs/reference/audit.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.