Aori is a universal intent settlement protocol built around an off-chain maker-oriented orderbook with onchain atomic settlement. It is one of the three or four serious intent Layers in production in 2026, and the one that most resembles a traditional central limit orderbook in its market structure. If you are trying to understand what Aori is, why it matters, and how it differs from sibling Layers like Eco Routes, Across, and UniswapX, this guide walks through the architecture, the solver economics, and the specific flows Aori is best suited for.

By the end you will know what an intent settlement protocol actually is, how Aori's orderbook differs from a Dutch auction or RFQ, what role LayerZero and Seaport play in the execution path, and where Aori sits in the Rail/Layer/App model that organizes the 2026 cross-chain stack.

Aori is a non-custodial, permissionless protocol that matches cross-chain trades off-chain and settles them onchain. Users sign orders expressing a desired outcome ("I will sell 100,000 USDC on Ethereum for USDT on Solana at this price or better"). Market makers post signed quotes. The orderbook matches them. When a match clears, a solver executes the fill atomically — the trade completes fully or reverts entirely, with no bridge limbo.

The protocol is built to optimize for professional market maker flow. Signature-based gasless orders let makers post deep inventory without paying gas on every cancel or update. Orders progress through a defined lifecycle — Unknown, Active, Filled, Cancelled, Settled — that gives market makers familiar risk-management primitives.

Aori supports an expanding list of EVM chains plus Solana, with new additions driven by demand from the maker side. Execution runs on LayerZero messaging, which handles the cross-chain state update between the source and destination settlement contracts.

Intent Layers have converged on a small number of market structures. Aori picked orderbook; its peers picked different paths.

The orderbook model shines when makers can quote depth across many pairs and want control over inventory exposure on each side. Dutch auctions shine when the asset is volatile and the market needs live price discovery. RFQ-style solver auctions shine when the asset is 1:1 (stablecoins) and the competition is on fee compression, not price discovery. Each model fits a distinct flow, which is why production stacks often use more than one.

A representative Aori flow, step by step:

If any step fails — a solver reneges, a message fails to verify, the destination amount falls below the user's minimum — the entire intent reverts. The user's funds do not move. This atomic property is the core security guarantee and the reason intent Layers replaced ad-hoc bridging for high-value flows.

Aori's contract architecture borrows patterns from Seaport, the order-matching engine that powers OpenSea and a wide set of NFT marketplaces. Seaport's model of signed, offchain-matched, onchain-settled orders translates cleanly to cross-chain intents — the same mechanics that let you buy an NFT without an onchain orderbook let you swap cross-chain without a bridge UI.

Aori also interoperates with ERC-7683, the cross-chain intent standard proposed by Uniswap Labs and Across and now adopted by 30+ projects through the Ethereum Foundation's Open Intents Framework. ERC-7683 standardizes the order format so any solver that implements the spec can serve any Layer that implements the spec. For Aori, this means the same professional market makers serving UniswapX cross-chain orders can serve Aori orders from a shared inventory pool.

The net effect: solver-side standardization tightens spreads everywhere, and Layers compete on developer experience, asset specialization, and market structure — not on who has the deepest isolated solver pool.

Solvers are the agents that take the other side of user orders. On Aori, the market maker and the solver are typically the same entity — a firm that quotes inventory into the orderbook and executes fills when matched. This is different from protocols like Across, where the solver is a neutral relayer and the pricing comes from a first-come-first-fill auction.

Solvers earn the spread between the price they quote into the orderbook and the cost of acquiring destination inventory. On deep pairs like USDC-USDT between major chains, spreads run 1-5 basis points. On exotic pairs or low-liquidity chains, spreads can widen to 20-50 bps. Solver capital is typically pre-positioned on both sides of each supported route, which is why expanding Aori's chain coverage is gated by maker capital availability.

For builders integrating Aori, the solver dynamics matter because they determine the floor on user-paid fees. A route where Aori has dense maker coverage will produce tighter pricing than a route that only has one or two quoting makers.

The 2026 cross-chain stack organizes into three tiers:

Aori is a Layer. It sits on top of LayerZero as its primary messaging Rail (with ERC-7683 as an interop standard) and serves Apps that need orderbook-depth execution. It does not compete with the Rails it runs on — it orchestrates them. This distinction matters because the "Aori vs LayerZero" framing is a category error: LayerZero is the messaging bus that Aori uses to coordinate cross-chain state.

Eco Routes and Aori are both Layers. They both sit above Rails. They both run solver auctions. But they specialize in different flows.

Eco Routes is a stablecoin-specialist Layer. It routes USDC, USDT, USDbC, USDG, oUSDT, USDT0, and USDC.e across 15 chains using CCTP, Hyperlane, LayerZero, or Wormhole per transaction depending on cost and finality. The market structure is a solver auction optimized for 1:1 stablecoin execution and payment flows, exposed through Routes CLI and Routes API.

Aori is an orderbook-specialist Layer. It handles any asset pair that a maker will quote — stablecoins, majors, or long-tail tokens — and gives professional market makers the familiar maker-taker primitives they need to quote tight spreads. The market structure is an off-chain orderbook with atomic onchain settlement via LayerZero.

Use Aori when the flow benefits from orderbook depth and maker-driven pricing. Use Eco Routes when the flow is stablecoin-centric, requires multi-rail orchestration, and needs a payment-grade developer experience. Most production stacks use both — Aori for pro trading flow, Eco Routes for treasury and payment flow. The stablecoin API architecture guide covers how the orchestration Layer pattern composes with other infrastructure.

Both Aori and UniswapX target trading flow. The difference is market structure.

UniswapX runs a Dutch auction — the user's target price starts aggressive and relaxes over a short window, with fillers bidding to execute at progressively better prices until one accepts. Dutch auctions surface real-time market depth on volatile assets and produce good execution for tokens where price discovery matters.

Aori runs an orderbook — makers post two-sided quotes, takers consume them, matching is atomic. Orderbooks produce tighter execution when makers have pre-committed inventory at specific price levels, which is typical for professional flow on deep pairs.

UniswapX is the natural fit for retail DEX swaps. Aori is the natural fit for professional flow that resembles traditional TradFi market making. Both are ERC-7683-compatible, so solvers can serve both from the same inventory pool.

Across is a first-relayer-fills model. A user signs a deposit, and the fastest registered relayer on the destination chain fronts liquidity. Across is optimized for raw speed on EVM-to-EVM transfers of major assets, with UMA's Optimistic Oracle handling settlement back to the source chain.

Aori is slower than Across on the same route if the route is a simple major-asset transfer — the orderbook adds matching latency that the first-filler model does not. But Aori produces better pricing on asset pairs where maker inventory is deeper than the race-to-fill incentive Across offers its relayer network.

Rule of thumb: if your intent is "move asset X from chain A to chain B as fast as possible," Across. If your intent is "trade asset X on chain A for asset Y on chain B at the best price," Aori.

Aori inherits the security assumptions of the Rails it uses. LayerZero messaging is the primary cross-chain communication layer — any Aori settlement is as secure as the LayerZero message path for that specific route. The ERC-7683 interop surface is also within the security envelope.

Onchain, Aori's settlement contracts are responsible for escrow on the source side and verifying proofs of destination-side fill. A bug in these contracts would be a direct risk. Audits and formal verification are ongoing concerns for any production intent Layer, and Aori publishes audit reports on its documentation site.

Off-chain, the orderbook and matching engine are not the custody layer — even if the matching engine goes offline, user funds remain in their source-chain escrow and can be reclaimed after expiry. This design choice is one of the main reasons orderbook intent protocols feel closer to self-custodial than to centralized exchanges.

Three flow types fit Aori well.

Professional cross-chain trading. Trading firms that already run traditional orderbook infrastructure translate their maker stack directly onto Aori. The maker-taker primitives, the signature-based gasless quotes, and the atomic settlement mirror what they expect from TradFi venues.

Cross-chain market making as a service. Firms that want to offer cross-chain execution to their own clients can plug into Aori, quote inventory, and earn the spread without building their own settlement stack. The orderbook does the matching; the firm does the pricing.

Long-tail asset pairs. Aori's orderbook can support any pair a maker is willing to quote. That makes it useful for tokens too illiquid for deep solver auctions on other Layers, provided at least one maker is posting inventory.

Where Aori is not the right fit: consumer-grade stablecoin payments, where a specialist Layer like Eco Routes gives better chain coverage and a payment-optimized developer experience. The best cross-chain intent protocols comparison maps each Layer to its best-fit flow.

Three trends will reshape what Aori and its peers look like by 2027.

First, fixed-rate, fixed-term intents. Current orders are mostly market-like — fill now at the best available price. Intents that can express "fill at this price by this time, otherwise cancel" will unlock institutional flows that currently route through OTC desks.

Second, compliance-gated orderbooks. Institutional makers want to quote into venues where the counterparty passes sanctions screening. Aori's orderbook model is well-suited to opt-in compliance layers — the maker can choose which counterparty profiles they will fill.

Third, AI-agent order submission. Agent frameworks that autonomously hedge or rebalance onchain positions will route through intent Layers at scale. Orderbooks with predictable latency and clean message formats will be well-positioned versus Layers that assume human-in-the-loop UX.

No. Aori is an intent settlement Layer that orchestrates cross-chain execution on top of messaging Rails like LayerZero. A bridge moves a specific asset using a fixed trust model; Aori matches user orders off-chain and settles them atomically onchain, abstracting the bridge choice entirely. The user never sees the underlying Rail.

Aori uses an off-chain orderbook with maker-taker primitives. UniswapX uses a Dutch auction where fillers compete on descending price. Orderbooks give deeper execution for professional flow with pre-committed inventory. Dutch auctions give better price discovery for volatile tokens. Both are ERC-7683-compatible, so solvers can serve both from the same inventory.

Yes, any asset pair that a maker will quote. For high-volume stablecoin payments specifically, a specialist Layer like Eco Routes typically gives better 15-chain coverage and a payment-optimized developer experience, because it orchestrates across CCTP, Hyperlane, LayerZero, and Wormhole per transaction rather than specializing in orderbook-style execution.

The trade reverts atomically and the user's funds remain in source-chain escrow. If matching fails, the intent expires and the user can reclaim the locked tokens. If a solver accepts a match but fails to fill on the destination, the settlement contract does not release source tokens. The failure modes do not leave funds stranded.

The official Aori documentation covers contract addresses, the order format, the matching engine API, and integration patterns for makers and takers. The Aori GitHub holds the reference implementations and example clients.

Aori is an intent settlement Layer with an orderbook market structure, built for professional cross-chain trading flow. It sits alongside Eco Routes, UniswapX, Across, and CoW Swap as one of the specialist Layers that orchestrate the 2026 cross-chain stack. Use Aori when your flow benefits from maker-driven orderbook depth and signature-based gasless orders. Use a sibling Layer when your flow is stablecoin-centric (Eco Routes), volatile-token-swap-centric (UniswapX), or pure speed-on-major-assets (Across). The Rail / Layer / App model makes the choice obvious — match the Layer to the flow, and let it orchestrate the underlying Rails.