> For the complete documentation index, see [llms.txt](https://docs.kcc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kcc.io/individuals/bridge-assets/bridge-assets-from-others-chains.md).

# Bridge assets from others chains

### Supported cross-chain bridge

Users can using "cross-chain bridges" to transfer your assets into your KCC Chain wallet. Below we provide a list of cross-chain bridges that support the KCC Network.

| No | Cross-chain Bridge Name | Official Website                     |
| -- | ----------------------- | ------------------------------------ |
| 1  | KCC Bridge              | <https://www.kcc.io/bridge/transfer> |
| 2  | O3 swap                 | <https://o3swap.com/>                |

### The Addresses of  Pegged-Tokens On KCC

When you transfer foreign tokens (which are not issued on the KCC chain) from other chains to the KCC network, they become the corresponding pegged tokens.&#x20;

Here are pegged token addresses of some common tokens on the KCC mainnet:&#x20;

<table><thead><tr><th width="210">Name</th><th>Address</th></tr></thead><tbody><tr><td>USDT</td><td>0x0039f574eE5cC39bdD162E9A88e3EB1f111bAF48</td></tr><tr><td>USDC</td><td>0x980a5AfEf3D17aD98635F6C5aebCBAedEd3c3430</td></tr><tr><td>BTCK</td><td>0xfA93C12Cd345c658bc4644D1D4E1B9615952258C</td></tr><tr><td>ETH</td><td>0xf55aF137A98607F7ED2eFEfA4cd2DfE70E4253b1</td></tr></tbody></table>

You can find the full list of pegged tokens on [Github](https://github.com/kcc-community/kcc-peg-token#mainnet).&#x20;


---

# 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.kcc.io/individuals/bridge-assets/bridge-assets-from-others-chains.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.