# Cross-Chain Transfer

Using Clover mobile wallet or extension wallet. You can cross-chain transfer you native CLV token to Ethereum and BSC. This is an automatic process, without the need to claim.

## CLV Tokens

Currently, there are three kinds of CLV assets:\
\
**WARNING: DO NOT send CLV cross-chain transfer to any of the addresses listed below or you will risk losing your assets, these are only example addresses or contract addresses which the team DOES NOT have access to. Please send the cross-chain transfer only directly to your own address or input address on an exchange account.**&#x20;

### 1. CLV native token

This is the token issued on Clover mainnet. The address format is like: **5CyngUVPJD2MnAbrYR9F72CA5YX1VekR6ip9n2QuuBWcKXKB**. You can view your balance in Subscan,  the url is like (you need to change the address to your own!):  <https://clover.subscan.io/account/5CyngUVPJD2MnAbrYR9F72CA5YX1VekR6ip9n2QuuBWcKXKB>

### 2. CLV erc20 token

This is the erc20 token deployed on Ethereum. The address format is like: **0xcdbf90174493dcc418f177a4d7b2604a95997e1f**. The smart contract address is: [0x80C62FE4487E1351b47Ba49809EBD60ED085bf52](https://etherscan.io/address/0x80C62FE4487E1351b47Ba49809EBD60ED085bf52)

### 3. CLV bep20 token

This is the bep20 token deployed on BSC. The address format is like: **0xcdbf90174493dcc418f177a4d7b2604a95997e1f**. The smart contract address is: [0x09E889BB4D5b474f561db0491C38702F367A4e4d](https://bscscan.com/address/0x09E889BB4D5b474f561db0491C38702F367A4e4d)

## CLV Native Token

If you install Clover extension wallet, you should see Clover token:

![](/files/7yAzi7SBUERWgiU73BWM)

Please note that this is Clover native token (the address format has a prefix of 5)

## Add Clover Wrapped Tokens

When you wan to make a cross-chain transfer, you may need to add Clover wrapped tokens on target networks, such as Ethereum, BSC. You can click the 'Add Token' button on the bottom of the main page:

![](/files/PkkvBSk7tV0ppY6YwsEX)

## Make a Cross-Chain Transfer

If you have the knowledge of the three different CLV assets. It is time to make a cross-chain transfer. Let us give an example of **how to transfer native CLV token to Ethereum**. Here we will use extension wallet to explain (You can use mobile wallet to do cross-chain transfer as well !).

### 1. Click action button and select 'Cross Chain'

![](/files/eNuQStl4NBO2w95NpJBL)

### 2. Select target chain

You need to select Ethereum if you want to send CLV to your Ethereum account address. (**By default, CLV will be sent to BSC chain !**)

![](/files/kbosMxRys3ZJPyqqvGqT)

### 3. Input recipient address and send amount

Before you click Continue button, please make sure:

* The target chain is correct,  here we use BSC
* The recipient address is correct.
* The transfer amount (There is a minimum amount for cross-chain)

![](/files/mXA0v6ZkTtSBcUWOMJaX)

Please noted that:&#x20;

* If you cross-chain transfer CLV to Ethereum or BSC, there will be a cross-chain fee + transaction fee charged.  However, users don't need to pay ETH or BNB as cross-chain fee.
* You can check current cross-chain fee at <https://tx.clover.finance/>

### 4. Confirm your cross-chain transaction

Once you confirm and send the cross-chain transaction, you can just wait for your transaction to be successful. You can check your cross-chain transaction in your wallet or Clover's cross-chain transaction explorer at <https://tx.clover.finance/>

![Clover cross-chain transaction explorer](/files/-MeZDh6uwf-ZRPlD85iD)


---

# 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.clv.org/portal/wallet-and-dapp/clover-extension-wallet/cross-chain-transfer.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.
