> For the complete documentation index, see [llms.txt](https://docs.goliath.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goliath.net/defi/slingshot/bridge.md).

# Bridge

## Overview

Bridge transfers assets between Ethereum Sepolia and Goliath Testnet.

**Access:** <https://slingshot.goliath.net/#/bridge>

## Supported Bridge Assets

| Asset   | Sepolia -> Goliath | Goliath -> Sepolia | Notes                                               |
| ------- | :----------------: | :----------------: | --------------------------------------------------- |
| **ETH** |        Live        |        Live        | Sepolia native ETH <-> bridged ETH token on Goliath |
| **XCN** |        Live        |        Live        | Sepolia ERC20 XCN <-> Goliath native XCN            |

## Contract Addresses

| Contract                | Network | Address                                      |
| ----------------------- | ------- | -------------------------------------------- |
| **Bridge**              | Sepolia | `0xA9FD64B5095d626F5A3A67e6DB7FB766345F8092` |
| **Bridge**              | Goliath | `0x2c1d218B5a97a26D144ffd12d5C813590f93FFEB` |
| **Sepolia XCN (ERC20)** | Sepolia | `0x7a8adc542A35c93da263A188367F4bF4c445B8E9` |
| **Bridged ETH token**   | Goliath | `0xEd02AA7dd3f105EDab8702D859781CAfF111324b` |

## User Flow

### Sepolia -> Goliath

1. Open `/#/bridge` and connect wallet to Sepolia
2. Choose token and amount
3. Confirm bridge transaction
4. Wait for required confirmations and relayer finalization
5. Switch to Goliath to verify receipt

### Goliath -> Sepolia

1. Connect wallet to Goliath
2. Approve token (ERC20 route, first time only)
3. Submit bridge/burn transaction
4. Wait for confirmations and relayer finalization
5. Switch to Sepolia and verify receipt

## Status and Monitoring

Bridge status API:

`https://testnet.mirrornode.goliath.net/bridge/api/v1`

| Endpoint               | Method | Description                  |
| ---------------------- | ------ | ---------------------------- |
| `/status/{depositId}`  | GET    | Status of deposit operation  |
| `/status/{withdrawId}` | GET    | Status of withdraw operation |
| `/history/{address}`   | GET    | Bridge history for address   |

## Developer Notes

* Typical functions exposed by bridge contracts are `depositNative`, `deposit`, and `burn`.
* Always verify ABI and addresses against explorer before deployment.
* For staking-based Sepolia to Goliath movement, use the dedicated [Migrate](/defi/slingshot/migrate.md) flow.
* For full step-by-step integration — contract ABIs, REST API, code examples — see the [**Bridge Integration Developer Guide**](/developer-guide/bridge.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, and the optional `goal` query parameter:

```
GET https://docs.goliath.net/defi/slingshot/bridge.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.