Bridging tokens between chains used to mean waiting 30 minutes, hoping nothing went wrong, and refreshing a status page. Across Protocol took a different approach: instead of locking your funds and minting copies on the other chain, it lets independent relayers fill your transfer in seconds — and they only get paid when the job is done right.
In this guide you’ll learn what intent-based bridging actually means, how to use Across Protocol step by step, what to expect on fees and timing, how to fix common problems, and how to spot the fake-bridge scams that keep targeting beginners.
id=”what-is-across”>What Across Protocol Is (Intent-Based Bridging Explained)
Across Protocol is a cross-chain bridge that moves tokens between networks using an “intent-based” model. To understand why that matters, it helps to know how most bridges work first.
A traditional lock-and-mint bridge works like a deposit box. You send your tokens to a smart contract on the source chain, and the contract holds them. Once it confirms the deposit, a matching set of tokens is released or minted to you on the destination chain. This works, but it has two costs: time and trust. Finality on the source chain can take minutes, and the funds sitting in the contract are a honeypot — some of the largest bridge hacks in crypto history drained exactly these kinds of vaults.
Across flips the model. Instead of locking your tokens in a vault, you express an intent: “I want to send X tokens from chain A to address Y on chain B.” Independent parties called relayers watch for these intents and compete to fill them with their own funds on the destination chain. When a relayer fills your transfer, they front the money immediately — that’s why Across transfers can arrive in seconds or minutes rather than waiting for slow finality.
Here’s the part that protects you: the relayer only gets reimbursed from the pool of deposited funds on the source chain if they can prove they actually filled your intent. If nobody fills it, or if a fill is disputed, there are dispute and refund mechanisms so your deposit isn’t simply lost. The security model shifts from “one giant vault holding everyone’s money” to “many relayers competing, reimbursed only after honest fills.”
None of this means bridging is risk-free — smart-contract risk and relayer liveness still matter — but it does mean Across avoids the single-point-of-failure design that powered the biggest bridge exploits. For a broader look at how different bridge designs compare, read our WBTC-to-Base bridging guide, which walks through trust models in plain terms.
How to Use Across Protocol: Step by Step
Using Across is straightforward if you’ve done any on-chain transfer before. The steps below describe the general flow — interface details change over time, so treat the labels loosely and read each screen before you confirm anything.
Step 1: Get your wallet ready. You’ll need a wallet that supports the source chain — for EVM chains, MetaMask or a similar wallet works fine. Make sure you hold the token you want to bridge plus a small amount of the source chain’s native gas token (for example, ETH on Ethereum) to pay for the deposit transaction. If the token you hold is a wrapped version, you may need to unwrap it first; see our WETH-to-ETH unwrapping guide if that’s the case.
Step 2: Open the Across app — carefully. Across’s official site is found by searching for the project’s name and checking the official social profiles; type the address yourself rather than clicking links from search ads, DMs, or comments, because phishing copies of bridge front-ends are one of the most common ways beginners lose funds. Connect your wallet to the app and confirm you’re on the correct source network.
Step 3: Choose your route. Select the token, the source chain, and the destination chain. Enter the amount. Check what’s available on the destination side — Across generally supports major assets across the networks it serves, but supported chains and tokens change over time, so verify the route exists before you go further rather than assuming a pairing is available.
Step 4: Review the quote. The app will show you an estimated fee and the amount you can expect to receive on the destination chain. Read both. If the fee looks unusually high relative to the amount, or the received amount seems off, stop and compare with another route or try a smaller test transfer first.
Step 5: Approve the token (first time only). If you haven’t bridged this token through Across before, your wallet will ask you to approve the Across contracts to move it. Keep this approval scoped to a single transaction where the wallet allows it — unlimited approvals are convenient but riskier, as explained in our token-approvals guide.
Step 6: Confirm the deposit. Sign the deposit transaction in your wallet. Double-check the recipient address shown — it should be your own address on the destination chain. This transaction goes on-chain on the source network and costs gas there.
Step 7: Watch for the fill and receive your funds. Once the deposit confirms, relayers typically fill the intent quickly — many transfers land within seconds to a couple of minutes. Track the transfer in the app’s activity view and, if you want independent confirmation, look up both the source deposit and the destination receipt on a block explorer (our bridge tracking guide explains how).
Fees, Relayers, and Timing
Across fees come in two parts, and understanding the split helps you judge whether a quote is reasonable. The first part is the bridge fee — the cost of the relayer service itself, which compensates relayers for fronting liquidity and taking on the risk of filling your intent. The second is source-chain gas, which you pay to the network for your deposit transaction and which has nothing to do with Across.
Because relayers compete to fill intents, the economics tend to stay tight: relayers who overcharge lose fills to cheaper competitors, and relayers who undercharge can’t cover their costs. In practice, quotes for common routes are usually competitive with other fast bridges, though exact costs vary with network congestion and the route. When the source chain is congested, your gas cost can dwarf the bridge fee — that timing is worth planning around.
Timing is where Across usually shines. The relayer fills your transfer with their own funds as soon as they see your deposit intent, so you don’t wait for full source-chain finality the way lock-and-mint designs require. For most supported routes, fills land in seconds to a few minutes. That said, “usually fast” is not “always fast”: unusual routes, thin relayer coverage, or network congestion can slow things down. If a transfer sits unfilled longer than the app suggests is normal, check the troubleshooting section below before doing anything drastic.
One more thing to know: the amount you receive on the destination chain is the intent amount minus the relayer fee and any liquidity adjustments. Always compare the received amount in the quote — not just the fee line — against what another route would give you.
Common Problems and How to Fix Them
Your transfer hasn’t been filled yet. First, don’t panic — and don’t try to re-send the same transfer. Re-sending doesn’t speed anything up; it just creates a second deposit. Check the app’s activity view and give it the time the app suggests. If it’s been far longer than expected, verify your deposit actually confirmed on the source chain using a block explorer. A deposit that never confirmed (because it ran out of gas or you rejected it) never created an intent, so there’s nothing to fill.
The app says the route is unavailable. Supported chains and tokens change over time. If your pairing doesn’t show up, the route may have been paused or never supported — don’t try to force it through a third-party wrapper you found in a comment thread. Check the project’s official channels (typed by you, not clicked) for announcements.
You sent the wrong token or amount. Cross-chain transfers are generally not reversible by support — there’s no “undo” button on a blockchain. Small mistakes like a slightly wrong amount can sometimes be absorbed, but sending an unsupported token or to a wrong address usually means the funds are stuck or lost. This is why a small test transfer is the best habit a beginner can build.
Your wallet shows a transaction you didn’t make. This is the most urgent scenario. If you ever see unexpected approval requests or transfers, stop everything, don’t sign anything else, and work through recovery steps — our wallet-drainer guide explains what to check first.
Gas fees ate your test transfer. Bridging from a congested network like Ethereum mainnet can cost more in gas than a small test is worth. If gas is high, consider testing on a cheaper route or waiting for quieter network conditions rather than skipping the test entirely — one failed large transfer costs far more than a delayed small one.
Intent-Based vs Lock-and-Mint Bridges
Here’s how the two designs compare across the factors that matter most to a beginner:
| Factor | Intent-based (Across) | Lock-and-mint |
|---|---|---|
| Typical speed | Seconds to minutes (relayer fills immediately) | Minutes to much longer (waits on source finality) |
| Funds at rest | Relayers front fills; deposits reimburse proven fills | Large pooled vault holds all deposits |
| Single point of failure | Reduced — many competing relayers | Higher — the vault is the target |
| Fee structure | Competitive relayer quotes | Often flat protocol fees |
| Route coverage | Depends on relayer activity per route | Depends on deployed contracts per chain |
Neither design is strictly “safer” in every situation — intent-based bridges still rely on smart contracts, relayer honesty is enforced economically rather than eliminated, and both models can have bugs. The honest way to think about it: intent-based designs remove the biggest historical failure mode (the giant honeypot vault), but they introduce new moving parts (relayer markets, dispute logic) that you should weigh honestly.
Staying Safe: Fake Bridges and Approval Hygiene
The biggest risk in using Across isn’t the protocol — it’s the phishing ecosystem around it. Fake bridge front-ends are among the most polished scams in crypto: they copy the real site’s design, buy search ads above the real result, and push links through comments, DMs, and fake “support” accounts. One wrong click, one approval signed on the fake site, and your wallet can be drained.
Your defenses are simple and they work. Type the official address yourself instead of clicking any link, ever — not from search results, not from a helpful stranger, not from a “support” DM. Bookmark it once you’ve confirmed it’s real. Check the URL character by character before connecting your wallet. Keep token approvals narrow and review them periodically. Start with a small test amount on any new route. And remember: no legitimate bridge support agent will ever DM you first, ask for your seed phrase, or ask you to “validate” your wallet by signing a mystery transaction.
FAQs
The Bottom Line
Across Protocol’s intent-based design is one of the more thoughtful answers to bridging’s two classic problems: slow finality and giant honeypot vaults. Relayers competing to fill your transfer means speed, and reimbursement-only-after-honest-fills means a healthier security structure than lock-and-mint designs.
Still, the protocol is only half the story — the other half is your own habits. Type addresses yourself, start with a test transfer, keep approvals narrow, and treat every unsolicited bridge link as hostile. Do those things and Across is a genuinely practical tool for moving value between chains.
This guide is for education only — not financial advice.
