> For the complete documentation index, see [llms.txt](https://suzuna.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suzuna.gitbook.io/whitepaper/on-chain-usage-records.md).

# On-Chain Usage Records

Every seven days SUZUNA aggregates its usage metrics for that period and publishes them to a smart contract on BNB Chain.

Each publication is called a checkpoint and contains the five product metrics for that seven-day window, along with the period's start and end times.

Checkpoints are append-only. The contract has no update function and no delete function, so once a checkpoint is confirmed its figures can never be revised. Each new period creates a new checkpoint rather than replacing the previous one, building a permanent public history.

Individual user actions are never written to the blockchain. Only the aggregated counts for a completed period are published.

#### What a checkpoint proves

A checkpoint proves that SUZUNA published a specific set of numbers at a specific time and cannot quietly revise them afterwards. It does not independently verify that the underlying data is accurate the contract records what the backend computes.

The published figures are available at suzunai.xyz and can be read directly from the contract on BNB Chain.


---

# 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://suzuna.gitbook.io/whitepaper/on-chain-usage-records.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.