> For the complete documentation index, see [llms.txt](https://docs.veritasprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veritasprotocol.com/ecosystem/soulbound-audit-token.md). # SoulBound Audit Token Soulbound NFT Certificates as Proof-of-Audit While auditing is undoubtedly a critical first step in securing a smart contract, the reality is that the challenge doesn’t end there. The audit reports, often detailed and technical, may not be easily accessible or understandable to the average user or investor. How can we bridge this gap? How can we make these technical audit reports understandable to anyone using smart contracts? This forms the problem that SoulBound Audit Tokens (SATs) aims to solve! SAT act as an on-chain certification system, a Proof-of-Audit, establishing a level of trust and transparency that has been notably absent in the smart contracts security industry. By providing a visible, color-coded security rating directly on the blockchain, SATs make it simpler for users to understand the security level of a smart contract, enabling them to engage with confidence. Notably, the SAT provides key information about the audit score and links to the full audit report right within the blockchain itself. **Three-Level Certification** SAT offers a three-tiered certification system to make the security level of smart contracts instantly recognizable. Each class is visually distinct and color-coded to provide an immediate understanding of the smart contract’s security status. Below are the specifics: **High-Security Certifications** * **Color:** Green**.** * **Implication:** The contract is highly secure, with minimal to no vulnerabilities detected. * **Decentralization Grades**: Decentralized/Semi-Centralized/Centralized. **Medium-Security Certifications** * **Color:** Yellow. * **Implication:** The smart contract has passed the audit, but some areas could benefit from further optimization. It is considered safe, but with reserves, often linked to the owner’s privileges. * **Note:** Users should read the full audit report for detailed insights. * **Decentralization Grades**: Decentralized/Semi-Centralized/Centralized. **Low-Security Certifications** * **Color:** Red. * **Implication:** The smart contract has undergone an audit and has significant vulnerabilities or areas requiring immediate attention. A list of critical recommendations for improvement often accompanies this rating. * **Note:** It is advised to proceed with extreme caution and await updates or fixes before interacting with such contracts. * **Decentralization Grades**: Decentralized/Semi-Centralized/Centralized.

SoulBound Audit Tokens

Each contract will display both a color-coded security rating and a label for decentralization, making it easier for users to make informed decisions when interacting with smart contracts. --- # 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://docs.veritasprotocol.com/ecosystem/soulbound-audit-token.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.