Ethereum bridges move tokens between Ethereum, rollups and other blockchains, letting traders access liquidity and trading opportunities without using a centralized exchange. They differ in how transfers settle, whether you receive native or wrapped assets, and what you pay to reach the destination. This comparison is based on each provider's official documentation and published features, checked in November 2026; we have not tested the tools hands-on.
Which one to pick
- Ethereum-to-L2 transfers: Across, for relayer-filled transactions with a quoted destination amount.
- Comparing bridge routes: Superbridge, because it displays native and third-party alternatives together.
- Same-asset transfers across supported chains: Stargate, for liquidity-based bridging through its supported pools.
- Cross-chain swaps and limit orders: deBridge, for solver execution with defined output conditions.
- Moving assets between Solana and Ethereum: Mayan Finance, for multiple swap methods and auction-based fills.
- Ethereum-to-Starknet transfers: StarkGate, for access to Starknet's native bridge and integrated alternatives.
Compare Ethereum bridge transfer models
| Tool | Type or Best for | Delivery model and token outcome | Price |
|---|---|---|---|
| Across | Ethereum, rollups and supported cross-chain swaps | Relayers deliver assets using destination liquidity | Variable LP and relayer fees; source gas extra |
| Superbridge | Comparing canonical and alternative routes | Native bridges, third-party protocols and solver routes | No Superbridge fee; provider and network costs apply |
| Stargate | Supported liquidity-pool transfers | Pool-backed delivery; asset representation depends on route | Variable protocol, messaging and gas costs |
| deBridge | Cross-chain trading and conditional orders | Solvers fulfill requested destination assets | Chain flat fee, solver gas and source transaction gas |
| Mayan Finance | Solana and multichain token swaps | Swift solver fills, CCTP or Wormhole-based routes | Method-dependent; Swift has no protocol fee |
| Wormhole | EVM and non-EVM asset transfers | Guardian-verified native or wrapped transfers; solver-based intent settlement | Route-specific gas and applicable relayer or solver fees |
| NEAR Intents | Outcome-based cross-chain exchanges | Market makers fulfill quoted asset intents | Website swaps: 0.2% plus 0.0001% protocol fee |
| StarkGate | Starknet deposits and withdrawals | Canonical settlement and integrated bridge protocols | Network and route-specific execution costs |
The tools
Across
Relayer-based asset transfers
Across is an intent-based bridge connecting Ethereum, rollups and selected non-EVM networks, including Solana. Users specify the asset and destination, while relayers supply their own capital to deliver funds before their reimbursement settles. Its bridge-and-swap interface also supports receiving a different asset on the target network. Across's total transfer fee is the difference between the deposited and received amounts; it covers liquidity-provider and relayer compensation. LP fees rise with pool utilization; relayer fees cover destination gas, capital costs and risk. Source-chain transaction gas is separate from the quoted transfer output.
Choose it when a supported transfer offers acceptable net proceeds without waiting for canonical withdrawal settlement.
Watch out for variable liquidity costs, approval transactions and unavailable token pairs.
Superbridge
Native bridge and route aggregator
Superbridge provides one interface for comparing several ways to move tokens between networks. Its documentation covers Ethereum and many EVM chains, including rollups, with Solana available on some routes. The application can display canonical bridges alongside third-party protocols, including solver-based alternatives. Traders can examine expected proceeds, estimated delivery times and provider charges before selecting a path. It also supports ordinary swaps and transactions combining token conversion with bridging. Superbridge does not add its own platform fee; users pay the selected provider and applicable network charges. Each underlying protocol remains responsible for executing its transfer, so two options displayed in the same interface can have different settlement assumptions.
Choose it when you want to compare native settlement with liquidity-based delivery before committing funds.
Watch out for differences in withdrawal procedures and reliance on the actual route provider rather than the aggregator.
Stargate
Cross-chain liquidity transfers
Stargate uses liquidity infrastructure and LayerZero messaging to move supported assets between blockchains. Its V2 design includes same-asset transfers, while its Hydra architecture extends coverage using asset representations backed by liquidity held on other networks. Consequently, receiving a token with a familiar symbol does not automatically establish that it is the canonical version on that destination. The protocol's transfer interface handles network selection, transaction submission and tracking. Messaging charges, available liquidity and protocol fees affect the quoted outcome. Route support changes; confirm the current path before transferring.
Choose it when a supported liquidity route delivers the token representation you intend to use.
Watch out for pool availability, wrapped Hydra assets and network-specific transfer restrictions.
deBridge
Solver-filled cross-chain orders
deBridge uses its Liquidity Network to execute cross-chain trades without maintaining shared liquidity pools. A user creates an order describing the assets and destination, and independent solvers can fulfill it using their available inventory. The interface supports market bridging and USDC-only cross-chain limit orders, alongside transfers involving Ethereum and Solana. Traders can inspect order status through deExplorer using a transaction hash, wallet or order identifier. Pricing includes a chain-specific flat component and dynamic solver costs, while the source transaction consumes gas. Orders can remain unfilled when no solver accepts the conditions, and cancellation requires a separate on-chain action.
Choose it when you need to exchange assets between networks under specified execution conditions.
Watch out for unfilled orders, cancellation gas and limited solver interest in illiquid tokens.
Mayan Finance
Solana-connected cross-chain swaps
Mayan Finance connects Solana with Ethereum and other supported networks through several execution methods. Swift uses destination-funded drivers competing in auctions; MCTP converts the input to USDC, sends it through Circle's CCTP, then uses drivers to swap into the destination asset. Fast MCTP uses CCTP v2. Wormhole Swap provides another mechanism built around token bridging and cross-chain messages. Swift has no protocol fee, but driver pricing still affects the quoted output. Its interface and developer APIs handle cross-chain swaps, with the appropriate method determined by the selected route and available assets.
Choose it when you need to move between Solana and EVM networks while changing tokens.
Watch out for method-specific fees and refunds that may return an intermediary asset instead of the original input.
Wormhole
Guardian-verified multichain transfers
Wormhole provides cross-chain messaging and token-transfer infrastructure for Portal and Wormhole Connect; its Settlement product also supports intent-based transfers through Mayan Swift and MCTP. Its Guardian network attests to source-chain events, allowing contracts on another network to process verified messages. Wrapped Token Transfers use lock-and-mint, while Native Token Transfers move supported tokens without wrapped representations. Wormhole Connect can also route native USDC through Circle's separate CCTP protocol. Ethereum, Solana, Base and several other networks appear in its feature matrix, but functionality differs by chain. A November 4, 2026 update schedules Linea, Moca and Plume for deprecation on December 2. Traders should inspect the particular route's asset format and supported transfer mechanism.
Choose it when your transaction needs a Wormhole-supported EVM or non-EVM pathway.
Watch out for wrapped-token compatibility, manual redemption requirements and changing network support.
NEAR Intents
Outcome-based cross-chain exchanges
NEAR Intents lets users describe the assets they want to receive rather than manually coordinating every bridging and swap transaction. Market makers compete to satisfy those requests, and the system uses on-chain verification for settlement. Its 1Click API supports quoting, deposit handling, transaction tracking and refunds, while the public website offers a direct trading interface. Published fees distinguish the website's swap charge from the underlying protocol fee; API integrations have their own pricing schedules. Ethereum transactions depend on currently supported asset and network combinations, as well as available market-maker quotes.
Choose it when you prefer specifying a destination asset and letting competing market makers handle execution.
Watch out for quote expiration, differing distribution-channel fees and limited offers for unusual asset pairs.
StarkGate
Starknet bridge interface
StarkGate is Starknet's official bridge interface, combining the canonical Ethereum–Starknet pathway with routes for Bitcoin-to-strkBTC, Solana and native USDC transfers through Circle CCTP. Its native Ethereum bridge follows Starknet's validity-proof settlement process. Returning assets to Ethereum can take up to eight hours according to the platform's published guidance. Users may select automatic withdrawal, which arranges the Ethereum finalization step, or complete that transaction manually after proof verification. StarkGate charges required execution fees separately from the amount entered for transfer. Timing and completion requirements differ across its integrated mechanisms, making route identification important before starting a withdrawal.
Choose it when you want Starknet's official interface and control over the available bridge path.
Watch out for native withdrawal settlement delays and manual finalization costs.
How to bridge USDC from Ethereum to Base
- Identify the token representation. Confirm you hold the intended USDC contract on Ethereum and want native USDC on Base rather than a bridged derivative. Token names alone are insufficient.
- Find available paths. Select Ethereum as the origin and Base as the destination in Across and Superbridge. Check Stargate for a supported equivalent route. Use the same input amount when comparing.
- Read the net output. Record the destination USDC quantity quoted by each interface. Check whether fees are already deducted and whether a separate swap is included in the transaction.
- Inspect settlement requirements. Distinguish relayer delivery, liquidity-pool bridging and any canonical option presented. Examine the estimated completion time and whether the receiving transaction needs manual intervention.
- Budget source-chain gas. Keep enough ETH in your Ethereum wallet for approval and transfer transactions. Include those expenses when calculating the total cost rather than comparing token output alone.
- Verify and sign. Check the official application domain, Base destination address, token contract, spending approval, minimum received amount and transaction details in your wallet before confirmation.
- Confirm delivery before trading. Save the source transaction hash, monitor the bridge's status interface and inspect the destination transaction using a blockchain explorer. Confirm the correct USDC balance is available on Base before placing orders.
Worked example (illustrative): Suppose you bridge 1,000 USDC from Ethereum to Base. Route A quotes 999.1 USDC received with an estimated $8 source gas cost, while Route B quotes 998.8 USDC with $3 gas. Assuming USDC is worth $1 and those gas estimates hold, the total costs are approximately $8.90 and $4.20 respectively. Route B has a smaller token payout but a lower overall transfer expense in this hypothetical comparison.
Bridge security and execution risks
Bridge smart contracts, verification systems and externally funded execution networks introduce risks that differ from those of ordinary same-chain swaps; an attractive quote does not eliminate the possibility of contract failure, delayed settlement or lost funds. Use verified application domains, limit token approvals where practical and test unfamiliar pathways with a small transaction before moving a substantial balance. Never submit a second transfer solely because the first appears delayed; establish its actual status and available recovery procedure first.
Frequently asked questions
What is the difference between a native bridge and a liquidity bridge?
A native bridge follows the source and destination networks' own settlement contracts, whereas liquidity-based systems can deliver funds from capital already available on the receiving chain. Their security assumptions and withdrawal procedures are not identical.
Does bridging USDC always give me native USDC?
No. Some mechanisms issue a wrapped representation backed by assets elsewhere, while CCTP-enabled transfers can move Circle-issued USDC between supported networks. Verify the destination token's contract address before using it as collateral or trading liquidity.
Can I bridge ETH from Ethereum to Solana?
Supported routes exist through products including Wormhole, Mayan Finance and deBridge, but the Solana-side asset may be wrapped ETH or another token selected through a cross-chain swap. Check the precise output mint and wallet compatibility.
Why is my cross-chain swap still pending?
A solver may not accept the offered price, source-chain finality may be incomplete or destination execution may require another action. deBridge exposes order states in deExplorer, while other providers offer their own transfer trackers and recovery instructions.
Do I need gas tokens on both chains?
You generally need the source network's transaction token to initiate a standard transfer. Some routes can provide destination gas or handle execution on your behalf, but you may still need native gas funds for subsequent trades, approvals or withdrawals.
Can I cancel or reverse an Ethereum bridge transfer?
A confirmed source-chain transaction cannot simply be reversed. Certain intent-based orders permit cancellation and refunds before fulfillment, but the procedure, eligible refund asset and required gas depend on the provider and order state.
Sources
Show all 17 sources
- Across: features and supported transfer methods
- Across: fee structure
- Superbridge: routes and charges
- Superbridge: bridging documentation
- Stargate: V2 architecture and liquidity
- Stargate: transfer mechanics
- deBridge: protocol documentation
- deBridge: fees, orders and cancellations
- Mayan Finance: product overview
- Mayan Finance: Swift execution and fees
- Mayan Finance: CCTP transfer method
- Wormhole: supported network features
- Wormhole: token transfer mechanics
- Wormhole: November 2026 network support update
- NEAR Intents: execution model
- NEAR Intents: published fees
- StarkGate: official bridge and transfer FAQ