# Pass an arbitrary call data cross-chain through deBridge This instruction shows how to send a message/call_data through deBridge protocol to perform a simple cross-chain swap into Kovan blockchain using Uniswap liquidity pool ### Create liquidity pool in Kovan network: Bridge some asset (e.g. BNB) from BSC to Kovan through https://testnet.debridge.finance/ in order to receive wrapped asset (deWBNB) in Kovan network Create liqudity pool at Uniswap for deWBNB/ETH pair in Kovan: ![](https://i.imgur.com/9I5gLhT.png) ### Prepare call_data for the swap Open regular swap widget and increase slippage tolerance parameter to make sure your transaction will not be reverted https://app.uniswap.org/#/swap ![](https://i.imgur.com/UP21Ydv.png) Select deAsset pair where liquidity was added and specify amount to be swapped ![](https://i.imgur.com/gN5QqOM.png) Click **Swap** button and open transaction data in Metamask window that popped up ![](https://i.imgur.com/PmiKhCa.png) Copy Uniswap router address and transaction data. You can also form transaction data manually based on the method of Uniswap contract: > swapExactTokensForETH(uint amountIn, uint amountOutMin, address[] calldata path, address to, uint deadline) **deBrige UI** Go to https://testswap.debridge.finance/ (version of deBridge UI for developers that also allows passing call_data) Put in the following data: - Network from: **BSC** - Network to: **Kovan** - Asset to be sent: **BNB** - Fill in amount to be bridged so that **received amount** exceeds the amount from the formed Uniswap transaction - Enable Bridge & Transfer option - Specify Uniswap Router address and call_data that was formed before ![](https://i.imgur.com/BLASLYM.png) Press confirm transfer and sign transaction ![](https://i.imgur.com/P16JeSi.png) You can track status of your cross-chain transaction in [deBridge explorer](https://explorer.debridge.finance/). **Call data** field of transaction reflects passed transaction data that will be executed in the target chain. ![](https://i.imgur.com/B5bnl9J.png) Keeper will claim and execute your transaction in the target chain if specified execution fee covers execution gas costs. Once tx executed you can also find it in Etherscan Example: https://kovan.etherscan.io/tx/0x8a79c7dec4998090c21d911077c46f9ef0181d775a310804a3c80311e5e28626 ![](https://i.imgur.com/AeGCSpP.png) Feel free to reach out to deBridge team in case you will have any problems
Last changed by  
 
Alex Smirnov
373

Read more

GMX-DLN integration

GMX is a decentralized exchange that allows users to swap tokens and leverage trading with long or short positions. Currently, it's functional on a few blockchains only. We propose extending the exchange's capabilities with the integration of the deBridge value transfer layer, DLN. DLN is an infrastructure product built on top of deBridge that allows to trade any liquidity and simultaneously pass call data between any chains. The integration will allow GMX to enable global accessibility and enable protocols and users from any chains that are supported by deBridge (including Solana) to open up positions and interact with GMX without the cost of additional deployments and the need to extend the existing architecture as the changes will mainly involve their frontend. Proposal The technical idea of the implementation would be to use DLN as a middle layer for cross-chain interactions. For example, it can allow users to trade any asset on one chain to USDC on Avalanche or Arbitrum and open up a position on GMX in the same transaction on behalf of a Safe account. The overall idea is to create a UI client for GMX so that users can connect any wallet on any chain and seamlessly interact with GMX while abstracting away the need to have gas and wallets, and even avoiding the need of switching chains. To access the system in a multi-layer way, the Safe account is at first deployed for the user on the networks he would like to interact on (See image below). For example, if the user wants to use Arbitrum as the destination chain, the Safe account is deployed to interact with GMX contracts on Arbitrum from any chain supported by deBridge. After this step, the user won't need to have gas tokens in the chains where GMX is deployed. Users will be able to interact with protocols from any desired chain while signed transactions will be executed by DLN on behalf of their Safe accounts. In DLN transactions are executed instantly without the need to wait for guaranteed finality, so UX will be similar to the one that users have when trading natively on Arbitrum

2/28/2023
Integration of deBridge Adapter into Multi-Bridge Implementation

In deBridge, we'd like to express our support for a multi-bridge Implementation developed by Celer team. We made a pull request (PR) where developed an adapter that adds support for deBridge infrastructure into the proposed multi-bridge framework. To test out integration, we performed a mainnet deployment of all smart contracts in BNB and Polygon Chains and made a test updateQuorumThreshold() operation initiated in the MultiBridgeSender contract in BNB Chain and successfully settled in the MultiBridgeReceiver Polygon. Transaction details can be found in deBridge explorer. The source code and additional details are available here: https://github.com/celer-network/sgn-v2-contracts/pull/232 We would like to encourage all bridge teams that support multi-bridge Implementation to make similar pull requests, adding their bridge adapter to the framework

2/2/2023
Read more from Alex Smirnov
Published on HackMD