Step‑by‑Step Tutorial: Cross‑Chain Transfer

Step

What to Do

Why It Matters

On‑Screen Cues

1. Open “IBC Bridge.”

Select “IBC Bridge” from the Transfer category.

Enters dedicated bridging interface.

• Chain & asset dropdowns • Route map widget

2. Choose source & destination.

Dropdown From (e.g., Osmosis) and To(Terra Classic) or vice‑versa.

Defines the IBC channel and available asset list.

• Channel ID auto‑fills • “Unsupported” badge if asset not whitelisted

3. Select the asset.

Pick a native token (e.g., $ATOM). The wallet balance is displayed.

Ensures only valid denominations move through the selected channel.

• Balance / “Max” button

4. Enter amount & review fees.

Type the amount or press Max. The UI calculates: IBC relay fee (gas on both chains), Juris service fee (0 % for now), and estimated arrival amount.

Full cost transparency; avoids under‑funded transfers.

• Fee breakdown table • Net amount highlight

5. Provide destination address (if needed).

From Terra → External: paste the external chain address.From External → Terra:your Terra wallet auto‑populates.

Prevents mis‑routing; bridge validates address prefix.

• Address checksum validation

6. Confirm & sign.

Click “Bridge asset.” Approve the wallet transaction. Funds lock and a transfer hash appears.

Initiates escrow + packet relay.

• Progress indicator (Escrow → Relaying → Received)

7. Track status.

Use the built‑in tracker or copy the tx hash to Mintscan for both chains. You’ll also receive an in‑app toast on completion.

Visibility until final voucher mint or redeem.

• Status chip turns green “Completed”

Pro Tips & Best Practices

Keep gas on both ends – Terra Classic gas is paid in $LUNC; source chains require their own native token (e.g., $ATOM).

Avoid tiny transfers – Fixed relay fees can consume a large percentage of very small amounts; batch instead.

Use stablecoins for safety – Bridging volatile assets can expose you to price swings during the 30‑60 s window.

Check channel status – Rarely, a channel may be paused for upgrades; the UI flags inactive routes in red.

Last updated