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

# 브릿징

GIWA 체인과 이더리움(Ethereum) 간에 자산 또는 데이터를 이동시키고 싶나요? 브릿징(bridging)에 대해 알아보세요.

GIWA는 이더리움과 연결되어있는 레이어 2(Layer 2)에요. 하지만 별도의 블록체인이기 때문에 이들 네트워크 간에 자산(ETH, ERC-20 토큰)이나 데이터를 이동시키기 위해서는 특별한 과정이 필요합니다. 이러한 과정을 **브릿징(bridging)**&#xC774;라고 해요.

쉽게 말해 브릿징을 통해 이더리움에 있는 여러분의 자산을 GIWA로 옮길 수도 있고, 반대로 GIWA에서 이더리움으로도 옮길 수 있어요.

브릿징을 활용한 앱을 만들고 싶으신가요? 아래 문서와 함께 시작해보세요.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-ethereum">:ethereum:</i></td><td>ETH 브릿징하기</td><td></td><td><a href="https://docs.giwa.io/get-started/bridging/eth.md">ETH 브릿징하기</a></td></tr><tr><td><i class="fa-coin-blank">:coin-blank:</i></td><td>ERC-20 토큰 브릿징하기</td><td></td><td><a href="https://docs.giwa.io/get-started/bridging/erc-20.md">ERC-20 토큰 브릿징하기</a></td></tr></tbody></table>

## 브릿지 서비스

일반 사용자들도 쉽고 빠르게 자산을 이동시킬 수 있도록 다양한 브릿지 서비스가 존재합니다. 자세한 내용은 [브릿지](https://docs.giwa.io/tools/bridges.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.giwa.io/get-started/bridging.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.
