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

# 1 RT

![](/files/sfHbOOoWuhnvDRca8FT3)

## **1RT 컨트랙트 주소**

<https://www.bscscan.com/address/0x012a6A39eeC345A0Ea2B994B17875E721d17eE45>

## 공급

1RT 총 공급량: 2,100,000,000

<figure><img src="/files/U49aQ1wgG12So9rDUepl" alt=""><figcaption><p>1RT 토큰 배포:</p></figcaption></figure>

1\. 2,000,000,000 – 게임 로열티 및 신규 회원 등록용

&#x20;2\.  100,000,000 – 개발자용

3\. 4,000,000 – 사전 생성된 토큰용

&#x20;

**개발자 대상 1RT 토큰 배포**

&#x20;96,000,000- 2023년 9월 1일부터 매월 200,000 1RT 지급 중, 최종 지급 2066년 예정

<figure><img src="/files/IdhUwqUFuNlhmxNvdC2N" alt=""><figcaption><p>연도별 1RT TOKEN 배포</p></figcaption></figure>

## 1RT 소각 메커니즘

&#x20;1RT 토큰은 다음의 경우 소각됩니다:

&#x20;1\.   신발 생성(Shoe Minting)

2\.   수리

3\.   스니커즈 레벨업

4\.   보석 업그레이드

5\.   소켓 잠금해제


---

# 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.1move.io/ko/tokenomics/1-rt.md?ask=<question>&goal=<endgoal>
```

`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.