Dexalot's RFQ lets a trader on any supported chain swap into Dexalot L1's order book in a single atomic transaction — no bridge, no wrapped asset, no waiting window.
December 24, 2024 |
Cross-chain trading in crypto is usually a bridge problem dressed up as a UX problem. You want AVAX, but your USDC sits on Arbitrum. The standard answer is to bridge: lock your USDC on one chain, mint a wrapped representation on another, wait for finality, accept that you now hold an asset whose redemption depends on a third-party contract’s solvency, and then trade. Every step adds delay, trust assumptions, and execution risk.
Dexalot’s SimpleSwap doesn’t do this. A user on Arbitrum can buy a token live on Dexalot L1, pay in their native USDC, and receive the output token natively on Avalanche — with no wrapped asset, no bridge transaction, and no waiting room. The mechanism that makes this possible is an RFQ system that most users never see. This post is what it actually does.
RFQ stands for Request for Quote. It is one of the oldest market structures in finance, predating exchange order books by centuries. In a TradFi RFQ, a buyer asks a dealer for a price on a specific size of a specific asset. The dealer responds with a firm quote: “I will sell you 10,000 shares at $42.17, good for 30 seconds.” If the buyer accepts within the quote’s lifetime, the trade prints at that exact price.
The defining property of an RFQ is that the price is a commitment from a specific counterparty. It is not a snapshot of a public book that might move between query and execution. It is not a curve that will deterministically move against you. It is a price that someone has agreed to honor, signed, and put on the line.
This is structurally different from how most DEX trading works. AMMs price you against a bonding curve (see our earlier post on slippage). Streaming order books let you see resting liquidity, but the price you actually fill at depends on what’s still there when your transaction lands. RFQ removes that ambiguity: the quote is the price, full stop.
The default solution for cross-chain trading is a bridge. The mechanics vary — lock-and-mint, burn-and-mint, optimistic, zk-verified — but the user experience converges on the same shape.
For a trader who just wants to swap one asset for another, the bridge is an entire workflow standing between intent and execution. It is also the layer where most cross-chain value gets lost, either to direct exploits or to slippage on the wrapped-asset side.
Dexalot is built on a hub-and-spoke model. The hub is Dexalot L1 — the application-specific chain where the canonical order book lives. The spokes are smart contracts deployed on each supported chain (Avalanche, Arbitrum, Base, BNB Chain), each holding a small inventory of the base and quote tokens for the pairs they serve.
Two pieces of infrastructure make cross-chain RFQ possible:
The order book itself never leaves Dexalot L1. There is no fragmented orderbook, no multi-chain matching engine, no liquidity duplicated across deployments. There is one source of truth for price, and small inventory pools at the edges to serve users where they already are.
Walk through a concrete example. A user on Arbitrum wants to swap 5,000 USDC for AVAX. AVAX/USDC trades on the Dexalot L1 order book. The user has never used a bridge, has no intention of bridging, and is interacting with their wallet on Arbitrum only.
From the user’s perspective, the entire interaction is one transaction on Arbitrum. No bridge dialog. No wrapped asset in their wallet. No delay window.
This phrase is overused in crypto marketing, so it’s worth being precise about what it means here.
The user never holds a bridged asset. The input token is native on the source chain, and the output token is native on the destination chain. When the swap settles on Arbitrum, the AVAX the user receives is the same AVAX anyone else holds on the network — not a wrapped derivative redeemable from a bridge contract.
The settlement itself is atomic on the user’s chain. There is no two-phase commit, no waiting for confirmations on a second chain before the user is whole. The user’s side of the trade completes in a single Arbitrum transaction, signed once, and either it executes fully or it reverts.
What does cross the chain boundary is the message infrastructure: order book updates and inventory rebalancing flow across chains via LayerZero, but only on the operator side. Users never sign a bridge transaction. They never wait for a bridge. The bridge is no longer in their path.
DEX aggregators like 1inch, Kyberswap, Odos, Velora, and OpenOcean route trades across the available DEX landscape to find the best execution for the user. AMMs are a natural part of this landscape, but they have a routing problem that RFQ solves elegantly.
When an aggregator routes through an AMM, the actual fill price depends on the curve, on what other transactions land in the same block, and on whatever sandwich attempts the mempool produces. Aggregators handle this with slippage tolerances and reverts, but the uncertainty is structural.
When an aggregator routes through Dexalot’s RFQ, the quote is a signed commitment. The aggregator knows the exact output, can present it to the user with confidence, and the trade either fills at that price or doesn’t fill at all. There is no slippage variable to model and no MEV surface for sandwich bots to exploit.
From the aggregator’s point of view, an RFQ source is the easiest possible integration: clean price, atomic settlement, predictable behavior. This is why every major aggregator now supports RFQ flow alongside AMM routing, and why Dexalot’s integrations across all the chains it supports translate directly into volume routed to the L1 order book.
The combination of an on-chain CLOB, a hub-and-spoke architecture, and an RFQ-driven cross-chain layer produces a UX that doesn’t feel cross-chain. A trader on Arbitrum, a trader on Avalanche, a trader on Base, and a trader on BNB Chain are all interacting with the same liquidity, at the same prices, in the same instant — without any of them touching a bridge.
For the project listing on Dexalot, it means one source of liquidity serves many markets. For the user, it means cross-chain stops being a step in the workflow and starts being a property of the infrastructure underneath. For the wider DEX ecosystem, it means there is now a way to deliver order-book execution to chains where building an order book directly would never be viable.
Bridges solved the problem of moving an asset between chains. RFQ solves the problem of not needing to.
