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

# Token Bridge

Blockchain bridges are protocols that facilitate the transfer of assets and data between different blockchain networks. In terms of functionality, a cross-chain bridge converts a native asset from one blockchain into its corresponding asset on another blockchain.

## KUB Bridge

[KUB Bridge](https://bridge.kubchain.com/en) is the native bridge of the KUB network. Users can bridge assets from selected networks to KUB by using our protocol. The current networks that are supported on KUB Bridge include:

* [Ethereum](https://ethereum.org/)
* [BNB Smart Chain](https://www.bnbchain.org/)
* [JFIN Chain](https://www.jfincoin.io/about-jfin-chain)

## Quickstart Guide

This quickstart is for users who want to deposit KUB or any ERC-20 tokens from selected networks to KUB or withdraw from KUB to selected networks. The only prerequisite for this quickstart is to have a Web3 wallet installed.

### Step 1: Get Native Tokens

You will need the native tokens of the source network to transfer your assets to the destination network. For example, if you want to bridge assets from Ethereum to KUB, you'll need ETH on Ethereum to start the process.

There are several ways to obtain the native currency:

* Using a supported centralized exchange, which allows you to purchase **ETH** and withdraw it to your wallet.
* Using an on-ramp service, which allows you to purchase **ETH** and send it directly to your wallet.

### Step 2: Add Network <a href="#step-2-add-the-preferred-network-to-your-wallet" id="step-2-add-the-preferred-network-to-your-wallet"></a>

You'll also need to add the desired network's RPC endpoint to your wallet. [KUB](/about-kub/connect-to-kub.md) can be added using any Web3 wallet that supports custom RPC. Most Web3 wallets should support Ethereum by default. For BNB Smart Chain and JFIN Chain, you should find their RPC details on their website to add their network to your Web3 wallet.

### Step 3: Initiate the Deposit

Visit the [KUB Bridge](https://bridge.kubchain.com/en) and log in using your wallet. Make sure you are connected to the source network (from which you want to deposit your assets) at the top of the page. Next, select the destination network (where you want your assets to go), e.g., Ethereum to KUB.

Choose the token you wish to bridge from the token drop-down menu. Enter the amount of **KUB** or ERC-20 tokens you want to transfer in the **From** box, and then press the **Bridge** button. Follow the instructions provided by your Web3 wallet.

After submitting the transaction through your Web3 wallet, you can expect your funds to arrive on the destination chain within approximately 5-10 minutes (depending on the chain congestion). Additionally, ensure your wallet is set to the destination chain so you can see your funds when they arrive.


---

# 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.kubchain.com/tools/token-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.