> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/tokenomics/chapter-10-model-security-and-transparency.md).

# Chapter 10 · Model Security and Transparency

A model is as credible as its disclosure is complete

* <mark style="color:$warning;">**Full audit coverage**</mark>: the stacking contract, crystal activation, lineage inscription, weight snapshots, LP valuation, BTC claiming, the 300% per-position boundary and every burn path are audited in full by third-party security firms, with reports published on chain.
* <mark style="color:$warning;">**Price protection**</mark>: multi-source pricing and TWAP guard against short-term manipulation and flash-loan weight inflation.
* <mark style="color:$warning;">**Permission locks**</mark>: key permissions are bound by both multisig and timelock; emergency pause only blocks new risk, and under no circumstance may an administrator move user assets.

| Disclosure item                               | Minimum standard                                                                             |
| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">Contracts</mark>    | Core addresses, source code, audit reports and version history published                     |
| <mark style="color:blue;">BTC reserve</mark>  | Pool address, live balance, cumulative inflow and distribution published                     |
| <mark style="color:blue;">Liquidity</mark>    | Initial and major LP addresses, lock arrangements, depth and concentration published         |
| <mark style="color:blue;">Permissions</mark>  | Multisig membership, thresholds, timelocks and callable rights published                     |
| <mark style="color:blue;">Distribution</mark> | Weight snapshots, distributable balance, total claimed and outstanding liabilities published |
| <mark style="color:blue;">Burning</mark>      | Burn address, cumulative burned and daily burned published                                   |

The credibility of an economic model rests on four things: <mark style="color:$warning;">**whether the code is public, whether the reserves are real, whether the routing is transparent, and whether the rules execute from on-chain state**</mark>. Everything else is left for time to verify.


---

# 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://vitaprotocol.gitbook.io/vita/vita-protocol/tokenomics/chapter-10-model-security-and-transparency.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.