deBridge
  • Introduction
  • The deBridge Messaging Protocol
    • Protocol Overview
    • Fees and Supported Chains
    • 🟒Deployed Contracts
    • Development Guides
      • Building an EVM-based dApp
        • EVM smart contract interfaces
          • Interfaces
            • ICallProxy
            • IDeBridgeGate
            • IDeBridgeToken
            • IDeBridgeTokenDeployer
            • IOraclesManager
            • ISignatureVerifier
            • IWethGate
          • Libraries
            • Flags
          • Periphery
            • CallProxy
            • DeBridgeToken
            • DeBridgeTokenProxy
            • SimpleFeeProxy
          • Transfers
            • DeBridgeGate
            • DeBridgeTokenDeployer
            • OraclesManager
            • SignatureVerifier
            • WethGate
      • Sending cross-chain messages from Solana
        • On-Chain external call preparation for Solana
        • Off-chain external call preparation for Solana
      • Lifecycle of a cross-chain call
      • Gathering data for the claim
    • Development Tools
    • Security
    • Slashing and Delegated Staking
  • πŸ”DLN: The deBridge Liquidity Network Protocol
    • Introduction
    • Protocol Overview
    • deBridge Hooks
    • Fees and Supported Chains
    • 🟒Deployed Contracts
    • Market and Limit Orders
    • Interacting with smart contracts
      • Introduction
      • Placing orders
      • Filling orders
      • Withdrawing Affiliate Fees
    • Interacting with the API
      • Authentication
      • Creating an Order
        • Quick Start
        • Reserve Assets
        • Bridging Reserve Assets
        • Bridging non-reserve assets
        • API Parameters
          • Estimation-Only
          • prependOperatingExpenses
        • API Response
          • JSON Example
        • Refreshing Estimates
        • Fees and operating expenses
        • Order Fulfillment
          • Detecting the Order
          • Fulfilling the Order
            • Pre-Fill-Swap
          • Claiming the Order
      • Tracking Order Status
        • Order States
      • Integrating deBridge hooks
        • Creating Hook data for Solana
      • Submitting an Order Creation Transaction
      • Cancelling the Order
      • Affiliate fees
    • Interacting with the deBridge App
      • Custom Linking
    • deBridge Widget
    • Protocol specs
      • Deterministic order ID
      • Hook data
        • Anatomy of a Hook for the EVM-based chains
        • Anatomy of a Hook for Solana
  • πŸ’ΈdePort
    • Getting started
    • Transfers Flow
  • ⚑deBridge Points
    • Referrers Overview
    • Integrators Overview
  • 🌐deBridge IaaS
    • Getting started
  • 🌐Legal
    • SDK & API License Agreement
  • External Links
    • deBridge Use Cases
      • πŸ’‘Examples
    • Talks, Videos, and Articles
    • Website
    • Github
    • Twitter
    • Social channels
      • Discord
      • Facebook
      • LinkedIn
      • Medium
      • Telegram
      • YouTube
Powered by GitBook
On this page

Was this helpful?

  1. DLN: The deBridge Liquidity Network Protocol
  2. Interacting with the API
  3. Creating an Order

Bridging Reserve Assets

Bridging of reserve assets, and steps to take.

PreviousReserve AssetsNextBridging non-reserve assets

Last updated 14 hours ago

Was this helpful?

This page outlines the behavior of input assets during order creation and provides a visual representation of the process for creating an order using reserve assets.

When interacting with the create-tx API, the includes a tx field. To create an order, it is sufficient to sign the transaction and submit it to the network. The data field within tx contains all instructions necessary to create the order on the source chain.

The simplest scenario occurs when bridging from the source chain to the destination chain. In this case, the order creation process on the initiator’s side consists of three distinct steps:

  • Step 1: Call create-tx API with the required .

  • Step 2: After receiving the , call approve on the ERC-20 contract of the reserve assets. The spender should be set to the value in response.tx.to, and the approved amount should match the value specified in the transaction.

    • Note: This step is required only for ERC-20 assets.

  • Step 3: Sign and submit response.tx to the blockchain. This action locks the specified amount of on the source chain until the order is either or .

Once these steps are completed, the bridging process from the user's perspective is finished. The next actions involve either or . Additional details on how solvers fulfill the order on the destination chain are available .

πŸ”
monitoring the order’s status
initiating cancellation
here
response
reserve assets
parameters
response
reserve assets
claimed by a solver
cancelled by an authorized entity
Reserve-asset bridging, visualized