> For the complete documentation index, see [llms.txt](https://docs.kleva.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kleva.io/legacy-kr/overview/kleva-token/reward-allocation.md).
# 이용자 보상 배분표
### KLEVA 토큰 보상 배분표
블록당 발행량 : 0.9 KLEVA
| 보상 수령 주체 | 할당 포인트 | *일별 보상 |
|---|
| ibKLAY 스테이커 | 297.5 | 8,675 |
| iboUSDT 스테이커 | 270 | 7,873 |
| iboWEMIX 스테이커 | 100 | 2,916 |
| ibKDAI 스테이커 | 110 | 3,208 |
| iboETH 스테이커 | 30 | 875 |
| iboUSDC 스테이커 | 120 | 3,499 |
| ibKLEVA 스테이커 | 120 | 3,499 |
| ibKCD 스테이커 | 5 | 146 |
| KLAY 대여자(레버리지 투자자) | 327.5 | 9,550 |
| oUSDT 대여자(레버리지 투자자) | 300 | 8,748 |
| KDAI 대여자(레버리지 투자자) | 100 | 2,916 |
| oETH 대여자(레버리지 투자자) | 40 | 1,166 |
| oUSDC 대여자(레버리지 투자자) | 100 | 2,916 |
| KLEVA 대여자(레버리지 투자자) | 50 | 1,458 |
| KSD 대여자(레버리지 투자자) | 30 | 875 |
| 총합 | 2,000 | 58,320 |
*\*일별 보상량은 조건부 보상 방식에 따라 소폭 변경될 수 있습니다.*
예치/스테이킹풀이 추가될 경우 보상 수령 주체가 늘어나 보상 배분표가 업데이트됩니다.
---
# 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://docs.kleva.io/legacy-kr/overview/kleva-token/reward-allocation.md?ask=&goal=
```
`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.