QX Interoperability - v.0.7
  • 💡ABOUT
    • License
    • How to Give Attribution For Usage of QX Interoperability
  • 👬Industry Initiatives
    • ISO Interoperability Framework
    • EEA Crosschain Interoperability Specification Suite
    • IEEE Standards for Blockchain Interoperability
    • ICMA Bond Data Taxonomy
    • IETF Secure Asset Transfer Protocol
    • SODA MIT Crosschain Interop WG
    • Decentralized ID for Tokenization
    • Cross-chain Interoperability Alliance
    • SWIFT Coalition
    • BIS Projects
    • MAS Projects
    • Regulated Liability Network
      • UK Finance - Regulated Liability Network
      • US - Regulated Liability Network
    • Hyperledger Projects
    • EEA-OASIS L2 WG
    • RollColl WG
    • ITU Digital Currency Global Initiative
    • EIP-5164: Cross-Chain Execution
    • EIP-3220: Crosschain Identifier Specification
    • EIP-7281: Sovereign Bridged Token
    • ERC-7092: Financial Bonds
    • ERC-3643: Permissioned Tokens
    • ERC1400: Universal Token for Assets and Payments
    • ERC6960: Dual Layer Token
    • CASA CAIPs
    • COSMOS IBC
    • Polkadot XCM
    • IEEE Crosschain Workshop
  • 🏦Use Cases
    • Payments/Digital Asset Transactions
      • Enable transfers of digital payment tokens
      • Conduct Compliant Cross-VASP Digital Asset Transaction
      • Swap NFT for Tokenized Bank Deposits
      • Enable Intra-Group Payments with Tokenised Deposits
    • Wholesale CBDC (wCBDC)
      • Enable Settlement with Simultaneous Delivery versus Payment
      • Facilitate Cross-Border Payments with wCBDC
      • Enable FX transactions to facilitate cross-border payments
      • Settle Crypto Derivatives using wCBDC
      • Access Liquidity via wCBDC
      • Settle Interbank Payments with wCBDC
      • Settle Interbank Payments with wCBDC (Acquirer-Merchant Settlement)
      • Make Property Payments with Tokenized Deposits
      • Provide FX Liquidity using wCBDC
      • Enable Payment versus Payment (PvP)
      • Crosschain digital bonds trades
    • Decentralized Finance (DeFi)
      • Aggregate Yields across Blockchains for Corporate Treasuries
    • Retail CBDC (rCBDC)
      • Provide Targeted Government Transfers (Government Vouchers)
      • Streamline Home Equity Lending
      • Provide Corporate Vouchers and Rewards
      • Make Milestone-Based Property Purchase Payments
      • Enable Traceable and Targeted Donations
      • Consumer Prepayments to Corporations
      • Enable Asset Transactions
      • Enable Cross-Border Remittances
      • Government Payouts
      • Managing Learning Accounts
    • Private Markets/Asset Tokenization and Trading
      • Tokenize and Trade Private Equity Fund Shares
      • Distribute and Settle Private Corporate Debt Issuance
      • Trade Employee Stock Grants as Digital Securities
      • Enable Secondary Trading for Non-Listed Assets and Private Markets
      • Automated Discretionary Portfolio Management with Tokenized Assets
    • Trade & Commerce
      • Support Tokenized Electronic Bills of Lading for Global Trade
      • Commercial Vouchers
      • Online Commerce
      • Programmable Rewards
    • DAOs
  • 🛠️Solutions Providers
    • Swift
    • Mastercard
    • Fnality
    • Quant Network
    • Ownera
    • Fujitsu
    • Deutsche Bank/Standard Chartered Ventures
    • Kaleido
    • Onyx/JP Morgan
    • Canton Network
    • Universal Digital Payments Network Alliance
    • Li.Fi
    • Visa
    • Partior
    • CLSNet
    • Impel
    • Adhara
    • Datachain
    • Ant Group
    • CitiGroup
    • WeBank
    • IMF ?
    • BIS ?
    • Progmat ?
    • GroundX ?
  • 📓Requirements
    • Legal & Regulatory Layer
    • Governance and Policies Layer
      • Audit and Compliance sub-layer
      • Operations sub-layer
    • Application Layer
    • Integration and Middleware Layer
      • Oracle sub-layer
    • Semantic Layer
    • Syntactic Layer
    • Foundational Layer
      • Discovery sub-layer
      • Smart contract sub-layer
      • Function call sub-layer
      • Messaging sub-layer
      • Transaction sub-layer
      • Consensus sub-layer
      • Data transfer sub-layer
      • Security sub-layer
        • Identity and Authentication
        • Data Privacy
    • -
  • Protocol Providers
    • Chainlink
    • Axelar
    • Connext
    • Across
    • Toposware
    • IBC
    • Hyperlane
    • Sovereign Labs
    • Polymer Labs
    • Orb Labs
    • Zetachain
    • Sygma
    • deBridge
    • Wormhole
    • Routeur Protocol
    • Synapse
    • Wanchain
    • Gnosis
    • LayerZero
    • Comparison
  • Bridging Approaches
    • Bridges
    • Native Bridge
    • Third Party bridge
    • Multi-bridge
    • Oracle
    • Shared Sequencer
    • Mechanisms
      • Hash Locking
      • Notary Schemes
      • Proof Aggregation
    • zk-rollup ecosystems
    • Intent-centric
    • Function Calls
    • Relayers
      • Multisig
      • MPC
      • Light Client
      • ZKP Stark
      • ZKP Snark
      • Hybrid method
Powered by GitBook

Ant Group

1. Problems/Challenges it aims to solve

2. Solutions

ODATS (Open Data Access Trusted Service): ODATS has been adapted and validated in various use cases including financial services and logistics.

AntChain Bridge:

3. Target Customers

4. Key Points

TO REVIEW - TRANSLATED FROM CHINESE

AntChain Bridge interprets cross-chain interoperability on two levels: communication and trustworthiness, i.e., the goal of cross-chain is to achieve trustworthy communication between blockchain entities.

In the architecture of AntChain Bridge, the relay needs to interact with the blockchain, and the communication protocols of heterogeneous chains vary widely, unable to uniformly adapt, therefore AntChain Bridge abstracts out a blockchain bridge component (Blockchain Bridge Component, BBC) to solve the communication problems between the blockchain and the cross-chain network.

Every kind of heterogeneous chain that wants to connect to the AntChain Bridge cross-chain network needs to implement a set of standard blockchain bridge components, which can be divided into on-chain and off-chain parts, including off-chain plugins and system contracts. Off-chain plugins need to be developed based on the SDK, while the on-chain part is usually a smart contract that requires the implementation of specific interfaces and logic. To reduce development difficulty, we offer an implementation in the Solidity version.

AntChain Bridge provides developers with SDK, manuals, and system contract templates to help developers complete plugin and contract development. At the same time, AntChain Bridge offers plugin services (PluginServer) to run plugins. The plugin service is an independent service with plugin management and the function to respond to relay requests.

In the current engineering implementation, the BBC off-chain part is implemented in the form of plugins. AntChain Bridge has implemented a set of SDKs. By implementing the interfaces (SPI) stipulated in the SDK, a plugin package can be generated through simple compilation. Plugin service (PluginServer, PS) can load BBC off-chain plugins; details can be referred to in the plugin service introduction document.

5. People

Geoff Jiang, President of Digital Technologies Business Ant Group

Yan Ying, Technical Director of AntChain

Li Ming, Chairman of the IEEE Computer Society Blockchain and Distributed Ledger Technology Standards Committee.

6. Resources

https://github.com/AntChainOpenLabs/AntChainBridgePluginSDK

https://jcupt.bupt.edu.cn/EN/article/downloadArticleFile.do?attachType=PDF&id=1443

PreviousDatachainNextCitiGroup

Last updated 7 months ago

On this page
  • 1. Problems/Challenges it aims to solve
  • 2. Solutions
  • 3. Target Customers
  • 4. Key Points
  • 5. People
  • 6. Resources

Was this helpful?

Page cover image