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
On this page
  • 1. Problems/Challenges it aims to solve
  • 2. Solutions
  • 3. Target Customers
  • 4. Key Points
  • 5. Key People

Was this helpful?

  1. Protocol Providers

Axelar

1. Problems/Challenges it aims to solve

  • Interoperability between blockchains: Axelar enables communication between different blockchain networks by routing messages across chains. This solves the problem of siloed blockchains unable to interoperate.

  • Complexity of cross-chain development: By providing APIs, SDKs, gas/transaction management, Axelar simplifies building cross-chain dApps vs handling low-level details.

  • Security of cross-chain communication: Axelar uses validator consensus, cryptographic proofs etc to secure message relay between chains.

  • Slow/unreliable message passing: Axelar optimizes cross-chain communication by parallelizing transfers, using Subway for fast message routing.

  • Centralization risks: Axelar aims to be decentralized and permissionless based on its validator network and decentralized governance.

2. Solutions

Permissioned instance of the Axelar blockchain (and related off-chain infrastructure) used for cross-chain message passing and secure interoperability.

Application-layer APIs & SDK: Make it easy for dApp developers to add cross-chain capabilities without needing to know the low-level details of Axelar network. The APIs initiate messages which are then processed securely by Axelar's underlying infrastructure.

Axelar network: Axelar has its own network of validators that secure the network through staking and voting. Axelar targets validators as customers to stake on the network and run validator nodes. Axelar incentivizes providers to run nodes and infrastructure for the various connected blockchain networks. This allows validators to verify cross-chain messages.

3. Target Customers

  • dApp developers: Axelar provides APIs, SDKs and other developer tools to easily integrate cross-chain capabilities into decentralized applications. This allows dApp developers to build apps that can communicate across multiple blockchains.

  • Blockchain networks: Axelar aims to connect various Layer 1 and Layer 2 blockchain networks together, enabling interoperability between chains. Axelar targets the developers/teams building these blockchain networks as customers to integrate their chains with Axelar.

  • Validators: Axelar has its own network of validators that secure the network through staking and voting. Axelar targets validators as customers to stake on the network and run validator nodes.

  • Node/infrastructure providers: Axelar incentivizes providers to run nodes and infrastructure for the various connected blockchain networks. This allows validators to verify cross-chain messages.

  • End users: The end users of the dApps built on top of Axelar that need to execute cross-chain transactions are also indirect customers. Axelar empowers advanced cross-chain apps catering to these users.

4. Key Points

The key points about Application-layer APIs and SDK:

  • The APIs allow dApps to call functions to initiate cross-chain message requests.

  • For example, a dApp can call an API to send a message to call a smart contract on another chain, passing arbitrary data.

  • The APIs and SDKs abstract away the complexity of interacting directly with the Axelar network.

  • They provide a smooth developer experience for building cross-chain dApps.

  • Under the hood, the APIs and SDKs interact with the Axelar Gateway on each chain.

  • The Gateway contracts contain the necessary logic to process and route cross-chain messages.

  • So the APIs handle initiating messages and the Gateways handle sending them into Axelar network.

The key points about Axelar Gateways:

  • It is deployed on every external blockchain integrated with Axelar. On EVM chains it is a smart contract, on non-EVM chains it is an application.

  • It enables communication between the external chain and Axelar network.

  • On source chains, it allows initiating cross-chain messages. On destination chains, it enables receiving and executing cross-chain messages.

  • It is controlled jointly by Axelar validators through multiparty cryptography.

  • It receives cross-chain requests from dApps and submits them to Axelar network via relayer services.

  • It authorizes and executes approved cross-chain payloads delivered from Axelar.

5. Key People

PreviousChainlinkNextConnext

Last updated 1 year ago

Was this helpful?