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
  • Mechanics
  • Transaction history
  • Payment of fees
  • Security
  1. EYWA Ecosystem
  2. Products
  3. Eywa v1
  4. Cross-chain Liquidity Protocol

Eywa Token Bridge

PreviousCross-chain DEX v1NextGasless transactions

Last updated 1 year ago

The Eywa Token Bridge lets projects present their token on other networks by locking their assets in smart contracts and issuing the token’s derivative on other networks. Our bridge allows you to move issued derivatives between blockchains in all directions, without having to return to the original token lock network using CDP. Eywa Assets use the bridge too.

Regardless of the differences among protocols, rules specifications and governance mechanics of these networks, a usage of the Eywa Token Bridge makes it possible for users to move assets among these chains in a reliable and secure way.

Mechanics

The Eywa Token Bridge consists of the Portal and Synthesis smart contracts located in each of Blockchains: 1, 2, 3, and uses the Eywa Cross-chain Data Protocol (CDP) to transfer cross-chain calls between them:

To move values among blockchains, the Eywa Token Bridge uses synthetic assets (s-tokens). S-tokens are created whenever someone needs to move the asset between two blockchains.

Consider an example: Bob moves the X-token from Blockchain 1 to Blockchain 2. We use the following approach:

Bob sends the transaction to the Eywa Token Bridge, the original X-token is locked in the Portal smart contract in Blockchain 1, this transaction triggers an event in the Bridge smart contract. This event is tracked and processed by oracles of the Eywa Oracle Network.

They verify incoming transactions and make cross-chain calls of smart contracts in destination blockchains. In our example, Bob’s transaction will trigger the Synthesis smart contract in Blockchain 2, which will issue the synthetic s_X token in Blockchain 2, backed by the X token locked in Blockchain 1.

At the same time, Bob can perform a reverse conversion at any time and take the original asset X.

Transaction history

Transferring tokens from one blockchain to another using the Eywa Token Bridge is a complex cross-chain operation. The user can track its execution in the interface in real time.

Payment of fees

Security

Only tokens whose smart contracts have been thoroughly audited by the EYWA team are added to the EYWA Token Bridge. The audit takes into account many characteristics of the project, and also examines the code of smart contracts for the presence of logic for moving and locking user tokens, which potentially creates a danger to user funds. Only tokens whose code complies with all security rules are allowed to be moved.

The Eywa Token Bridge uses to pay for transactions. The user can pay the commission with the native asset of the source network (ETH, BNB, AVAX...).

πŸ—οΈ
Gasless
Gasless transactions
Examples of bridge with native tokens
Example how bridge Synth tokens to other chain without use Portal