Bridge out

Testnet deployment pending. No bridge route is configured on testnet-0, so the commands below fail with bridge/7 no mailbox (or route not found) until governance configures the mailbox and a route. This page describes the flow the binary implements; it will be updated with the live route ids.

1. Find a route


aevad query bridge routes --node "$AEVA_NODE" -o json | jq '.routes[] | {route_id, direction, status, local_denom}'

A route has a direction — NATIVE_OUT (AEVA out and back), SYNTHETIC_IN (a remote asset such as USDC in and back) or RIGHT_OUT (units of an OPEN, bridgeable right kind out and back) — and a rolling cap per direction.

2. Send

The recipient is a 32-byte hex address on the remote chain (an EVM address left-padded with zeros):


aevad tx bridge out <route-id> 0x000000000000000000000000<20-byte-recipient> 1000000000000000000 --from issuer

The amount is escrowed (native coins, rights) or burned (synthetics) on Aeva and a Hyperlane message is dispatched; it is delivered on the remote chain once the relayer carries it and the ISM validators have signed it.

3. Coming back

A transfer back is a message from the remote chain, processed when the relayer submits it. Aeva checks the origin, the route’s status and the inbound cap, then releases the escrow (or mints the synthetic) to the recipient. For rights, the recipient must pass the asset’s policy on Aeva.

See The bridge.