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

# XVS Bridge

The XVS bridge remains an active LayerZero OFT V2 deployment. This section is pinned to the stable [`token-bridge` v2.7.0 tag](https://github.com/VenusProtocol/token-bridge/tree/v2.7.0), rather than the moving `develop` branch.

The contract names use `ProxyOFT` in the LayerZero token-model sense. `XVSProxyOFTSrc` and `XVSProxyOFTDest` are not EIP-1967 upgradeable proxies in the tagged mainnet artifacts. `XVSBridgeAdmin` is the transparent proxy.

| Network role                                                                     | Contracts                                            | Token behavior                                                                                               |
| -------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| BNB Chain source                                                                 | Native XVS, `XVSProxyOFTSrc`, `XVSBridgeAdmin`       | XVS is locked on outbound transfers and released on inbound transfers                                        |
| Ethereum, Arbitrum, opBNB, Optimism, Base, zkSync Era, and Unichain destinations | Omnichain `XVS`, `XVSProxyOFTDest`, `XVSBridgeAdmin` | XVS is burned on outbound transfers and minted on inbound transfers, subject to the TokenController mint cap |

`BaseXVSProxyOFT` is abstract and is not a deployment address. `TokenController` is inherited by the destination-chain XVS token. The bridge uses LayerZero V1 `uint16` endpoint IDs (named chain IDs in the ABI) and OFT V2 APIs; these must not be replaced with EVM chain IDs, LayerZero V2 EIDs, or OApp selectors.

LayerZero marks V1 deprecated for new integrations in its [V1 deployment reference](https://docs.layerzero.network/v1/deployments/deployed-contracts). The existing Venus bridge is nevertheless active. “Deprecated upstream transport” and “retired Venus product” are different lifecycle claims.

A deployment on two networks does not by itself prove that their trusted-remote path is enabled. For user transactions, use the networks exposed by the current Venus interface and verify the selected route, limits, mint capacity, and native-gas fee immediately before signing. See the [XVS omnichain registry](/deployed-contracts/xvs-omnichain.md) for addresses.


---

# 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-v4.venus.io/technical-reference/reference-xvs-bridge.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.