How to bridge assets to Parallel? (L2 guide)

Understanding Parallel Network Architecture

1. Parallel is a Substrate-based Layer 2 blockchain built to scale Polkadot’s ecosystem through parallelized execution and shared security.

2. It leverages Polkadot’s relay chain for finality and consensus while maintaining its own runtime logic and smart contract capabilities.

3. The network supports EVM-compatible smart contracts via the Frontier framework, enabling seamless migration of Ethereum-based assets and dApps.

4. Native token PAR is used for gas fees, staking, and governance, and acts as the primary settlement medium within the Parallel ecosystem.

5. Cross-chain communication relies on XCM (Cross-Consensus Messaging), allowing trustless message passing between Parallel and other Polkadot parachains or external chains via bridges.

Supported Bridging Pathways

1. The official Parallel Bridge connects Ethereum Mainnet to Parallel via a lock-and-mint mechanism, where ETH or ERC-20 tokens are locked in a multisig vault and mirrored as wrapped assets on Parallel.

2. Polkadot-native bridging uses XCM to transfer DOT, USDT, or other assets from Statemint, Acala, or Moonbeam directly into Parallel’s asset hub.

3. Third-party bridges like Nomad previously offered support but have been deprecated due to security incidents; current documentation only recommends audited, production-ready integrations.

4. Users can also utilize the Parallel Finance DApp interface to initiate cross-chain transfers without requiring CLI tools or manual RPC configuration.

5. Each bridging route enforces strict validation layers including signature verification, light client proofs, and timeout safeguards to prevent stuck or duplicated transfers.

Step-by-Step Asset Transfer Process

1. Connect a compatible wallet such as Talisman or Polkadot.js Extension to the Parallel Finance portal.

2. Select the source chain (e.g., Ethereum) and destination chain (Parallel), then choose the asset — for example, WETH or USDC.

3. Approve the token allowance on Ethereum using MetaMask, followed by signing the bridge transaction with the connected wallet.

4. Wait for confirmation on Ethereum (typically 12–30 blocks), then monitor the Parallel block explorer for minting completion.

5. Once confirmed, the wrapped asset appears in the user’s Parallel wallet balance and is immediately usable in lending, staking, or swap protocols.

Gas and Fee Considerations

1. Ethereum-side fees depend on network congestion and are paid in ETH; users must hold sufficient ETH for both approval and bridge initiation.

2. Parallel-side gas is priced in PAR and dynamically adjusts based on computational weight and storage usage during asset minting.

3. The bridge charges a fixed fee of 0.1% per transfer, deducted from the transferred amount before minting.

4. No additional slippage or liquidity pool fees apply during bridging — those only occur if the user swaps the bridged asset afterward on ParallelSwap.

5. Batch transfers are not supported; each asset type requires a separate bridging session with independent confirmations.

Frequently Asked Questions

Q: Can I bridge BTC directly to Parallel?Bitcoin is not natively supported. Users must first wrap BTC as WBTC on Ethereum, then bridge WBTC via the Ethereum-Parallel bridge.

Q: What happens if my bridged transaction stalls on Ethereum?The bridge monitors pending transactions for up to 72 hours. If no confirmation arrives, funds remain locked in the vault and can be manually reclaimed using the “Rescue” function in the portal.

Q: Are bridged tokens on Parallel fully redeemable back to the source chain?Yes. The reverse path exists for all officially bridged assets, subject to the same lock-and-burn logic and minimum withdrawal thresholds defined in the bridge contract.

Q: Does Parallel support arbitrary message passing for custom smart contract calls across chains?XCM enables generalized message delivery, but only pre-approved call types — such as token transfers and reserve deposits — are whitelisted for security reasons. Arbitrary remote execution is disabled by default.