Cross-Chain Swaps in Pera — Move Assets Across Networks

Updated October 28, 2026

What is a Cross-Chain Swap?

A cross-chain swap lets you turn crypto on another blockchain into ALGO or USDC on Algorand, without leaving the app. It isn’t a bridge: nothing is locked or wrapped. Your crypto is swapped by a provider, and you receive native ALGO or USDC on Algorand.

In Pera, these swaps are part of Pera Fund and are operated by Exodus (XO Swap). Pera provides a non-custodial wallet interface and doesn’t execute or control the swap.

How Cross-Chain Swaps Work (The Simple Version)

You select the asset you want to swap and the source network (e.g., ETH on Ethereum)
Pera Fund generates a deposit address on the source network
You send your assets to that address
The provider processes the swap
The equivalent asset arrives in your Pera Wallet on Algorand (e.g., as ALGO or USDC)

The provider swaps the crypto you send and pays out native ALGO or USDC on Algorand. The process typically takes a few minutes, depending on confirmation times on the source network.

How to Swap Assets Using Pera Fund

The simplest way to bring crypto into Algorand is through Pera Fund, which handles the swap for you.

Open Pera Wallet
Tap Fund
Select Crypto as your input
Choose the asset and network you’re swapping from (e.g., BTC on Bitcoin, ETH on Ethereum)
Select your output: ALGO or USDC
Enter the amount
The first time, read and accept the Exodus Terms and Privacy Policy with Accept & Continue, then confirm the order — Pera Fund generates a deposit address
Send your crypto to that address from the source network
Once processed, your ALGO or USDC appears in your wallet

Supported source networks and assets include BTC, ETH (Ethereum and Base), SOL, AVAX, ARB (Arbitrum), ADA, XRP, BNB, HBAR, SUI, and stablecoins (USDC, USDT, PyUSD) across multiple networks. See the full list in our Pera Fund guide.

Bridging Through dApps

For more advanced bridging options — like bridging specific wrapped tokens or interacting with bridge protocols directly — you can connect Pera Wallet to bridge dApps via Pera Connect.

Open the Discover tab in Pera or navigate to a bridge dApp in your browser
Connect your Pera Wallet via Pera Connect
Follow the bridge protocol’s instructions
Approve transactions in Pera when prompted

Always verify you’re on the correct URL before connecting your wallet.

Important Things to Know

Double-check the network. The most common bridging mistake is sending assets on the wrong network. If Pera Fund expects ETH on Ethereum and you send ETH on Base, those funds may be lost. Always confirm the network before sending.

Confirmation times vary. Bitcoin transactions can take 10–60 minutes. Ethereum varies with gas prices. Algorand settles in seconds. The bottleneck is usually the source network, not Algorand.

Fees. The provider charges its own fees on top of network fees. These are displayed before you confirm. Pera Fund shows the total cost upfront.

Minimum amounts. Pera Fund shows the provider’s minimum and blocks smaller amounts. Don’t manually send less than the quoted amount to the deposit address.

Irreversibility. Once you send assets to a deposit address, you can’t reverse the transaction. Verify the amount, network, and address before confirming.

Troubleshooting

I sent crypto but it hasn’t arrived yet. Check the transaction status on the source network’s block explorer (e.g., etherscan.io for Ethereum, mempool.space for Bitcoin). If the source transaction is confirmed, check the History tab in Pera Fund for the conversion status. Some swaps take 10–30 minutes depending on network congestion.

I sent to the wrong network. Unfortunately, assets sent to the wrong network are usually unrecoverable. Always verify the network matches exactly what Pera Fund specifies.

The amount I received is less than I expected. Conversions include provider fees and market rates at the time of execution. Review the quoted rate in Pera Fund before sending.

Need more help? Visit perawallet.app/contact-us.