xAsset Bridge

Upgrade you token into multi-chain world

xAsset Bridge helps projects Bridge Token to Different Chains, holders of the token could quickly and safely wrap their tokens to different chains. We supports two fungible token bridging methods for different token types

Token Type

• Protocol-Owned Token

  • XY Finance will help build an independent bridge to bridge your token to the desired chains.

  • The protocol team can retain token ownership. (eg. LOOT, NUM, and SINGLE)

• Non-Protocol-Owned Token

  • XY Finance will build the shared bridge (eg. PEPE, MOG, USDC and ETH) between major chains and partnered appchains (eg. OX Chain). Any appchain can request an extension of the bridge to their appchain.

  • XY Finance will retain token ownership to ensure security across our partnered appchains.

  • This type of token is only compatible with the Mint & Burn method

  • If you want to build an independent bridge, it is only permitted for specific tokens, such as stablecoins and major tokens like ETH and BTC.

  • The newly deployed token for shared bridge will follow the following token standard.

https://github.com/XY-Finance/xy-protocol/blob/master/contracts/token-bridge/XYERC20V2.sol

Bridging Method

• Mint&Burn Method: The token will interact with xAsset Bridge by mint&burn manner on the chain. If the mint&burn method is adopted on the chain, while users bridge the token to other chains, the token will be transferred to the xAsset Bridge contract deployed on the chain and burned. While users bridge the token back from other chains, the token will be minted from the xAsset Bridge contract and sent to the user.

• Pool-based Method: The token will interact with the xAsset Bridge by lock / unlock manner on the chain. If the Pool-based method is adopted on the chain, while users bridge the token to other chains, the token will be locked to the xAsset Bridge contract deployed on the chain. While users bridge the token back from other chains, the token will be unlocked from the xAsset Bridge contract and sent to the user.

To determine the appropriate scenario and method for your project, please evaluate the following information to choose the scenario and method that best suits your needs:

• If your token is deployed only on 1 chain:

  • And if you want to deploy token(s) to a new chain -> Scenario1 : Mint&Burn Method

• If your tokens are already deployed on N chains:

  • And if you want to enable token cross-chain functionality on these N chains -> Scenario2 : Pool-based

  • And if you want to deploy tokens to a new chain and enable token cross-chain functionality on n+1 chains -> Scenario 3: Combination of both methods.

Integration Flow

Step 1: Determine Your Bridging Method and Token Type

Choose your desired bridge method and token type and contact us through this form

Step 2: Implementation Phase

Once you have determined step1, you can proceed with the implementation phase.

Protocol-Owned Token

Scenario 1 : Mint&Burn Method

Here's what you need to do:

• Follow How to Develop Under XY Standards to deploy the token contract on the desired chain(s) and send your token address to the XY team.

• XY team will provide you relay contract address , which you will need to set as the minter.

• XY team will implement the cross-chain bridging mechanism (usually takes 2 weeks to complete)

• You will receive a front-end bridge that allows users to bridge your token through XY Finance.

Scenario 2 : Pool-based

Here's what you will proceed

• Send your current token address to the XY team.

• XY team will implement cross-chain bridging mechanism (Usually takes 2 weeks to complete)

• Follow How to Deposit / Withdraw Liquidity to provide initial liquidity on the chain where you have deployed your token.

• You will receive a front-end bridge that allows users to bridge your token through XY Finance.

Scenario 3 (Combination of both methods) and Other Cases

• Contact us through this form to know more detail

Non-Protocol-Owned Token

It is only compatible with the Mint & Burn method, and the newly deployed token will follow the following token standard.

• Confirm the token you want to deployed

• XY team will implement the cross-chain bridging mechanism (usually takes 2-4 weeks to complete)

• You will receive a front-end bridge that allows users to bridge your token through XY Finance.

Commonly asked questions:

1. How does xAsset Bridge charge fees?

The integration of xAsset Bridge does not charge any fees. However, when users utilize XY Finance in the future to bridge your project's tokens, we will charge a certain fee from it. To learn about the pricing details of the xAsset Bridge, please refer to the following page and check the xAsset Bridge session

🌉yBridge Fee Information

2. What security measures does xAsset Bridge have?

• Validators: The consensus mechanism of xAsset Bridge incorporates multiple validators, which support and consistently validate data requests from executors as needed.

• Contract Independence: The Token Contact will be deployed by the project itself, while the Relay Contract will be deployed by XY, but it will be independent and non-upgradable, ensuring the security of the entire process.

3. If the token has taxes, can I integrate xAsset Bridge?

In the regular integration process, once you provide your token address to the XY team, we will deploy the relay contract for the xAsset Bridge service. If your token involves transfer taxes, you need to whitelist the relay contract address as both the 'sender' and 'receiver' in order to exempt these taxes during the bridge process.