# Cross-chain Bridging

$VC is native to VinuChain and bridged to BNB Chain (BSC).

### Token Address:

Here are the addresses:

1. **VC (VinuChain):** [**native gas coin does not have a contract.**](https://mainnet.vinuscan.com/)

* As it is the native gas coin of the VinuChain protocol, it does not have a contract address.
* For applications that require its contract address, you can simply omit it / leave it blank.
* For applications on the VinuChain network, you can wrap VC into [wVC](https://vinuexplorer.org/token/0xEd8c5530a0A086a12f57275728128a60DFf04230).

2. **VC (BSC):** [**0x2Bf83D080d8Bc4715984e75E5b3D149805d11751**](https://bscscan.com/token/0x2Bf83D080d8Bc4715984e75E5b3D149805d11751)

* $VC on BNB Chain is a wrapped version of VC.
* The only way $VC can circulate on BSC is by first bridging it from VinuChain to BSC.
* Therefore, the total real supply of $VC across all chains is always the same as the total supply of $VC on VinuChain.
* $VC sitting in bridge hot/cold wallets on BSC are simply placeholder supply (not circulating / not 'real').

### Bridge

You can use [**Wanbridge** ](https://bridge.wanchain.org/#/?asset=VC\&from=VinuChain)to conduct cross-chain transfers of $VC:

* <https://bridge.wanchain.org/#/?asset=VC&from=VinuChain>


---

# 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://vinu.gitbook.io/vinuchain/technical-docs/cross-chain-bridging.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.