Skip to main content
In short: you can move USDC between Ethereum, Base, Arbitrum and HyperEVM, and WETH between Ethereum, Base and Arbitrum. The money lands in your account on the far side, never in your wallet. A crossing usually lands within about two minutes for USDC and one for WETH, but that is our expectation and not a promise. Up to 1% comes off the amount. A plan can spend only what arrived.

​
Routes

Pick the asset and the destination. The plan chooses the route: USDC takes the first, WETH takes the second. HyperEVM carries USDC only, so WETH cannot go to it or come back. A destination must be a network the service runs on. A plan that crosses to any other network is refused when you save it, because money sent there would have nowhere to be paid out.

​
It lands in your account

A crossing pays the same account on the other network. It cannot pay another address, and it cannot pay your wallet. To reach your wallet, add a send step on the far network after the crossing.

​
What it costs

Up to 1% comes off the amount you send. The plan assumes 0.1% when it checks that you have enough. The fee comes off what you send, so the amount that lands is smaller than the amount that left. Write the next step to spend what arrived, not a number you typed. A step that restates the amount you sent is short by the fee, and the check blocks it before it runs.

​
How long it takes

These are documented expectations. We do not hold a measured median from our own crossings. The run page shows a countdown. When the countdown ends it says “taking longer than usual”, never “failed”, because a slow crossing is not a failed one. On one test crossing from Base to Arbitrum in early October, USDC landed in 5 to 20 seconds. That is one observation.

​
What the plan does while it waits

Most steps finish when their transaction goes through. A crossing finishes when something outside the transaction happens: the other side pays out. So the run waits, and a step on the far network cannot start early. The system enforces that and does not rely on timing. A crossing goes out in a transaction of its own, with its approval. It is never merged with other steps. A card that runs once can include one crossing, and its later steps run on the new network.

​
Under the hood

For people evaluating the design.

​
Routes live in a registry, not in the contracts

Which networks a crossing serves, and which token on one side matches which token on the other, is kept in an on-chain route list. A new network is a new entry in that list. It does not change your account address, and it needs no new account contract. A new route takes effect after a notice period. The last routes added, those to HyperEVM, went in three days before they took effect.

​
A deposit with no counterpart is lost

A deposit on a network with nothing to pay it out on the far side is final and cannot be recovered. This is why both ends are checked: the origin must permit a crossing, and the destination must be served. The destination is checked when you check, save and start the plan.