The simplest way to bridge an asset into a rollup ecosystem is to use the rollup’s canonical bridge when security and token provenance matter most, and a liquidity bridge when a faster arrival or exit justifies extra trust assumptions.
The minimum route
A rollup is a network that executes transactions separately from its base chain and posts enough data or proof back to it. The base chain is usually called layer 1, or L1; the rollup is layer 2, or L2. A bridge is the smart-contract system that moves value between them.
For a canonical bridge, connect a wallet—an application that controls your blockchain keys—to the rollup’s official bridge, select the source network, destination network, asset, and amount, then approve the token and submit the deposit. The approval lets the bridge contract spend that ERC-20 token; the deposit then locks it on L1 and sends a message to the L2 bridge. The paired L2 token contract credits or mints the corresponding representation to your address.
The L1 transaction confirming is not the finish line. Check that the L2 message has executed and that the token contract is the one recognized by the rollup. A familiar symbol can represent a different contract, especially when a canonical asset and a third-party wrapped version both exist.
Where the alternatives differ
A liquidity bridge removes the wait for canonical settlement by having a relayer pay you from inventory already held on the destination. The relayer later settles the transfer through its own mechanism. This is why liquidity bridges can make an L2-to-L2 transfer feel like one quick transaction, while a canonical withdrawal from an optimistic rollup may wait through a challenge period. A zero-knowledge rollup can usually finalize an exit after its validity proof is accepted.
- Security: a canonical bridge inherits the rollup’s contract and proof system; a liquidity bridge adds relayers, liquidity management, and its own verification assumptions.
- Speed: liquidity wins when the destination has inventory; canonical deposits are often simpler, but canonical withdrawals can be slow.
- Asset identity: canonical routes are usually clearest about which token is native to the destination; fast routes may deliver a wrapped or alternate representation.
That distinction matters when moving USDC from BNB Chain into a rollup and then using a destination venue such as Curve Finance or Kyber Network. The bridge gets the asset onto the right network; it does not automatically find the best swap or guarantee that an application accepts every representation.
Paraswap belongs after the bridge when the destination application requires a different token. Use a route that compares available swap paths for that conversion.
The practical choice
Use the canonical bridge for a large amount, a long-term balance, or any case where verifying the token’s origin matters. Use a liquidity bridge for a smaller, time-sensitive transfer after checking its route, received token contract, fee, and available destination liquidity. The extra convenience is real, but it is buying speed with another layer of assumptions.