> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/audits-overview/audits-overview.md).

# Audits Overview

An overview of independent security audits conducted on Playnance smart contracts and on-chain infrastructure, providing transparency into the platform’s security posture and verification processes.

***

### Security Audits at Playnance

Playnance conducts independent third-party security audits as part of its commitment to secure, transparent, and verifiable on-chain infrastructure.

Audits focus on critical components of the system, including smart contracts, token logic, permissions, and execution mechanisms operating on PlayBlock.

All audits are performed by external security firms and reviewed internally by the Playnance engineering team.

Audit reports are published to provide full visibility into audit scope, findings, and remediation status.

***

### Completed Audits

CertiK — Smart Contract Security Audit (December 2025)

* Auditor: CertiK
* Scope: Core smart contracts, token logic, and on-chain execution components
* Status: Completed
* Focus Areas:
  * Contract security and correctness
  * Permission and access controls
  * Potential vulnerabilities and attack vectors
  * Compliance with best practices for on-chain systems<br>

**Resources:**

→ Download Full Audit Report (PDF)

{% file src="/files/hZMj1DsJKv1mNiTH7Lwu" %}

→ CertiK Skynet — Live Security Profile

Link: <https://skynet.certik.com/projects/Playnance>

***

### Audit Transparency

All published audits represent independent assessments conducted at the time of review.

Playnance treats audit findings as part of an ongoing security process rather than a one-time event.

Where applicable:

* Findings are reviewed and addressed
* Fixes are validated internally
* Changes are reflected in subsequent deployments

***

### Ongoing Security Commitment

Audits are one component of Playnance’s broader security and compliance framework, which includes:

* Continuous on-chain monitoring
* Deterministic settlement and verifiable execution
* Internal review processes
* Protocol-level transparency through PlayBlock Explorer

Additional audits and security reviews may be published as the system evolves.


---

# 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.playnance.com/audits-overview/audits-overview.md?ask=<question>&goal=<user_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.
