Across vs. Bebop
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. Bebop is an RFQ and solver-auction DEX. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider Bebop when you want tight same-chain RFQ execution or solver-auction coverage. Confirm the live winner on rates.gg.
What each protocol is
Across. Across is an intents protocol for bridging and cross-chain swaps. Relayers front destination liquidity. Across advertises approximately two-second fills on supported mainnet routes; actual timing depends on the route. Its intent settlement and refund mechanisms are separate from that initial fill. Official docs: Across Docs. App: across.to.
Bebop. Bebop is on-chain trading infrastructure. The RFQ API returns firm quotes from private market makers. The Aggregation API runs a solver auction across DEXs. Settlement is atomic in audited contracts; Bebop does not custody funds. Official docs: Bebop Docs. App: bebop.xyz.
Short version
| Dimension | Across | Bebop |
|---|---|---|
| Role | Intent-based interoperability protocol | RFQ and solver-auction DEX |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Priced into the RFQ or auction quote (spread / solver pricing) |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | EVM networks plus Solana on the trading APIs |
| Settlement | Canonical assets delivered by bonded relayers | On-chain through Bebop settlement contracts |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Audited settlement contracts; signed orders settle through the deployed contracts, with maker liquidity and contract assumptions |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Tight same-chain RFQ execution and solver-auction coverage |
| Docs | Across Docs | Bebop Docs |
Where each fits
Across may fit when:
- You are moving USDC or ETH between major supported chains
- Fast destination fills matter; confirm the estimate for your route
- You want a dedicated intent rail rather than a meta-aggregator
Bebop may fit when:
- You need a firm RFQ from market makers on a supported pair
- The trade is same-chain and price impact on an AMM would be high
- You want solver-auction coverage for longer-tail tokens
Key differences
Across and Bebop should be compared on the job you need to complete: the input asset, destination asset and chain, trade size, execution method and custody assumptions. They may overlap on some routes and complement each other on others. A broader chain list or faster advertised fill does not establish a better net rate. Compare executable quotes in the same window, including gas and every underlying step.
When to use which
- Use Across when you are moving canonical USDC or ETH between major chains and care about speed.
- Use Bebop when you want tight same-chain RFQ execution or solver-auction coverage.
- If both can quote the same route, take the better net output after fees, time and settlement type. Check that print on rates.gg.
FAQ
Which is cheaper, Across or Bebop?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. Bebop: Priced into the RFQ or auction quote (spread / solver pricing). Compare executable quotes for the same size, destination and time window, including gas, underlying venue costs and any extra transfer. Expected output and minimum received are different figures; compare like with like.
Is Across a substitute for Bebop?
Only on overlapping pairs and chains. When both can quote the same route, take the better net output after fees and time. When only one supports the asset or chain, that one is the only option.
Where are the official Across and Bebop docs?
Across: Across Docs. Bebop: Bebop Docs. Live rate comparison: rates.gg.
Official sources
- Across docs: Across Docs
- Across app: across.to
- Across — Introduction: docs.across.to/introduction
- Across — Features and fill times: docs.across.to/introduction/features
- Across — API reference: docs.across.to/api-reference
- Bebop docs: Bebop Docs
- Bebop app: bebop.xyz
- Bebop — API overview: docs.bebop.xyz/build
- Bebop — Settlement contracts: docs.bebop.xyz/core-concepts/settlement-smart-contracts
Get the Best of Both With Rift
Rift is a strong alternative to choosing a single provider. Its rate comparison includes Across and Bebop alongside additional venues, while the Rift API routes orders across its supported execution integrations. You can compare both approaches and get one execution flow for the available route.
Rift adds no router fee and uses secure hardware enclaves to enforce noncustodial execution. Underlying venue fees, spreads and network costs still apply, and availability depends on the asset, chain and order size. The live quote shows the route and expected output.