Documentation Index
Fetch the complete documentation index at: https://docs.jup.ag/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Bridge to Solana lets you transfer crypto assets from other blockchains to Solana. The service uses , a cross-chain interoperability protocol integrated directly into the Jupiter interface as an embedded widget at jup.ag/onboard/debridge. deBridge converts tokens from the source chain into Solana-compatible tokens in a single transaction. You can bridge a wide range of tokens, not just major assets.| Detail | Value |
|---|---|
| Source chains | 9 (Ethereum, BNB Chain, Polygon, Arbitrum, Avalanche, Solana, Linea, Optimism, Base) |
| Tokens | Any token with available liquidity on the source chain |
| Output | Native Solana-compatible tokens (no wrapped tokens) |
| Provider | deBridge |
| Jupiter fees | None |
How deBridge works
deBridge uses a 0-TVL (zero total value locked) architecture. Unlike traditional bridges that rely on liquidity pools where user funds are locked in smart contracts, deBridge uses an intent-based system where external solvers fulfill orders in real time. No user funds are stored in pools that could be targeted by exploits. This means:- No wrapped tokens. You receive native assets on Solana, not synthetic or wrapped versions.
- No pooled liquidity risk. There is no pool of locked funds that could be exploited.
- Market-dependent rates. The exchange rate depends on available liquidity at the time of the transaction.
Jupiter does not operate the bridge. deBridge handles all cross-chain logic, routing, and settlement. Jupiter provides the interface.
Supported source chains
deBridge supports bridging from the following 9 chains to Solana. EVM chains are blockchains compatible with the Ethereum Virtual Machine (such as Ethereum, Polygon, and BNB Chain). L2 (Layer 2) chains are scaling solutions built on top of Ethereum (such as Arbitrum, Optimism, and Base).| Chain | Type |
|---|---|
| Ethereum | EVM |
| BNB Chain | EVM |
| Polygon | EVM |
| Arbitrum | EVM (L2) |
| Avalanche | EVM |
| Optimism | EVM (L2) |
| Base | EVM (L2) |
| Linea | EVM (L2) |
| Solana | Non-EVM |
Solana appears as both a source and destination chain. This means the deBridge widget also supports bridging from Solana to other chains, although the primary Onboard use case is bridging to Solana.
Supported tokens
deBridge supports a large number of tokens on each source chain. The token selector is searchable by name or contract address. Available tokens include major assets (ETH, USDC, USDT, WETH, DAI) and smaller tokens (PEPE, SPX6900, and others), depending on available liquidity on the source chain. The tokens you can receive on Solana depend on the bridging route and available liquidity.How to bridge
Connect your Solana wallet
Connect your Solana wallet to Jupiter. This is the destination wallet by default.
Navigate to Bridge to Solana
Go to jup.ag/onboard/debridge, or select Bridge from other chains via deBridge from the Onboard page.
Select the source chain and token
In the “You pay” section, select the source blockchain and the token you want to bridge. Enter the amount.
Select the destination token
In the “You receive” section, select the token you want to receive on Solana. The output amount is calculated automatically based on the current exchange rate.
Review the transaction details
Before confirming, the widget displays:
- The exchange rate between source and destination tokens
- The estimated fees (gas on source chain + deBridge protocol fee)
- The ETA (estimated time of arrival)
- The price impact percentage
Connect your source wallet
Click Connect wallet to connect the wallet on the source chain (for example, MetaMask for Ethereum). This is separate from your Solana wallet.
Additional features
Send to a different Solana address
Send to a different Solana address
The deBridge widget includes a “Trade and Send to Another Address” option. When enabled, you can enter a different Solana address as the destination instead of your connected wallet. This is useful for bridging on behalf of another wallet.
Settings and routing
Settings and routing
The widget includes a settings panel (gear icon) where you can adjust source chain parameters, including gas fee preferences. A Routing section (expandable at the bottom of the widget) shows details about the route deBridge is using for the transaction.
Fees
| Fee type | Charged by | Details |
|---|---|---|
| Gas fee (source chain) | Source blockchain network | Required to execute the transaction on the source chain. Amount depends on the chain and network congestion. |
| deBridge protocol fee | deBridge | A small fee for the cross-chain transfer. Displayed in the widget before confirmation. |
| Jupiter fee | Jupiter | None |
Transaction speed
The deBridge widget displays an estimated time of arrival (ETA) for each transaction. In many cases, the displayed ETA is approximately 1 second, though actual settlement time may vary depending on source chain finality (the point at which a transaction is considered irreversible on the source blockchain) and network conditions.deBridge vs. USDC Bridge
If you specifically want to bridge USDC, consider the USDC Bridge (CCTP). CCTP (Cross-Chain Transfer Protocol) is a protocol by Circle that transfers USDC through a burn-and-mint mechanism, guaranteeing a 1:1 transfer. Here are the key differences:| deBridge (this page) | USDC Bridge (CCTP) | |
|---|---|---|
| Tokens | Any supported token | USDC only |
| Mechanism | 0-TVL, intent-based | Burn-and-mint (Circle) |
| Slippage | Possible (market-dependent) | None (1:1 transfer) |
| Provider | deBridge | Wormhole + Circle |
| Source chains | 9 chains | 8 chains |
| Wrapped tokens | No | No |
| Best for | Moving any token, or swapping during bridge | Moving USDC with guaranteed 1:1 rate |
Risks and limitations
Having issues with the deBridge bridge? See the Onboard FAQ for troubleshooting and support contacts.

