Docs: routes & execution
BroEx is a legal, non-custodial cross-chain exchange. Every direction runs through the same order lifecycle — quote, create-order, and status tracking are identical. The only difference between pairs is the route: a direct single-step swap, or a deeper multi-network route chosen automatically for the pair.
Deposit in → routed exchange → payout out
Your deposit enters the router. The system picks the optimal path for your pair and current network conditions, then either settles directly or routes across several networks before preparing payout.
Final payout can be on the original network or another selected destination asset/network, and it always follows the resulting route model rather than a random transfer path. If a route cannot complete, funds are returned to your refund address.
What a multi-network route is
A deeper path that traverses several networks to deliver a pair reliably. It does not introduce a separate backend contract; the same order API and lifecycle are preserved.
When it is used
The route is chosen automatically for the pair — you never select it. Direct routes serve pairs with direct liquidity; multi-network routes serve pairs that settle more reliably across several networks.
Direct route vs multi-network route
| Field | Direct route | Multi-network route |
|---|---|---|
| Primary intent | Cross-chain swap on a direct, single-step route. | Deeper multi-network route for reliable cross-chain delivery. |
| Routing visibility | Execution detail appears when provider data is available. | The route model is always shown; execution detail appears when available. |
| Route depth | One step where a pair has direct liquidity on the network. | Several networks are traversed before delivery to your destination. |
| Settlement window | Usually narrower in low-complexity routes. | Can be wider due to route depth and network confirmation timing. |
| Outcome range | Payout follows the selected destination path. | Payout lands on your selected destination network, or is returned to your refund address if the route cannot complete. |
How a multi-network route works
Step 1
Deposit intake
The order receives your deposit and starts the standard non-custodial lifecycle.
Step 2
Route selection
The router picks the optimal path for the pair — direct, or a deeper multi-network route.
Step 3
Multi-network execution
Funds are exchanged across the selected networks toward your destination asset.
Step 4
Payout preparation
The destination payout is prepared once the route completes.
Step 5
Settlement window
Final payout timing remains route-dependent and confirmation-dependent.
Order lifecycle
- 1. Deposit received.
- 2. Deposit processed and route selected.
- 3. Routed execution across the chosen networks.
- 4. Payout prepared for your destination network.
- 5. Final outcome: completed, refunded, or expired.
Cross-chain payout examples
These are route-model examples for clarity. They explain routed intent and destination settlement, not a guaranteed live venue-by-venue trace.
Example A
Deposit → multi-network routing → payout prepared on the original deposit network.
Example B
Deposit → multi-network routing → payout prepared on your selected destination network.
Example C
Deposit → multi-network routing → payout prepared on another supported network.
Example D
Deposit → routing cannot complete → funds returned to your refund address.
What multi-network routing means in practice
Routing is driven by provider and router signals. The UI exposes the resulting route type and route notes, but does not disclose internal routing heuristics.
This means users see route outcomes and settlement semantics, not the raw internal routing math.
What may remain internal
The route model is always shown. The full venue-by-venue and hop-by-hop graph may remain internal when provider/runtime data is not publicly exposed.
What destination chain selection changes
Destination chain selection defines where final payout is prepared and settled. The deposit network is the routed origin context while settlement adapts to your selected destination network and asset.
What settlement window means
Settlement window is the interval in which payout can complete after routing and network confirmations. On a multi-network route, this can vary more due to route depth.
What stays unchanged
- DEX-only execution policy.
- Non-custodial flow from user perspective.
- Same order lifecycle and status progression model.
What route visibility means
Route visibility is structured in three layers: the route model (always visible), execution detail visibility (shown when runtime fields exist), and routing-layer managed internals (may remain non-public).
What the user sees in UI
- Route type and a short route note on the landing and swap widget.
- Settlement notes on swap and order views.
- The route model for multi-network routes.
- Execution detail rows on the order page when runtime data is available.
FAQ
- Why do some pairs use a multi-network route?
- Not every pair has deep direct liquidity between two networks. A multi-network route settles across several networks to deliver reliably to your destination, while keeping the same order API and lifecycle.
- Does a multi-network route change custody?
- No. The flow remains non-custodial from the user perspective: you send from your wallet and track the order through the same lifecycle.
- Does the route reveal every internal venue and hop?
- Not always. The UI shows the route steps and execution details when available. Some routing-layer details may remain internal if providers do not expose them publicly.
- Why can a multi-network route take longer?
- Settlement can vary with route depth and network confirmation timing. This is reflected as a route-dependent settlement window.
- What is shown to users versus kept internal?
- User-visible signals include the route type, route steps, timeline, and available execution rows. The full private venue graph remains routing-layer managed.
- Can a route settle to a different destination network?
- Yes. The deposit network is the routed origin, while settlement is prepared for your selected destination network and asset.