> ## Documentation Index
> Fetch the complete documentation index at: https://docs.debridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bridging Non-Reserve Assets

> Bridging Non-Reserve Assets: Overview and Pre-Order-Swap.

# Overview

The [deBridge Liquidity Network (DLN)](/dln-details/overview/introduction) protocol supports bridging any liquid token from the source
chain to the destination chain,  not just [reserve assets](/dln-details/dln-specifics/reserve-assets). While the actions taken by the system are similar to those used
when [bridging reserve assets](/dln-details/dln-specifics/bridging-reserve-assets), the internal flow differs and introduces considerations
that must be communicated clearly for a seamless end-user experience.

```mermaid theme={null}
sequenceDiagram
    actor User
    participant CreateTx
    participant Aggregators
    participant ERC20_Contract
    participant dln as DlnContracts
    rect rgba(230, 230, 255, .15)
        Note right of User: Get Transaction <br/> and Estimate
        User        ->> CreateTx     : get(...)
        activate CreateTx
        CreateTx    ->> Aggregators  : simulate(...)
        activate Aggregators
        Aggregators -->> CreateTx    : simulation response
        deactivate Aggregators
        CreateTx    -->> User        : response
        deactivate CreateTx
    end
    opt inputAssetType == ERC20
        User            ->> ERC20_Contract : approve(actorAddr, tx.to, amount)
        ERC20_Contract  -->> User          : approve tx receipt
    end
    User ->> User : sign response.tx
    rect rgba(240, 240, 240, .15)
        Note right of User: Create Order <br/> Transaction
        Note right of User: Atomic
        User ->> dln : submit signed response.tx
        activate dln
        opt inputAssetType == ERC20
            dln ->> ERC20_Contract : transferFrom(actorAddr, dlnAddr, amount)
        end
        dln ->> Aggregators: swap()
        dln ->> dln : finishCreatingOrder()
        deactivate dln
        dln -->> User : transaction receipt
    end
```

### Pre-Order-Swap

Cross-chain settlements are executed in [reserve assets](/dln-details/dln-specifics/reserve-assets) to simplify operations for solvers.
As a result, whenever a non-reserve asset is bridged, it must first be swapped into a reserve asset before the order is
created—a process referred to as the **Pre-Order-Swap**.

The `create-tx` API automatically handles this swap step. It queries DeFi aggregators in the background to simulate the swap
and produce `response.tx.calldata` (see step 1a in the diagram). The API is optimized to select the best available rate.

Once a user signs and submits `response.tx`, the DLN smart contracts initiate the process by transferring the approved
non-reserve assets to themselves (step 3a). The actual **Pre-Order-Swap** is executed via an Automated Market Maker (AMM)
(step 3b). Given the potential for price slippage, **the destination chain estimate is based on the minimum amount a user
would receive from the swap**.

<Tip>
  If integrators prefer to manage the swap path manually, they can perform the conversion to [reserve assets](/dln-details/dln-specifics/reserve-assets)
  themselves before calling the `create-tx` endpoint -- ensuring complete control over the swap route.
</Tip>

This design—basing estimates on the minimum outcome of the **Pre-Order-Swap** -- helps shield users from market volatility and
reduces the likelihood of orders being ignored due to insufficient profitability from a solver's perspective.

Once the swap completes, the [reserve assets](/dln-details/dln-specifics/reserve-assets) are locked within the protocol until the order
is either [fulfilled or cancelled](/dln-details/integration-guidelines/order-creation/order-tracking-api/order-states).

<Tip>
  If the order is [cancelled](/dln-details/integration-guidelines/order-creation/cancelling-order), the locked [reserve
  assets](/dln-details/dln-specifics/reserve-assets) are returned to the user. It is important to note that the user will receive reserve assets back
  \-- not the original non-reserve assets used at the start of the process.
</Tip>