Bridge Tokens

Most users should bridge through the official web UI. The programmatic flow below is for scripts and AI agents.

Bridge UI

The UI handles approvals, fee estimation, and relay monitoring. On testnet, the sidebar exposes a faucet for test tokens like HORSE — fund your wallet with Hoodi L1 ETH from a public Hoodi faucet first.

Programmatic bridging

Use the flow below only when scripting a bridge transfer or driving it from an agent.

Agent prompt

Paste this into your coding agent:

Reference https://docs.taiko.xyz/SKILL.md
 
Bridge 0.1 WETH from Ethereum L1 to Taiko L2.
Approve the ERC20Vault, then call sendToken with the BridgeTransferOp struct.

Manual mode

Contract addresses

Bridge ERC-20 tokens (L1 → L2)

The mainnet examples below use a generic 18-decimal ERC-20. Adjust parseUnits / --to-wei for tokens with different decimals (for example, USDC has 6 decimals). For the Hoodi testnet version, see Testnet example.

import { ethers } from "ethers";
 
const provider = new ethers.JsonRpcProvider("https://eth.llamarpc.com");
const signer = new ethers.Wallet(process.env.PRIVATE_KEY, provider);
 
const ERC20_ABI = ["function approve(address spender, uint256 amount) returns (bool)"];
const token = new ethers.Contract(TOKEN_ADDRESS, ERC20_ABI, signer);
 
const L1_ERC20_VAULT = "0x996282cA11E5DEb6B5D122CC3B9A1FcAAD4415Ab";
const amount = ethers.parseUnits("100", 18);
 
const tx = await token.approve(L1_ERC20_VAULT, amount);
await tx.wait();

const VAULT_ABI = [
  "function sendToken((uint64 destChainId, address destOwner, address to, uint64 fee, address token, uint32 gasLimit, uint256 amount) op) payable returns (tuple)"
];
 
const vault = new ethers.Contract(L1_ERC20_VAULT, VAULT_ABI, signer);
 
const op = {
  destChainId: 167000,
  destOwner: signer.address,
  to: signer.address,
  fee: 0,
  token: TOKEN_ADDRESS,
  gasLimit: 140000,
  amount: ethers.parseUnits("100", 18),
};
 
// fee = 0 means self-relay; otherwise pass msg.value ≥ fee to cover the relayer
const tx = await vault.sendToken(op, { value: 0 });
const receipt = await tx.wait();
console.log("Bridge tx:", receipt.hash);

Testnet example

Swap in the Hoodi L1 ERC20Vault, a Hoodi L1 RPC, and chain ID 167013:

cast send 0x0857cd029937E7a119e492434c71CB9a9Bb59aB0 \
  "sendToken((uint64,address,address,uint64,address,uint32,uint256))" \
  "(167013,$YOUR_ADDRESS,$YOUR_ADDRESS,0,$TOKEN_ADDRESS,140000,$(cast --to-wei 100))" \
  --rpc-url https://hoodi.ethpandaops.io \
  --private-key $PRIVATE_KEY

Notes

• First bridge deploys a BridgedERC20. The first time a given L1 token is bridged to L2, Taiko deploys a BridgedERC20 contract for it. Subsequent bridges reuse the same contract.
• Bridged USDC ≠ native USDC. Bridging L1 USDC through the ERC20Vault produces a BridgedERC20, not Taiko's native USDC (0x07d83526730c7438048D55A4fc0b850e2aaB6f0b). For native USDC use Circle CCTP.
• No rebase tokens. Rebasing tokens (e.g., stETH) aren't supported. Use the wrapped version (e.g., wstETH).
• Fee-on-transfer tokens. Supported, but the amount credited on L2 reflects the post-fee balance.
• Self-relay. Setting fee to 0 skips the relayer — you finalize the message on L2 yourself via the Bridge UI or by calling processMessage on the L2 Bridge.
• Common L2 tokens: