# Page Not Found

The URL `wnz/4.-winnerz/4.10-staking` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [4.2 매칭 시스템(체육관 & 트레이너)](https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.2-and.md)
- [4.3 오프라인(위너즈 챔피언십 대회 & 스포츠 센터 프랜차이즈)](https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.3-and.md)
- [4.10 팬 토큰](https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.10.md)
- [4.11 토큰의 유틸리티](https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.11.md)
- [4.5 NFT 선수 카드](https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.5-nft.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 following URL with the `ask` and `goal` query parameters:

```
GET https://winnerz.gitbook.io/whitepaper_kor/wnz/4.-winnerz/4.2-and.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.

### Option 2 — Browse the documentation index

Full index: https://winnerz.gitbook.io/whitepaper_kor/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://winnerz.gitbook.io/whitepaper_kor/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., `/whitepaper_kor/wnz/4.-winnerz/4.2-and.md`).

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