# Bridging

GIWA is an Ethereum-connected Layer 2, but it runs as a separate blockchain. To transfer assets (ETH, ERC-20 tokens) or data between these networks, a special process called **bridging** is required.

In simple terms, bridging lets you move your assets from Ethereum to GIWA — and back from GIWA to Ethereum.

Want to build apps that leverage bridging? Get started with the documentation below.

<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>Bridging ETH</td><td></td><td><a href="/pages/slaCIRKGpBcVOlEV4QMR">/pages/slaCIRKGpBcVOlEV4QMR</a></td></tr><tr><td><i class="fa-coin-blank">:coin-blank:</i></td><td>Bridging ERC-20 Token</td><td></td><td><a href="/pages/wmqn3eYOA9I9mlsTp1Kp">/pages/wmqn3eYOA9I9mlsTp1Kp</a></td></tr></tbody></table>

## Bridge Service

You can move assets easily and quickly using a variety of bridge services. For more details, please refer to the [Bridges](/giwa-chain/en/tools/bridges.md) page.


---

# Agent Instructions: 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.giwa.io/giwa-chain/en/get-started/bridging.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.