> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/ko/baeuggi.md).

# 배우기

Chiliz Chain 아키텍처, CHZ 토큰노믹스, 브리징, 스테이킹, 검증자, Fan Token, 스테이블코인, DAO, 지갑을 다루는 개념 가이드입니다.

이 섹션은 Chiliz Chain의 개념과 이론적 지식을 더 깊이 이해하고자 하는 분들을 위한 안내입니다.

{% content-ref url="/pages/zx74yRIJsKZdQxfTgtaP" %}
[Chiliz Chain 소개](/ko/baeuggi/chiliz-chain-sogae.md)
{% endcontent-ref %}

{% content-ref url="/pages/MVa7u81ftJlg1e3sorzR" %}
[토크노믹스](/ko/baeuggi/chiliz-chain-sogae/tokeunomiks.md)
{% endcontent-ref %}

{% content-ref url="/pages/HcPbTp3Rxmmm6F6KIzBO" %}
[Chiliz Greenhouse](/ko/baeuggi/chiliz-chain-sogae/chiliz-greenhouse.md)
{% endcontent-ref %}

{% content-ref url="/pages/fHCVSLo8W0H8Y2V1DCuM" %}
[브리지 소개](/ko/baeuggi/beuriji.md)
{% endcontent-ref %}

{% content-ref url="/pages/CpcPn5bBWShR6VE1ja88" %}
[스테이킹 소개](/ko/baeuggi/seuteiiking.md)
{% endcontent-ref %}

{% content-ref url="/pages/M1uHpR7znIkq55BqxLP0" %}
[검증자 소개](/ko/baeuggi/geomjeungja.md)
{% endcontent-ref %}

{% content-ref url="/pages/nLvr7GxqbL4qJ0rBdhv1" %}
[Fan Token 소개](/ko/baeuggi/paen-token.md)
{% endcontent-ref %}

{% content-ref url="/pages/WjPHmjmJzcRJFDCKS2RW" %}
[스테이블코인 소개](/ko/baeuggi/seuteibulkoin.md)
{% endcontent-ref %}

{% content-ref url="/pages/jCKRgfChNbsUi1PhLeyv" %}
[DAO 소개](/ko/baeuggi/dao.md)
{% endcontent-ref %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/ko/baeuggi.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.

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.