> For the complete documentation index, see [llms.txt](https://onchain-basics.gitbook.io/onchain-basics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onchain-basics.gitbook.io/onchain-basics-docs/paraswap-how-to-bridge-and-swap-with-fewer-steps.md). # ParaSwap: how to bridge and swap with fewer steps ParaSwap moves crypto between blockchains and swaps into a destination asset. It serves the run where you start with Bitcoin, ETH or a token on one network and need a different asset on another: the source trade, cross-chain transfer and destination trade are planned as one flow, even though they settle in stages. ### How does a cross-chain swap settle? It settles through a source-chain transaction, a cross-chain delivery and a destination-chain payout or swap. Suppose you hold a token on Solana and want ETH on an Ethereum layer 2. A route may trade your token into an asset the bridge can carry, transfer that asset, then trade it into ETH on the destination chain. You care about the final ETH received, rather than the intermediate asset. The transfer mechanism matters. One route may lock or burn an asset and release or mint its counterpart after a message is verified; another may use a solver with liquidity already on the destination chain. Solver liquidity can shorten the wait, while a route that waits for source-chain finality may take longer. A single flow does not make those stages atomic: a confirmed source transaction can still be followed by delayed delivery or a failed destination swap. ### Can I swap from Solana to an Ethereum layer 2? Yes, if a live route supports the exact input token, destination network and output token you select. Check the token’s contract or mint address, because the same ticker can refer to different assets. Check the recipient address on the destination chain as well; a valid address alone does not establish that its owner can use the asset there. For an unfamiliar route, a small transfer tests delivery before you commit the full amount. A ParaSwap cross-chain swap is most useful when the Solana asset must arrive as something different on the layer 2. Compare quotes by minimum ETH received and expected arrival time, then keep enough SOL for the source transaction. Once the route matches your asset and recipient, [ParaSwap](https://paraswap.pro) lets you move and swap the crypto across chains in one flow. Before signing, check whether the quoted output is native ETH or a token representation that you would need to exchange again. ### How much does a cross-chain swap cost? The practical cost is the gap between the input’s market value and the value you receive on the destination chain, plus gas paid separately. A quoted service fee alone misses price impact and execution costs. Read the quote through these components: * Source-chain gas and any source swap spread or price impact. * Bridge or solver fee, including any charge for delivery. * Destination execution gas, whether included in the quote or paid separately. * Destination swap price impact and the quoted minimum received. For example, on a $1,000 input, a 0.5% difference in final output is $5 before separately paid gas. Slippage tolerance is different: setting it to 0.5% limits how far execution may move against the quote; it is not a fixed fee. A starting tolerance around 0.3%–1% may suit a liquid pair, while thin destination liquidity can demand more. If increasing tolerance changes the economics materially, compare another route or split the trade. ### How long does a bridge transfer take? It can take seconds on a fast liquidity route or tens of minutes when the route waits for source-chain finality; congestion and available liquidity can extend either estimate. A Bitcoin-source transfer also depends on confirmations, so its timing differs from a Solana-source transfer. Treat an arrival estimate as a route estimate, not a deadline. If the source transaction is confirmed but the destination balance has not appeared, check the source transaction first, then the route’s delivery status and destination transaction. Do not submit the same transfer again merely because a wallet balance has not updated. A delayed relay and a failed destination swap call for different recovery steps, and the transaction records show which stage needs attention. ### Is a cross-chain swap safe? Its risk depends on the route’s contracts, message verification or solver, token representation and destination execution. Check the exact assets and networks in the quote, the recipient, the minimum received and whether the route relies on a wrapped token. A fast quote can be less useful than a slower one if it leaves you holding an asset with poor destination liquidity. For repeated transfers, save the route details that affect the result, not just its headline speed. ParaSwap can combine the move and swap, but each new token pair can produce a different route and cost. Before each transfer, compare the final asset and minimum received again; those two fields catch more expensive mistakes than a familiar ticker does. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://onchain-basics.gitbook.io/onchain-basics-docs/paraswap-how-to-bridge-and-swap-with-fewer-steps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.