# Page Not Found

The URL `files/M25YK0H4wWJ9RFboUjUY` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Cred信用积分系统界面说明](https://clarkwang-guidebook.gitbook.io/phavercn/cred-xi-tong-jie-shao/cred-xin-yong-ji-fen-xi-tong-jie-mian-shuo-ming.md)
- [积分更新介绍： PHAVES](https://clarkwang-guidebook.gitbook.io/phavercn/ji-fen-jie-shao/ji-fen-geng-xin-jie-shao-phaves.md)
- [Phaver代币](https://clarkwang-guidebook.gitbook.io/phavercn/bai-pi-shu/phaver-dai-bi.md)
- [Phaver接受LensHolic专访](https://clarkwang-guidebook.gitbook.io/phavercn/phaver-jie-shao/phaver-jie-shou-lensholic-zhuan-fang.md)
- [Phaver积分（off-chain）](https://clarkwang-guidebook.gitbook.io/phavercn/bai-pi-shu/phaver-ji-fen-offchain.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://clarkwang-guidebook.gitbook.io/phavercn/cred-xi-tong-jie-shao/cred-xin-yong-ji-fen-xi-tong-jie-mian-shuo-ming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://clarkwang-guidebook.gitbook.io/phavercn/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://clarkwang-guidebook.gitbook.io/phavercn/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/phavercn/cred-xi-tong-jie-shao/cred-xin-yong-ji-fen-xi-tong-jie-mian-shuo-ming.md`).

You may also use `Accept: text/markdown` header for content negotiation.