Cross-chain bridge

Cross-chain messaging contracts deployed (May 31, 2026), not carrying value. AereMessenger (0xe54c2329…25477325) is a Hyperlane-Mailbox-compatible cross-chain message bus deployed on chain 2800. No token route carries assets. A warp route contract (AereWarpRouteV3) is deployed and inert, AERE is not in the public Hyperlane registry, and no date is set for any route. Measured on 2026-10-15, AereMessenger accepts a message on one signature from one key (threshold() and validatorCount() both return 1) and has never dispatched one (nonce() returns 0). The form below is a preview: nothing can be sent from it.

The design: move tokens between AERE Network and chains registered in Hyperlane, with messages attested by ECDSA signatures and protected against replay. Today the attestation is one signature from one Foundation key, which is not a multisig and is not enough to carry value.

Bridge architecture (Tier 1.4 + 1.5 contracts deployed, carrying no value)

AereMessenger: 0xe54c2329…25477325, Hyperlane-compatible message bus
AereIGP: 0x61B48615…fdD86E837, Interchain Gas Paymaster
AereSpokePool V1, deprecated: 0xCAB1DBA5…B3181AbD. Do not integrate. Our own registry marks it flawed: its settlement path could release locked principal without properly verifying the delivered output leg. Measured 2026-08-01, it holds a zero balance. Replaced by AereSpokePoolV2Corrected 0xbEF9BF0D…8C623d8d (6,317 bytes live), which is deployed but deliberately inert: no remote spoke is enrolled, so no intent route is open on either version today.
AereERC7683 V1, deprecated: 0x67Fb9830…273ccb29. It routes into the deprecated SpokePool above, so it inherits the same problem. Replaced by AereERC7683V2Corrected 0x8eC4e7F0…381560e3 (7,931 bytes live), also inert.
Patterns: Hyperlane Warp Route (typed token), Across-v3 intent (one-click)
Status: Phase 1, bootstrap validator set. No intent route is live: the V1 intent contracts are deprecated and the corrected V2 pair is deployed but not wired. Across registry and solver onboarding are pending.

The legacy 1-of-1 federated AereBridge was torn down on the Foundation's AERE-only-token mandate. AereMessenger + per-asset Warp Routes are the canonical path going forward.

No route is live, so there is no transfer time to estimate. The attestation threshold is one signature today; a route that carries value needs more independent signers first.