Symbiosis BridgeV2 Contract

Symbiosis core smart contracts: BridgeV2 contract as a proxy between Synthesis/Portal contracts and the Symbiosis realayer network.

• If you are curious to see the Symbiosis Protocol in action, check out Symbiosis WebApp.

• The Symbiosis Core Smart Contracts are open source and available at https://github.com/symbiosis-finance/core-contracts.

• For security audits, please refer to Security Audits.

In the previous article: Symbiosis Mint-Burn Process, we explained the core concept of cross-chain operations:

• When the Portal locks tokens on one blockchain, Synthesis mints tokens on another blockchain.

• When Synthesis burns tokens on one blockchain, the Portal releases tokens on the original blockchain.

Now let’s take a closer look at the BridgeV2 contract.

An instance of the BridgeV2 contract is deployed on each blockchain supported by Symbiosis. It acts as a proxy between the Rrelayers Network and the Portal/Synthesis contracts.

BridgeV2 accepts calls from two sources:

1. Portal/Synthesis contracts deployed on the same blockchain When invoked by these contracts, BridgeV2 emits an Oracle request (i.e., a smart contract event) that contains all the necessary data and instructions to carry out the corresponding operation on the destination blockchain.

2. Relayers Network These are off-chain entities submitting transactions signed with an MPC (multi-party computation) key. The corresponding MPC address is stored in the BridgeV2 contract. When BridgeV2 is called via such a transaction, it executes the instructions included in the transaction calldata on-chain.

Scheme 1 below illustrates the BridgeV2 workflow during cross-chain operations:

Scheme 1. BridgeV2 routine.

Relayers Network: See Relayers network for more details.