Across vs. Socket (Bungee)
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. Socket (Bungee) is a multi-bridge and swap routing engine. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider Socket (Bungee) when you need embedded cross-chain UX and multi-bridge 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.
Socket (Bungee). Socket is the routing engine. Bungee is the product surface (app, widget, API) built on Socket. Together they quote same-chain and cross-chain routes across bridges and DEXs, including deposit-address flows for non-EVM destinations. Official docs: Socket Docs. App: bungee.exchange.
Short version
| Dimension | Across | Socket (Bungee) |
|---|---|---|
| Role | Intent-based interoperability protocol | Multi-bridge and swap routing engine |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Route quote includes underlying venue costs and any affiliate / integrator fee |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Supported Bungee/Socket routes, including selected non-EVM deposit flows |
| Settlement | Canonical assets delivered by bonded relayers | Depends on the selected bridge or DEX route |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Socket contracts plus each underlying bridge |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Embedded cross-chain UX and multi-bridge coverage |
| Docs | Across Docs | Socket 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
Socket (Bungee) may fit when:
- You want a widget, link or API embed rather than a single bridge
- The route is EVM-to-EVM or a supported deposit-address flow
- Destination payload execution after the bridge is useful
Key differences
Across and Socket (Bungee) 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 Socket (Bungee) when you need embedded cross-chain UX and multi-bridge 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 Socket (Bungee)?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. Socket (Bungee): Route quote includes underlying venue costs and any affiliate / integrator fee. 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 Socket (Bungee)?
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 Socket (Bungee) docs?
Across: Across Docs. Socket (Bungee): Socket 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
- Socket (Bungee) docs: Socket Docs
- Socket (Bungee) app: bungee.exchange
- Socket (Bungee) — What is Socket: docs.socket.tech/about/what-is-socket
- Socket (Bungee) — Bungee overview: docs.bungee.exchange/overview/what-is-bungee
- Socket (Bungee) — Integration intro: docs.socket.tech/integrate/introduction
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Across and Socket (Bungee). It brings routes from both together with additional venues on supported pairs, comparing available quotes to find the best net execution for your order. You get the strengths of both through one API.
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.