# Audit

Smart contract auditing is a critical step in ensuring the security and reliability of blockchain applications. Accelchain employs a multi-faceted approach, combining Symbolic Execution and AI-Driven Static Analysis to comprehensively audit contracts.

#### **Audit Initiatives:**

* *Initiating Audits:* Users can seamlessly initiate audits directly from the main left navbar or by using the 'Run Audit' button located on the upper right side of the IDE in edit mode.
* *Contract Upload:* From the navbar, users can upload contracts directly, triggering an audit report based on both Symbolic Execution and Static Analysis.<br>

> For now, Accelchain Audits are adhering to Ethereum.org's SWC (Smart Contract Weaknesses and Common Vulnerabilities) guidelines only.
>
> <https://swcregistry.io/>
>
> The tools may not cover all possible attack vectors or business logic vulnerabilities present in the smart contract.&#x20;
>
> Audit features for 'Attack Vectors' and 'Business Logic Vulnerabilities' are in the pipeline and should be launched soon!

#### **Comprehensive Audit Report:**

* *Combining Insights:* Accelchain provides users with a comprehensive Audit Report, combining findings from Symbolic Execution and AI-Driven Static Analysis.
* *Categorization:* Identified issues are categorized by severity, allowing prioritization based on criticality.
* *Limitations:* Symbolic execution may not cover all possible states, and AI analysis is currently focused on the 36 predefined SWC IDs.
* *Upcoming Features:* Accelchain is actively working on features for auditing 'Attack Vectors' and 'Business Logic Vulnerabilities,' enhancing the tool's capabilities.

####


---

# Agent Instructions: 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:

```
GET https://accelchain.gitbook.io/docs/audit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.