> 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/leveraged-yield-farming.md).

# 투자 가이드

- [#0: 핵심용어집](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/glossary.md)
- [#1: 디파이 투자의 이해](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/understanding-of-defi.md)
- [#2: 잠재적 위험과 관리](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/risk-management.md)
- [#3 예치⬝스테이킹 가이드](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/lend-stake.md)
- [#4: 레버리지 투자의 이해](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/understanding-of-lyf.md)
- [#5: 스테이블 코인으로 투자하기](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/stablecoins.md)
- [#6: 롱/숏 투자의 이해와 일반 가상 자산으로 투자하기](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/long-short-position.md)
- [#7: 복수의 레버리지 투자를 통한 위험 최소화 전략](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/hedging-strategy.md)
- [청산](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/liquidation.md)
- [미상환 부채와 대응](https://docs.kleva.io/legacy-kr/leveraged-yield-farming/bad-debt.md)


---

# 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:

```
GET https://docs.kleva.io/legacy-kr/leveraged-yield-farming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.