> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/virtuals-protocol-whitepaper-ko/virtuals-1/usdvirtual/token-distribution.md).
# 토큰 분배
$VIRTUAL 토큰 분배 (총계: 1,000,000,000)
**모든 토큰은 완전히 잠금 해제되어 베스팅되었습니다**.
향후 인플레이션 없이 발행될 총 1,000,000,000 $VIRTUAL 토큰의 분배 계획은 DAO 내의 다양한 이해관계자들에게 배분됩니다. 다음은 배분 내역입니다:
1. 공개 배분: 60%(600,000,000토큰)가 현재 공개 유통 중입니다.
2. 유동성 풀: 5%(50,000,000토큰)는 유동성 풀을 위해 따로 배정됩니다.
3. 생태계: 35%(350,000,000토큰)는 생태계 금고에 تخص정됩니다. 이 배분은 VIRTUAL 프로토콜 생태계 내 성장에 기여하는 커뮤니티 인센티브와 이니셔티브를 위해 earmarked 되어 있습니다. 이 자금은 DAO가 관리하는 멀티시그 지갑에 보관되며, 향후 3년 동안 연간 10%를 초과하는 발행은 없을 것입니다. 단, 거버넌스 승인을 받은 후에만 배포가 가능합니다.
---
# 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://whitepaper.virtuals.io/virtuals-protocol-whitepaper-ko/virtuals-1/usdvirtual/token-distribution.md?ask=&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.
