Bridge Portals

The Bridge Portals tool in Lucid, accessible by clicking the ‘Open’ button under the Bridge tool section on the Lucid homepage, is designed to facilitate secure and efficient cross-chain token transfers. It provides an intuitive interface for users to select tokens, chains, and bridges, while also offering features like multi-bridge transfers and transaction history tracking.

This tool simplifies the cross-chain transfer process by automatically determining whether a single bridge or a multi-bridge transfer is required based on the transfer amount. Users can seamlessly select the best routes and bridges for their needs, ensuring an optimized and efficient transfer experience.

What is Bridge Portals and how does it function?

Bridge Portals function similarly to Multi-Bridge Asset Transfers, but the entire process is seamlessly executed within the Lucid platform. Lucid’s Bridge Portals module is the only xERC20 bridge aggregator that helps users discover the fastest and most cost-effective routes for cross-chain asset transfers. It ensures secure, seamless, and highly efficient transactions across multiple ecosystems. It is executed within Lucid.

Single Bridge vs Multi-Bridge Transfers

The system automatically determines whether a single bridge or a multi-bridge transfer is required based on the transfer amount and single-bridge limits. The organisation deployer sets the single bridge limits during the organisation setup on Lucid, ensuring tailored transfer configurations to meet the organisation’s requirements.

Single Bridge Transfer

When transferring a token amount that does not exceed the single bridge token transfer limit, the interface restricts the user to select only one bridge.

1. Example (First Screenshot below):

• Transfer Amount: 200 Test Tokens

• Since the transfer amount is within the limit of a single bridge, the user can only select one bridge from the “Select Bridge” dropdown.

1. Steps for Single Bridge Transfer:

• Select the token to transfer (e.g., TEST0103).

• Choose the destination chain.

• Enter the Receiver Address or click Use Your Wallet Address to auto-fill.

• Under Select Bridge, choose a bridge sorted by parameters such as “Cheapest” or other criteria.

• Verify the fees and limits displayed (e.g., Relayer Fee, Burning Limit, Minting Limit).

• Confirm and proceed with the transfer.

The transfer of 200 test tokens falls within the single bridge transfer limits. As a result, the user is only required to select a single bridge to complete the transfer.

Multi-Bridge Transfer

If the transfer amount exceeds the single bridge limit, the interface automatically enables the multi-bridge option. This allows the user to select multiple bridges to execute the transfer.

1. Example (Screenshot below):

• Transfer Amount: 2000 Test Tokens

• The transfer amount exceeds the single bridge token transfer limit, so the Multi-Bridge Transfer section is activated automatically.

1. Steps for Multi-Bridge Transfer:

• Select the token to transfer (e.g., TEST0103).

• Choose the destination chain.

• Enter the Receiver Address or click Use Your Wallet Address to auto-fill.

Under the Multi-Bridge Transfer section:

• Select multiple bridges from the dropdown. You can add more bridges using the + Add Bridge button.

• Set the Consensus Threshold (e.g., 2 of 2) to ensure successful execution through selected bridges.

• Verify the fees and limits displayed for each bridge (e.g., Relayer Fee, Burning Limit, Minting Limit).

• Confirm and proceed with the transfer.

The user attempts to transfer 2000 test tokens, which exceeds the single bridge transfer limits. Consequently, the Multi-Bridge Transfer section is automatically enabled, allowing the user to select multiple bridges for the transfer.

Transaction History

The Bridge History section provides a detailed record of all past transactions, including:

• Time/Date: When the transaction occurred.

• Chains: Source and destination chains. (see the arrow between chain logos)

• Details: Token type and amount.

• Origin Address: The wallet initiating the transfer.

• Bridges: Bridges used to relay the transfer.

• Status: Consensus achieved (e.g., 2/2 or 3/3).

• Actions: Options to view transaction details in a block explorer and resend transaction.