Symbiosis Documentation
Symbiosis NestDeveloper ToolsGo to Bridge & Swap
  • Getting Started with Symbiosis
  • Symbiosis: Frequently Asked Questions
  • Main concepts
    • Glossary
    • Symbiosis SIS Token
    • Symbiosis sTokens
    • Symbiosis: Cross-Chain Swaps
      • Symbiosis: To/From BTC
      • Symbiosis: To/From TON
    • Cross-Chain Zaps
    • Symbiosis as Interchain Communication Protocol
    • Symbiosis & Fees
    • Security Audits
    • Bug Bounty Program
  • Governance
    • 🚩Governing Symbiosis
  • User Guide (WebApp)
    • Symbiosis WebApp
    • Bridge with Symbiosis: sUSDC, sWETH, sWBTC
    • Swap & Bridge with Symbiosis
    • Swap & Bridge To and From Bitcoin
    • Swap & Bridge To and From Tron
    • Stuck Transactions
    • Bridging SIS Token
    • Symbiosis Liquidity Pools
    • Withdrawing from Symbiosis Octopool
    • Cross-Chain Zaps
    • Common Issues and Solutions
    • Where are My Tokens?
    • Symbiosis Explorer
    • More about Slippage Tolerance
  • Reward Programs
    • Symbiosis Reward Programs
    • Farming on Octopools
    • SIS LP Farming
    • veSIS
  • Cross-chain liquidity engine
    • Symbiosis Core Smart Contracts
    • Symbiosis Mint-Burn Process
    • Symbiosis BridgeV2 Contract
    • Symbiosis Routing Contracts
    • Symbiosis & Emergencies
    • Symbiosis Octopools
  • Relayers network
    • Symbiosis Relayers Network
    • Symbiosis PoS Staking & Symbiotic Staking
      • Symbiosis X Symbiotic: SIS Restaking Vault User Guide
    • Relayers Network: Architecture and Operations
    • Symbiosis Relayer Node
    • Symbiosis Relayers Network: Emergencies
  • Developer Tools
    • Symbiosis Developer Tools
    • Symbiosis API
    • Symbiosis JS SDK
      • JS SDK Types
      • JS SDK Configuration
  • Miscellaneous
    • Symbiosis on Testnet
    • Symbiosis Multisig Address on Scroll
    • Symbiosis v1 vs. v2
    • Gasless Crypto Exchanges
  • Follow Us
  • Symbiosis | X
  • Symbiosis | Telegram
  • Symbiosis | Blog
  • Symbiosis | Publish0x
  • Symbiosis | Discord
  • Symbiosis | Linkedin
  • Symbiosis | Github
Powered by GitBook
On this page

Was this helpful?

  1. Cross-chain liquidity engine

Symbiosis BridgeV2 Contract

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

PreviousSymbiosis Mint-Burn ProcessNextSymbiosis Routing Contracts

Last updated 4 months ago

Was this helpful?

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

  • Symbiosis core smart contracts are open source and available at

  • For security audits of Symbiosis core smart contract, please refer to Security Audits.

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

  • Whenever Portal locks tokens on one blockchain -> Synthesis mints tokens on another blockchain.

  • Whenever Synthesis burns tokens on one blockchain -> Portal releases tokens on another blockchain.

Let's take a closer look at the BridgeV2 contract.

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

BridgeV2 accepts calls from:

  1. The Portal/Synthesis contracts locked on the same blockchain When BridgeV2 is invoked by these contracts, it issues an Oracle request (an event in terms of smart contracts) that contains all the necessary data and instructions to accomplish the operation on the corresponding destination blockchain.

  2. Relayers: transactions signed with an MPC key, the MPC address for this key is stored in the BridgeV2 contract. When BridgeV2 is invoked by such a transaction, the instructions from the transaction calldata get executed on the blockchain.

Scheme 1 below shows the BridgeV2 routine during cross-chain operations:

In addition, Portal/Synthesis sends cross-chain fees collected from users to BridgeV2. More information about fee collection can be found here: Symbiosis & Fees.

About relayers. The Symbiosis relayers network is an off-chain part of the Symbiosis protocol. The main purpose of the network is to provide fast, accurate, and secure transfer of information about cross-chain operations conducted via the Symbiosis protocol. See Relayers network for more details.

Symbiosis WebApp
https://github.com/symbiosis-finance/core-contracts
Scheme 1. BridgeV2 routine.