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

# Bridge

Bridge KII between Kiichain and other networks. Includes Hyperlane warp route addresses and Nexus as a bridging option.

KII can move between Kiichain and supported external chains through Hyperlane warp routes. Use the addresses below to verify you are interacting with the correct contracts, and use [Nexus](https://nexus.hyperlane.xyz/?origin=kiichain\&originToken=KII\&destination=bsc\&destinationToken=KII) as a UI option for bridging assets.

## Bridge with Nexus

[Nexus](https://nexus.hyperlane.xyz/?origin=kiichain\&originToken=KII\&destination=bsc\&destinationToken=KII) is a Hyperlane-powered bridge interface. You can bridge KII between Kiichain and connected chains such as BNB Smart Chain (BSC), Polygon, Base, Ethereum, and Mantle.

Always confirm the destination chain and token address before signing a transaction.

## KII addresses on other chains

Official Hyperlane warp route configuration (source of truth):

* [Hyperlane registry — KII / kiichain-config.yaml](https://github.com/hyperlane-xyz/hyperlane-registry/blob/main/deployments/warp_routes/KII/kiichain-config.yaml)

| Chain                 | Contract address                             | Type                        |
| --------------------- | -------------------------------------------- | --------------------------- |
| Kiichain              | `0xEEC6574eAbBa52bac3f0277F2cD5Ac7e67197886` | Native (EvmHypNative)       |
| BNB Smart Chain (BSC) | `0xEEC6574eAbBa52bac3f0277F2cD5Ac7e67197886` | Synthetic (EvmHypSynthetic) |
| Polygon               | `0xEEC6574eAbBa52bac3f0277F2cD5Ac7e67197886` | Synthetic (EvmHypSynthetic) |
| Ethereum              | `0xEEC6574eAbBa52bac3f0277F2cD5Ac7e67197886` | Synthetic (EvmHypSynthetic) |
| Mantle                | `0xEEC6574eAbBa52bac3f0277F2cD5Ac7e67197886` | Synthetic (EvmHypSynthetic) |
| Base                  | `0x3EBA6644819546C44Eb3e7c3A92f034f921dcA80` | Synthetic (EvmHypSynthetic) |

On Kiichain, the warp route represents native KII. On other chains, the listed address is the synthetic KII token contract for that network.

Decimals are `18` on all listed chains. Symbol: `KII`.

## Safety checklist

* Prefer the Hyperlane registry link above when confirming addresses.
* Base uses a different contract address than the other listed chains.
* Do not send KII to an unverified or manually pasted address from unofficial sources.
* If a UI and the registry disagree, trust the [Hyperlane registry config](https://github.com/hyperlane-xyz/hyperlane-registry/blob/main/deployments/warp_routes/KII/kiichain-config.yaml).


---

# 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.kiiglobal.io/docs/learn/getting-started/bridge.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.