The bridge
Testnet deployment pending. The bridge modules are part of the genesis
binary, but no mailbox, validator set or route is configured on testnet-0.
Every bridge out fails until governance configures one.
The bridge connects Aeva to other chains through
Hyperlane . Hyperlane carries the messages; Aeva’s own
module, x/bridge, holds the route registry and is the only way through.
| Direction | Out | In |
|---|---|---|
NATIVE_OUT | a native coin (AEVA) is escrowed on Aeva | released from escrow |
SYNTHETIC_IN | the synthetic is burned on Aeva | a remote asset (e.g. USDC) is minted on Aeva as a synthetic |
RIGHT_OUT | units of an OPEN, bridgeable right kind are escrowed | units return from escrow to the recipient |
- Routes are set by governance (
MsgSetRoute), with a rolling cap per direction, and can be paused (MsgPauseRoute). - Rights go out only when the policy is OPEN and the issuer has flagged the kind bridgeable: a policy cannot be enforced on another chain.
- Escrow is checked every block: per route, the escrow equals what went out minus what came back (invariants I8 and I8b).
- There is no path around
x/bridge: direct use of the warp module is refused.
Messages
MsgBridgeOut, MsgSetRoute, MsgPauseRoute, MsgRotateIsm,
MsgSweepEscrowIncome, MsgSetKindBridgeable,
Reference → Messages.
CLI
aevad query bridge routes
aevad tx bridge out <route-id> <0x-remote-recipient> <amount> --from holderOn the explorer
/bridge , routes, caps and transfers (empty on testnet-0 until a route is configured).
Last updated