EYWA
  • Eywa v2
    • πŸ’₯Eywa v2: new era of Web3 interoperability
  • Eywa token
    • πŸ’ŽTokenomics Eywa/CrossCurve
    • πŸ“ˆEywa token utility
    • ⚑Eywa NFT Collection
      • Eywa NFT Bridge from Aurora to Arbitrum
      • Merge interface in the Arbitrum chain
      • EYWA NFT Manager interface
      • Dashboard interface
    • 🏒Eywa DAO
      • Overview of EYWA DAO
      • Voting
      • Obtaining veEYWA and Calculating the Boost
      • Staking
  • EYWA Ecosystem
    • πŸ’‘Vision
    • πŸ—ΊοΈProduct & EYWA token Roadmap
    • πŸ—οΈProducts
      • Eywa v1
        • Cross-chain Liquidity Protocol
          • Cross-chain DEX v1
          • Eywa Token Bridge
          • Gasless transactions
        • Cross-chain Data Protocol
          • Eywa CDP Introduction
          • Eywa Oracle Network
          • Data transfer flow
      • Eywa v2
        • πŸŒ‰Consensus Bridge
        • ⚑CrossCurve
    • πŸ›‘οΈSecurity audits
    • 🧠Team
    • πŸ¦„Project History
    • πŸ”—External Links
    • ❓FAQ
  • User documentation
    • πŸ’ΈEywa DEX
      • About EYWA Cross-chain DEX
      • Interface Eywa WebApp
      • How to trade
      • Slippage settings
      • Routing
      • Operation Interruption
        • Slippage condition
        • Data transfer error
    • 🏒DAO
      • EYWA Locker Interface
      • Working with the EYWA Locker contract in Arbiscan.
      • EYWA Vote Interface
      • EYWA Incentives Interface
    • πŸ”—Contracts addresses
      • Cross-chain Liquidity Protocol
        • CLP smart-contracts
        • Supported stablecoins
        • Addresses of Eywa stableswap pools
        • Addresses of s-tokens
        • Addresses of e-tokens
      • Cross-chain Data Protocol
        • Governance of Eywa Oracle network
        • Cross-chain messaging
  • DEVELOPER DOCUMENTATION
    • πŸ’»Guide for Developers
      • Technical Documentation for EYWA DAO Smart Contracts
        • EmissionManagerV1
        • EscrowManager
        • EscrowVoteManagerV1
        • GaugeFactoryV1
        • GaugeV1
        • IncentiveRewardsDistributor
        • ProposalManager
        • RebaseRewardsDistributorV1
        • RewardsDistributorFactoryV1
        • CalldataHelperV1
        • Treasury
        • DelegationManagerV1
        • DelegationConditionValidatorV1
        • LockHolderFactoryV1
        • LockHolderV1
  • Eywa Oracle Network - will be ENDED in April 2024
    • πŸ₯‡Validators token distribution
    • Incentivised PoA mainnet
      • General information
      • Application for participation in PoA mainnet
      • Requirements for PoA mainnet validators
      • Rewards for PoA mainnet
      • Instruction for node operators
    • FAQ
  • βš–οΈLEGAL INFORMATION
    • Terms of Service
    • Protocol Disclaimer
    • Cookies Policy
    • Risk of using Eywa
Powered by GitBook
On this page
  1. EYWA Ecosystem
  2. Products
  3. Eywa v1
  4. Cross-chain Data Protocol

Data transfer flow

PreviousEywa Oracle NetworkNextEywa v2

Last updated 1 year ago

A scheme describing the data transfer workflow is shown below:

Step 1. A cross-chain transaction is composed. A cross-chain transaction must be composed according to a certain structure.

Step 2. A cross-chain transaction is sent to a Bridge smart contract. Once a cross-chain transaction is created, it is sent to the Bridge smart contract located in the source network.

Step 3. The Bridge smart contract emits an event containing cross-chain call data. The event with the cross-chain call data is written to a source network block.

Step 4. Creation of an event block by the Eywa Oracle Network. Members of the current Eywa Oracle Network epoch pull from the source block of the network the events emitted by the Bridge smart contact. The events are then packed into the block in the same order as in the source network block. This block contains, among others, the event we are considering.

Step 5. BLS signature generation for a block. After each node-validator creates a block, the process of collecting the threshold BLS signature is initiated. In this way a consensus of all participants of the network regarding the block content is achieved.

Step 6. Writing a block to the Eywa blockchain. If consensus is obtained (>β…” from epoch participants), the block is added to the corresponding Eywa blockchain relaychain. A relaychain is a blockchain whose blocks contain cross-chain calls from only one source network.

Step 7. Sending cross-chain call to destination network by Pusher service. The cross-chain call is sent to Blockchain B by the Pusher service. The Pusher service performs several sequential steps:

  1. Parses EYWA blockchain blocks into individual cross-chain calls.

  2. Prepares the cross-chain calls for sending by attaching a cryptographic proof that will be verified on the Bridge smart contract in Blockchain B.

  3. Sends the transaction to the Bridge smart contract in Blockchain B network.

Step 8. Validation of a cross-chain call in a Bridge smart contract on the destination network. The Bridge smart contract verifies the validity of the cryptographic signature of the epoch participants.

Step 9. Sending a cross-chain call to the target smart contract. If the cross-chain call verification in the Bridge smart contract is successful, the cross-chain call is redirected to the target smart contract.

πŸ—οΈ
Cross-chain Data Protocol scheme