Phala Network Docs
  • Home
    • 👾Phala Network Docs
  • Overview
    • ⚖️Phala Network
      • 💎Phala Cloud
      • 🥷Dstack
      • 🔐GPU TEE
    • 💎PHA Token
      • 🪙Introduction
      • 👐Delegation
        • Delegate to StakePool
        • What is Vault
        • What is Share
        • WrappedBalances & W-PHA
        • Examples of Delegation
        • Use Phala App to Delegate
        • Estimate Your Reward
      • 🗳️Governance
        • Governance Mechanism
        • Join the Council
        • Voting for Councillors
        • Apply for Project Funding
        • Phala Treasury
        • Phala Governance
        • Setting Up an Account Identity
  • Phala Cloud
    • 🚀Getting Started
      • Create Your Phala Cloud Account
      • Your First CVM Deployment
      • Explore Templates
        • Launch an Eliza Agent
        • Start from Template
    • 🪨TEEs, Attestation & Zero Trust Security
      • Attestation
      • Security Architecture
    • 🥷Phala Cloud User Guides
      • Deploy and Manage CVMs
        • Deploy CVM with Docker Compose
        • Set Secure Environment Variables
        • Deploy Private Docker Image to CVM
        • Debugging and Analyzing Logs
          • Check Logs
          • Private Log Viewer
          • Debug Your Application
        • Application Scaling & Resource Management
        • Upgrade Application
        • Deployment Cheat Sheet
      • Building with TEE
        • Access Your Applications
        • Expose Service Port
        • Setting Up Custom Domain
        • Secure Access Database
        • Create Crypto Wallet
        • Generate Remote Attestation
      • Advanced Deployment Options
        • Deploy CVM with Phala Cloud CLI
        • Deploy CVM with Phala Cloud API
        • Setup a CI/CD Pipeline
    • 🚢Be Production Ready
      • CI/CD Automation
        • Setup a CI/CD Pipeline
      • Production Checklist
      • Troubleshooting Guide
      • Glossary
    • 🔒Use Cases
      • TEE with AI
      • TEE with FHE and MPC
      • TEE with ZK and ZKrollup
    • 📋References
      • Phala Cloud CLI Reference
        • phala
          • auth
          • cvms
          • docker
          • simulator
      • Phala Cloud API & SDKs
        • API Endpoints & Examples
        • SDKs and Integrations
      • Phala Cloud Pricing
    • ❓FAQs
  • Dstack
    • Overview
    • Getting Started
    • Hardware Requirements
    • Design Documents
      • Decentralized Root-of-Trust
      • Key Management Service
      • Zero Trust HTTPs (TLS)
    • Acknowledgement
    • ❓FAQs
  • LLM in GPU TEE
    • 👩‍💻Host LLM in GPU TEE
    • 🔐GPU TEE Inference API
    • 🏎️GPU TEE Benchmark
    • ❓FAQs
  • Tech Specs
    • ⛓️Blockchain
      • Blockchain Entities
      • Cluster of Workers
      • Secret Key Hierarchy
  • References
    • 🔐Setting Up a Wallet on Phala
      • Acquiring PHA
    • 🌉SubBridge
      • Cross-chain Transfer
      • Supported Assets
      • Asset Integration Guide
      • Technical Details
    • 👷Community Builders
    • 🤹Hackathon Guides
      • ETHGlobal Singapore
      • ETHGlobal San Francisco
      • ETHGlobal Bangkok
    • 🤯Advanced Topics
      • Cross Chain Solutions
      • System Contract and Drivers
      • Run Local Testnet
      • SideVM
    • 🆘Support
      • Available Phala Chains
      • Resource Limits
      • Transaction Costs
      • Compatibility Matrix
      • Block Explorers
      • Faucet
    • ⁉️FAQ
  • Compute Providers
    • 🙃Basic Info
      • Introduction
      • Gemini Tokenomics (Worker Rewards)
      • Budget balancer
      • Staking Mechanism
      • Requirements in Phala
      • Confidence Level & SGX Function
      • Rent Hardware
      • Error Summary
    • 🦿Run Workers on Phala
      • Solo Worker Deployment
      • PRBv3 Deployment
      • Using PRBv3 UI
      • PRB Worker Deployment
      • Switch Workers from Solo to PRB Mode
      • Headers-cache deployment
      • Archive node deployment
    • 🛡️Gatekeeper
      • Collator
      • Gatekeeper
  • Web Directory
    • Discord
    • GitHub
    • Twitter
    • YouTube
    • Forum
    • Medium
    • Telegram
Powered by GitBook
LogoLogo

Participate

  • Compute Providers
  • Node
  • Community
  • About Us

Resources

  • Technical Whitepaper
  • Token Economics
  • Docs
  • GitHub

More

  • Testnet
  • Explorer
  • Careers
  • Responsible Disclosure

COPYRIGHT © 2024 PHALA.LTD ALL RIGHTS RESERVED. May Phala be with you!

On this page
  • What is SubBridge?
  • SygmaBridge has been integrated into SubBridge
  • About Sygma protocol
  • What are the differences between SygmaBridge and ChainBridge?
  • Security Concern

Was this helpful?

Edit on GitHub
  1. References

SubBridge

PreviousAcquiring PHANextCross-chain Transfer

Last updated 1 year ago

Was this helpful?

What is SubBridge?

SubBridge is the cross-chain router of the parachains, bridging Dotsama and Ethereum and assets in other ecosystems.

SubBridge is based on the “XCM + EVM-Bridges cross-chain protocol” to realize cross-chain transmission of assets and information. Currently, ChainBridge and SygmaBridge are integrated as our EVM-Bridge solution.

In August 2021, Phala launched the first parachain-Ethereum smart contract bridge on Substrate, which can support the mutual transfer of parachain assets between Ethereum and parachain. In the future, parachains in the Substrate ecosystem can integrate and use SubBridge to achieve asset transaction and messages migration with other ecosystems (e.g., EVM) , and promote the prosperity of the Polkadot’s ecosystem.

SygmaBridge has been integrated into SubBridge

About Sygma protocol

is a multi-purpose interoperability layer that supports developers in building cross-chain dApps. Sygma now has supported both EVM chains and Substrate chains. is developed by the Sygma team and Phala team together, which is fully compatible with XCM protocol, bringing the maximum flexibility for the Substrate parachains.

What are the differences between SygmaBridge and ChainBridge?

SygmaBridge is the updated version of ChainBridge, which use an MPC-based relayer forward messages between chains, while ChainBridge is based on multiple voters confirming crosschain transaction on destchain. Compared with ChainBridge, SygmaBridge distinctly decreased the fee cost, because now we only need to send one transaction to destchain to complete the whole operation.

Destination of using SygmaBridge

Since currently both SygmaBridge and ChainBridge exist, users can choose which bridge to use, even SubBridge UI always uses SygmaBridge for PHA transfer. The difference between using ChainBridge and SygmaBridge only detdetermd by the way we construct the MultiLocation of the destination.

  • For using SygmaBridge

MultiLocation::new(1, X4(Parachain(2035), GeneralKey('sygma'), GeneralIndex(ethereumChainId), GeneralKey(recipientAddress))
  • For using ChainBridge

MultiLocation::new(1, X4(Parachain(2035), GeneralKey('cb'), GeneralIndex(ethereumChainId), GeneralKey(recipientAddress))

Security Concern

The security of the SubBridge is of prior concern. In terms of EVM compatibility, SubBridge has its own solution with the following security advantages:

  • SubBridge has passed an audit by Certik, a top blockchain security company (Per the audit report, there are no critical or major errors or known vulnerabilities; some minor concerns have been solved or addressed);

  • Admin takes multi-signature management to guarantee asset security;

  • SubBridge consists of several relayers, the operation is guaranteed when there is a single node out of service.

Read the for more details on code auditing.

🌉
Sygma
The Substrate pallet
following section