Cross-Chain Arbitrage MEV 2026: Intents, Bridges, and Risk

Answer first — Cross-chain arbitrage is not one strategy. Intent solving uses pre-positioned inventory to fill a user's destination-chain request and receives settlement later. Bridge arbitrage moves assets through a bridge while carrying price, finality, and bridge risk. The correct comparison is not a projected return percentage; it is a per-attempt ledger covering fill value, gas, protocol fees, rebalancing, inventory financing, failed attempts, and settlement risk.

Two Architectures

Protocols use different terminology and settlement rules. Read the current protocol documentation before treating any step as atomic, guaranteed, or final.

Intent Solving

A simplified intent flow is:

1. A user requests an asset or outcome on a destination chain.
2. A solver quotes the request under the protocol's auction or matching rules.
3. The selected solver uses destination-chain inventory to fill the user.
4. The protocol verifies fulfillment.
5. The solver is repaid under that protocol's settlement mechanism.
6. The solver rebalances inventory across chains.

The fill is only part of the economics. Rebalancing can become the largest operational cost when order flow is directional. A solver that repeatedly pays users on one chain and receives repayment elsewhere may run out of usable inventory even while its accounting balance appears positive.

Bridge Arbitrage

A simplified bridge-arbitrage flow is:

1. Detect a price difference after accounting for executable depth.
2. Submit the source-chain transaction.
3. Wait for the bridge's required message, proof, or finality path.
4. Receive or mint the destination asset.
5. Execute the destination trade.
6. Rebalance or return inventory.

During that sequence, the observed spread can close or reverse. The transfer can be delayed, the destination route can change, or a risk control can halt the bridge. This is not equivalent to a single-chain atomic transaction.

The Cost Ledger

Evaluate every candidate with the same formula:

net result =
  destination proceeds
  + settlement received
  - source inventory delivered
  - source and destination gas
  - protocol, bridge, and LP fees
  - slippage and price impact
  - rebalance cost
  - capital financing cost
  - failed-attempt and timeout cost
Copy

For an intent solver, include orders that were quoted but not filled, fills that were delayed, and inventory that could not be rebalanced at the expected cost. For bridge arbitrage, record failed source transactions, delayed messages, changed destination quotes, and return-path costs.

Risk Controls

Inventory limits

Set a maximum exposure per chain, token, bridge, and settlement state. A global balance is not enough; capital on the wrong chain may be unusable.

Finality policy

Document which chain state is considered safe for each action. Do not assume the same confirmation rule fits Ethereum, an optimistic rollup, a fast-finality chain, and an external bridge.

Route allowlist

Restrict contracts, tokens, bridges, routers, and destination chains. A quote should not silently introduce a new bridge or token wrapper.

Quote expiration

Every quote needs a clear expiry and a fresh executable-depth check. A visible mid-price is not the price available to the strategy.

Circuit breakers

Stop new fills when settlement is delayed, bridge status changes, inventory breaches its limit, oracle data becomes stale, or rebalancing cost exceeds policy.

Independent monitoring

Monitor protocol status, source and destination transactions, bridge messages, inventory, and repayment independently of the execution client.

Reproducible Evaluation

1. Select one protocol and one route.
2. Record the protocol version and official contract addresses.
3. Define the exact fill and settlement states.
4. Capture quotes and executable depth at decision time.
5. Record source, destination, repayment, and rebalance transactions.
6. Assign every fee to the attempt that caused it.
7. Keep timed-out and failed attempts in the dataset.
8. Report the observation window and number of opportunities.
9. Separate measured facts from assumptions.
10. Do not turn one route's result into a general expected return.

What FRB Supports

FRB Agent currently focuses on supported single-chain execution workflows, including simulation-first controls and private bundles where available. It does not claim to be a production cross-chain intent solver. A solver needs protocol-specific quoting, inventory management, repayment reconciliation, and bridge circuit breakers that are distinct from a single-chain atomic strategy.

The architectural material remains useful to FRB users because it explains why a visible cross-chain price difference is not automatically an executable opportunity.

FAQ

Is intent solving atomic?

Do not assume so. User fulfillment and solver repayment can be separate protocol stages. Review the specific protocol's settlement and dispute model.

Which bridge is fastest?

There is no stable universal answer. Time depends on route, chain finality, liquidity, relayer state, security model, and current conditions. Measure the exact route rather than reusing a marketing number.

Does a larger displayed spread mean a better opportunity?

Not necessarily. A large spread may reflect shallow liquidity, a delayed bridge, a depegged wrapped asset, or a route the strategy cannot settle safely.

Can a single wallet balance cover all routes?

Usually not efficiently. Intent solving depends on usable inventory on destination chains. Track available, committed, unsettled, and rebalancing inventory separately.

Primary References

• Across documentation
• deBridge DLN documentation
• Wormhole documentation
• LayerZero documentation
• FRB risk disclosure