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

# Security & Audit

{% hint style="info" %}
Third-Party Audit · Locked LP · Renounced Contract
{% endhint %}

**Smart Contract Audit**

A full third-party audit is currently in progress and expected to be
\
completed within 1–2 weeks. The full report will be published on-chain
\
and linked via the official website and Telegram the moment it is live.
\
Always verify the contract address through official channels only.

 **Liquidity Locked**
\
100% of LP tokens will be locked for a minimum of 12 months via
\
PinkLock at the time of public launch. The lock proof will be
\
publicly verifiable on-chain.

**Contract Renounced**
\
Ownership will be renounced at launch — no admin will be able to
\
mint, pause, or modify the token contract after that point.

 **Public Multisig**
\
The team treasury is controlled by a 3/5 multisig wallet.
\
All signers are publicly disclosed.

{% hint style="info" %}
⚠️ Scam Protection: The team will never ask for your private keys
\
or seed phrase. Any DM claiming to be KittyInu support asking for
\
wallet access is a scam — report and block immediately.
{% endhint %}


---

# 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://kittyinu.gitbook.io/kittyinu-docs/security-and-audit.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.