> For the complete documentation index, see [llms.txt](https://allblue-docs.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://allblue-docs.gitbook.io/docs/en/contracts-and-deployments/security-and-verification.md).

# SECURITY & VERIFICATION

This section provides publicly available audit reports and information about the scope of each audit.

Some smart contracts within the AllBlue ecosystem have undergone security reviews by external security auditing firms.

### Auditor

Some audits were conducted by **Cyberscope**, a Web3 security auditing firm.

The audit reports include the contracts reviewed, identified issues, and the code scope covered at the time of each audit.

### Audit Scope

Security audits are based on the **specific code and contract scope stated in the audit report at the time of the audit**.

Contracts deployed later, configuration changes, external protocols, or code not included in the original audit scope may fall outside the scope of the audit.

A security audit is a process intended to identify and review potential vulnerabilities and does not guarantee the absence of all risks.

### Security & Verification

AllBlue provides external smart contract audit reports and project KYC verification records that were conducted for previous protocols.

| Verification                | Provider   | Scope                  |
| --------------------------- | ---------- | ---------------------- |
| V2 Smart Contract Audit     | Cyberscope | PumpSpace V2 contracts |
| Stable Smart Contract Audit | Cyberscope | AquaBank contracts     |
| Team KYC                    | Coinscope  | PumpSpace project team |

Each audit report and verification record can be reviewed on the corresponding page.

Security audits and KYC verification are based on the code or project information reviewed at the time of verification.