Bridge API
Explore Avail DA's Bridge API endpoints for cross-chain message and token transfers between Avail and Ethereum.
Warning
DIRECT BRIDGE CALLS ONLY
Avail-to-Ethereum bridge sends must be submitted as direct
Avail-to-Ethereum bridge sends must be submitted as direct
vector.sendMessage / vector_sendMessage transactions.Wrapped bridge sends are rejected during transaction validation. Do not submit bridge sends through proxy, multisig, scheduler, utility.batch, utility.batchAll, or any other call wrapper.This restriction only applies to bridge send transactions. Normal non-bridge proxy, multisig, scheduler, and batch transactions continue to work as expected.Note
BEFORE WE START
- The Avail VectorX bridge can be used to pass messages and tokens between
Avail DA Turing - Ethereum Sepolia (testnet bridge), and between Avail DA mainnet - Ethereum mainnet (mainnet bridge). - You can check out a complete list of endpoints required to use the bridge API in the networks page.
Note
TWO WAYS OF USING THE BRIDGE API
- You can build and run the bridge API locally using the instructions outlined in this repo: availproject/bridge-api
- We have included two public endpoints for the bridge API in the networks page that you can use. For the sake of simplicity that is what we will be using in this guide.
- For the sake of simplicity, we will use the Turing testnet bridge API in this guide.
Setting up the dev environment
- To use the Avail bridge API with
curl, you just need to havecurlinstalled on your system. You can check if it is installed by running:
curl --version- If this does not work, go to curl's website to install it on your system.
How is this guide?