Bridge¶

The BRO-ker bridge moves supported chain-native assets between compatible BRO-ker wallets. It provides a live preview before confirmation and records recent bridge activity in the bot.

Network graph¶

flowchart LR
    SOL[Solana<br/>SOL] <--> ETH[Ethereum<br/>ETH]
    SOL <--> BASE[Base<br/>ETH]
    SOL <--> RH[Robinhood Chain<br/>ETH]
    ETH <--> BASE
    ETH <--> RH
    BASE <--> RH
    ARC[Arc testnet<br/>USDC] -. environment must match .- SOL
    ARC -. environment must match .- ETH
    ARC -. environment must match .- BASE
    ARC -. environment must match .- RH

BRO-ker exposes SOL for Solana bridge routes, ETH for Ethereum, Base, and Robinhood Chain routes, and USDC for Arc. A source and destination must be different.

Arc is currently a testnet surface. BRO-ker blocks value transfer between testnet Arc and mainnet networks. Arc routes can only become usable when both sides are in compatible environments.

Create a bridge preview¶

Open Bridge from the dashboard.
Choose the source and destination networks.
Select the source and destination wallets.
Choose a quick amount, All, or enter a custom amount.
Set bridge slippage if needed.
Request a preview and review it before confirming.

Use Flip to exchange source and destination when the reverse pair is supported.

What the preview shows¶

Field	Meaning
From and to	Source and destination network, asset, and wallet
Expected receive	Provider estimate at quote time
Minimum receive	Lowest output accepted under the selected slippage
Provider	The route source selected for this preview
Fees	Available network, bridge, or route fee estimates
Estimated arrival	Provider estimate, not a guaranteed completion time
Expiry	Time after which a new preview is required

Production bridge execution is sourced through LI.FI, with route availability checked live. The interface can support a network pair even when no usable route exists for the current amount or market conditions.

Confirmation safeguards¶

Before execution, BRO-ker checks that the preview belongs to your Telegram account, has not expired, and still matches the source wallet and selection. The transaction is built for the selected route and signed by the source-network BRO-ker wallet.

Choosing All does not intentionally spend the full native balance. The bot estimates and reserves an amount for source-chain gas, but changing network conditions can still make that reserve insufficient.

Status and history¶

A bridge can pass through submitted, processing, completed, failed, or needs-review states. Cross-chain settlement has at least a source transaction and can include further provider and destination steps.

Use the displayed explorer and provider links to verify progress. If BRO-ker reports an uncertain result, do not immediately submit the same bridge again; first check whether the source transaction spent funds and whether the route is still processing.

Bridge risks¶

Cross-chain routes add smart-contract, liquidity, provider, relayer, price, and destination-network risk. Quotes can expire, the received amount can vary within the accepted limit, and settlement can take longer than estimated.

Verify both wallets, both networks, and the final asset. A bridge moves value between networks; simply selecting another dashboard network does not.