> For the complete documentation index, see [llms.txt](https://docs.kasu.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasu.finance/how-kasu-works/the-role-of-the-usdkasu-token/usdkasu-token-locking-mechanics.md).

# $KASU Token Locking Mechanics

$KASU Token Lockers receive a temporary amount of non-redeemable and non-transferrable rKASU, regardless of whether they are also Lenders. However, utility and rewards are only experienced by Token Lockers who are also Lenders that achieve minimum Loyalty Levels. The amount (and synthetic value) and period of locked $KASU tokens determines a multiplier associated with the amount of rKASU that a Token Locker will receive as follows: 

Given that the synthetic value of rKASU is pegged to the $KASU token price, any fluctuations in the $KASU price naturally affect the synthetic value of rKASU.

An example is given by a Token Locker who locks 100 $KASU for 30 days. The associated multiplier is 0.05x. The Token Locker will therefore receive 5 rKASU. Similarly, a Token Locker who locks 100 $KASU for 720 days will receive 100 rKASU. The utility and rewards associated with locking $KASU to accumulate rKASU are detailed in the following sections. 


---

# 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.kasu.finance/how-kasu-works/the-role-of-the-usdkasu-token/usdkasu-token-locking-mechanics.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.