> 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/9.-on-chain-events.md).

# 9. On-Chain Events

CREZA emits structured events for BscScan, dashboards, and indexers. Every income row and admin stat can be rebuilt from chain history.

```mermaid
flowchart LR
    DEP[Deposit] --> E1[DepositProcessed]
    RED[Redemption] --> E2[RedemptionExecuted]
    SUN[Sunday UTC] --> E3[DAOPoolSettled]
    LAUNCH[Launch] --> E4[OwnershipRenounced]
```

## Primary events

| Event                           | When emitted        | Key fields                                        |
| ------------------------------- | ------------------- | ------------------------------------------------- |
| `DepositProcessed`              | User deposits USDT  | user, referrer, usdtAmount, crzMinted, floorPrice |
| `RedemptionExecuted`            | User burns CRZ      | user, crzBurned, usdtPayout, retainedReserve      |
| `DAOPoolSettled`                | Weekly Sunday cycle | volume, poolUSDT, shares, valuePerShare           |
| `OwnershipRenouncedPermanently` | Protocol launch     | previousOwner, nullAddress, timestamp             |

## Indexer use cases

* **Dashboard** — live income by user (direct, level, ROI, rank, DAO)
* **Admin panel** — aggregate deposits, payouts, active users
* **Audit trail** — immutable log per `(txHash, logIndex)`

## Transparency

All events are public on BSC. No off-chain ledger is required to verify protocol activity—MongoDB/indexer is a cache, chain is source of truth.


---

# 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/9.-on-chain-events.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.