DxChain Wiki
  • 👋Welcome to DxChain!
    • About $DX
    • About DxChain V3
    • Important Links
    • Project Updates
  • 📝The Basics
    • 📖DxChain V3 LitePaper
      • Notice
      • 1. Background
      • 2. Introduction
      • 3. The Ecosystem Powered by DxChain 3.0
      • 4. DxChain Design Principles & Architecture
        • 4.1 Fully Compatible with EVM
        • 4.2 DPoS Consensus Algorithm
        • 4.3 Cross Chain
        • 4.4 API Layer
        • 4.5 Blacklist Management
        • 4.6 P2P Decentralized Network Layer
        • 4.7 MPT + LevelDB
        • 4.8 Ellipse Curve Digital Signature Algorithm
      • 5. Economic system
      • 6. Governance
      • 7. Roadmap
      • 8. Follow Us
      • 9. Reference
      • 10. Risk Warning
  • 🪙Stake and Trade
    • About DX DPoS
    • How to Earn DX
    • Stake on DxChain
      • DxChain V3 Staking
      • Wallet
      • Consensus
      • How to Stake
    • Develop on DxChain
      • Compile and Run
      • On-chain Interaction
        • DPoS API
      • Smart Contract
      • Private Chain Construction
      • Genesis Block
      • Parameters Table
      • Mainnet
      • Testnet
      • Participate as Validator
    • Trade on DxChain
      • Cross Chain Bridge
  • ⛏️Liquidity Mining
    • Introduction of DxFarm
      • Functions
    • Tutorial
  • 🎙️Media Press
  • 🌏中文社区
    • 📙DxChain新人手册
    • 📜DxChain V3技术文档
      • 1. 背景
      • 2. 简介
      • 3. DxChain 3.0赋能的生态系统
      • 4. 技术的设计原理与架构
        • 4.1 全面兼容EVM
        • 4.2 DPOS共识机制
        • 4.3 跨链
        • 4.4 接口层
        • 4.5 严格的黑名单管理
        • 4.6 P2P分布式网络层
        • 4.7 MPT + LevelDB
        • 4.8 椭圆曲线数字签名算法
      • 5. 经济系统
      • 6. 社区治理
      • 7. 在社交媒体上与我们互动
      • 8. 参考文献
      • 9. 风险提示
      • 免责声明
    • ⛓️重要链接
    • 💻开发者文档
      • 关于DxChain 3.0
      • 钱包
      • 共识
      • 创世块
      • 开发者
        • 编译和运行
        • 链上交互
          • DPoS API
        • 智能合约
        • 私链搭建
        • 主网
        • 测试网
      • 参与区块验证
      • 参数表
    • 💎「DX V3去中心化质押」
      • 质押投票
        • 1)连接钱包
        • 2)进行投票
          • 可能出现的问题
        • 3)领取奖励
        • 4)取消投票
      • 成为节点
        • 1)部署节点
        • 2)申请节点
        • 3)同意节点
        • 4)成为节点
        • 5)取消节点
        • 6)恢复节点
      • 测试环境
    • 💎「DX V3托管社区」
      • 托管社区FAQ
      • 矿机节点
        • 1)进行投票
        • 2)领取奖励
        • 3)取消投票
      • 超级节点
        • 1)成为超级节点
        • 2)修改奖励比例和质押数
        • 3)查看节点托管费用
        • 4)查看节点收益
        • 5)恢复/取消节点
    • 💡骆驼小课堂
      • 🪙USDT是什么?
      • 🪙什么是币币交易?
      • 🪙如何支付节点托管费用?
      • 💬如何加入DxChain全球社区
      • 🌉【跨链桥】进行了跨链交易但不到账
      • 📱DxChain3.0测试教程
      • 🧬区块链的共识机制
      • 🔐私钥/助记词是什么
      • 🌉什么是区块链的跨链技术
    • 🪧社区布告
      • 节点托管收费细则
      • DxChain V3节点公告
      • 「提现白名单」功能上线公告
      • DX关于热钱包使用安全的公告
      • DX关于Coinbase钱包支持DX-ERC20的公告
Powered by GitBook
On this page

Was this helpful?

  1. The Basics
  2. DxChain V3 LitePaper
  3. 4. DxChain Design Principles & Architecture

4.3 Cross Chain

Previous4.2 DPoS Consensus AlgorithmNext4.4 API Layer

Last updated 3 years ago

Was this helpful?

DxChain Bridge uses AWS Nitro Enclave to build a fast, safe, and low-cost cross-chain bridge between Ethereum and DxChain.

The DxBridge will be composed of Nitro Enclave and a list of trusted nodes (called Warden). Nitro Enclave will be used to build an isolated execution environment to prevent any centralized interference and reduce the complex steps without sacrificing system security.

DxBridge mainly consists of two parts:

  • Nitro Enclave: AWS Trusted Execution Environment solution. By creating an isolated environment, users can use and process private keys with high security while preventing users and applications on the parent instance to views or obtaining information.

  • A set of Wardens: third-party searchers and verifiers of transactions. Warden is mainly responsible for retrieving DxChain and Ethereum and submitting legal transactions that need to be processed to Nitro Enclave. First, Warden will look for transactions that have been successfully sent to the Ethereum wallet or transactions that have been retrieved from DxChain. There must be enough funds to pay for related expenses, including the gas fee and cross-chain fees required, otherwise, the transaction will be rejected and Warden will not retrieve these transactions. Nitro Enclave requires a certain number of Wardens to submit the same transaction at the same time, then the bridge will send the corresponding transaction on another chain and submit legal transactions by providing a private key segment.

Nitro Enclave can directly connect with Warden to obtain on-chain events and send transactions. The private keys of all addresses in the transaction are derived from the master private key generated during initialization that no other party can obtain. The master private key uses the Shamir Secret Sharing algorithm to distribute the private key segments to Warden, and uses TLS communication to verify the identity during the process. Nitro Enclave will ask Warden for private key segments via TLS connection to retrieve the master private key, and distribute new private key segments to Warden again after restart. In addition, transactions confirmed to have been processed by the bridge will be backed up locally.

📝
📖
Figure 5: The Process of DxBridge