> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/kr/undefined-2/yield-farming/crosschain-farming.md).

# 크로스체인 파밍

다른 블록체인에서 파밍하고 동일한 CAKE 보상을 받으세요

<figure><img src="https://raw.githubusercontent.com/pancakeswap/pancake-document/en/.gitbook/assets/image%20%2836%29.png" alt=""><figcaption></figcaption></figure>

멀티체인 배포를 통해 PancakeSwap은 이제 PancakeSwap 파밍의 대표적인 일드 파밍 경험을 다른 블록체인의 사용자에게도 제공합니다. 파밍에서는 LP 토큰을 스테이킹하여 PancakeSwap을 지원하면서 CAKE를 획득할 수 있습니다.

일드 파밍에 대해 더 알아보려면 [메인 섹션](/kr/undefined-2/yield-farming.md)을 확인하세요.

파밍을 시작하려면 [파밍 이용 방법 가이드](https://docs.pancakeswap.finance/earn/yield-farming/how-to-use-farms/how-to-use-farms)를 확인하세요.

{% hint style="warning" %}
일드 파밍은 시럽 풀보다 더 높은 보상을 제공할 수 있지만, **비영구적 손실(Impermanent Loss)** 위험이 따릅니다. 이름처럼 그렇게 무서운 것은 아니지만, 시작하기 전에 개념을 알아 두는 것이 좋습니다.

자세한 내용은 Binance Academy의 [비영구적 손실에 대한 훌륭한 글](https://academy.binance.com/en/articles/impermanent-loss-explained)을 확인하세요.
{% endhint %}

PancakeSwap 크로스체인 파밍은 Celer Network가 제공하는 크로스체인 메시징 서비스를 기반으로 합니다. 자세한 내용은 <https://www.celer.network/>에서 확인하세요.


---

# 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://docs.pancakeswap.finance/kr/undefined-2/yield-farming/crosschain-farming.md?ask=<question>&goal=<user_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.
