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. User documentation
  2. Eywa DEX
  3. Operation Interruption

Data transfer error

PreviousSlippage conditionNextDAO

Last updated 1 year ago

A cross-chain operation cannot be executed if the data transfer protocol that facilitates interaction between smart contracts across blockchains is not functioning. The Eywa DEX application does not allow operations to be performed when the data transfer protocol is not working. However, theoretically, force majeure situations can occur when users initiate a cross-chain transaction simultaneously with the failure of the CDP protocol. In this case, the atomic lock/mint and burn/unlock operations will be only partially completed. CDP is designed in such a way that it will first complete the unfinished cross-chain operations once the protocol is restored.

However, by the time the protocol is restored, market conditions may have changed, and the user may want to cancel the execution of the cross-chain operation before it is processed. For this purpose, we have implemented the Emergency withdrawal mechanism.

If the cross-chain transition takes longer than the established time, an error message will appear:

First, the user needs to switch to the network where the message was not delivered. To do this, click on the Change destination network button:

Next, initiate the fund withdrawal operation in the network from which the message was sent but ultimately not delivered:

Click on the Withdraw deposit button and sign the transaction.

Sending the Withdraw transaction ensures that the cross-chain operation will not be continued, the user's funds will be unlocked, and the user will be able to access them.

πŸ’Έ