Everything you need to bridge a token

A warp route is a pair of linked contracts — one on each chain — that let a token move between them. One side locks (or mints) the token; the other side does the opposite. Nothing about the token's economics changes: the total supply in circulation across both chains stays the same, it's just able to move.

Warp Foundry deploys only your token's own contracts. The shared security (a 3-of-4 validator set) and gas infrastructure are already live in production — nothing extra gets created or configured by you.

This decides the direction of the route:

• Terra Classic — your token already exists there (a native denom or an existing CW20). It gets locked on Terra Classic, and a synthetic copy is minted on the chain(s) you pick in step 03.
• BSC / Ethereum — your token already exists there (the chain's own gas coin, or an existing ERC20). It gets locked on that chain, and a synthetic cw20 is minted on Terra Classic instead. The destination is fixed — there's no step 03 in this direction.

Picking the wrong side doesn't break anything — you can only lock a token that really lives on the chain you pick, so if you don't have it there, the next step (address detection) will tell you.

On an EVM origin (BSC/Ethereum) you choose between:

• Native coin — the chain's own gas token (ETH, BNB). Nothing to type; there's no contract address for a native coin.
• Existing token contract — paste the ERC20 address and click Detect to auto-fill its name, symbol and decimals.

On Terra Classic, only an existing CW20 contract can be the origin — paste its address and click Detect the same way.

The owner wallet is the one that ends up controlling each side's contract — it's the only wallet allowed to later change security settings or the router links (the enroll steps in the checklist, below). It does not have to be the wallet paying for gas on every step — deploy/initialize/create accept any funded wallet, only the two enroll steps require the owner specifically.

Double-check these addresses before continuing — they're only changeable later with the "Switch account" / "Make this the owner" controls explained below, and changing an already-deployed contract's owner means abandoning it and deploying a fresh one.

You only need the wallets for the chains actually involved in your route — a BSC-origin route to Terra Classic never touches Phantom, for example.

Every route walks through the same shape of steps, just mirrored depending on direction:

• Deploy — creates your token's own router contract on one chain (locks the real token, or is ready to mint the synthetic). Any funded wallet can sign.
• Initialize — wires the production security module and fee hook onto that router, and records the owner. Any funded wallet can sign.
• Create the synthetic token (Terra Classic side only) — instantiates the cw20 that gets minted/burned on transfers. Any funded wallet can sign.
• Enroll (both directions) — tells each router where its counterpart lives on the other chain. This is onlyOwner — it must be signed by the exact owner wallet from step 04.
• Verify — reads both sides on-chain to confirm they point at each other, then generates the registry YAML for listing the route.

Steps are resumable — closing the page or hitting an error never loses progress. Click Retry and it picks up where it left off (and safely recovers an already-sent transaction instead of sending a duplicate).

These are two separate things. The service fee (shown on the first page, paid in LUNC, or waived entirely by a coupon) is what Warp Foundry itself charges. It never covers network gas — the actual on-chain transaction costs on Terra Classic (~60 LUNC total across its steps) and whichever other chain you're using (a small amount of that chain's own gas token). Gas always comes out of whichever wallet signs that step, paid directly to the network — Warp Foundry never touches it.

If the service fee shows a price (it's free during testing periods), a coupon code field appears right below it on the first page. Type your 5-character code and click Apply — a valid code waives the fee entirely for that order. Each code works exactly once.

Once Verify finishes, your order status moves to in_review. The generated registry YAML is what gets submitted so your route can appear in the official bridge UI — from the order page you can submit that as a listing request directly.

Message us on Telegram with your order link and, if a step failed, the downloaded log. Prefer to do everything by hand instead of using this tool? Every step here is open source and documented in the self-deploy documentation.