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

# 10. Security & Governance

CREZA prioritizes **immutable, autonomous execution**. There is no multisig override, no upgrade proxy, and no emergency pause.

```mermaid
flowchart TB
    DEPLOY[Contract deployed] --> CONFIG[Parameters set]
    CONFIG --> RENOUNCE["owner → 0x000…000"]
    RENOUNCE --> LOCK["Forever immutable"]
```

## Renounced ownership

After launch, administrative control transfers to the **EVM null address**. No wallet can:

* Change 80/20 or 85/15 ratios
* Pause deposits or redemptions
* Re-mint CRZ outside user deposits
* Drain the USDT vault
* Alter reward or DAO rules

## Verify on-chain

1. Call `owner()` on the Factory Router
2. Confirm result = `0x0000000000000000000000000000000000000000`
3. Check `OwnershipRenouncedPermanently` event at launch block

## Governance model

| Layer          | Control                                                    |
| -------------- | ---------------------------------------------------------- |
| Smart contract | **100% — all rules in bytecode**                           |
| Team / company | **0% — no admin keys**                                     |
| Community      | Interacts via deposits, products, governance through usage |

## Non-upgradeable deployment

No UUPS or transparent proxy. What is deployed on BSC is what runs forever—auditors and users see the exact live bytecode.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://crezanetwork.gitbook.io/crezanetwork-whitepaper/10.-security-and-governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.