Overview
Reactive Contracts send cross-chain callback transactions to destination chains. By default, callbacks are delivered through the Reactive Callback Proxy. Hyperlane Mailboxes provide an alternative transport for these callbacks. The Mailbox contract on each supported chain acts as the entry and exit point for cross-chain messages.
Reactive Contracts still listen to event logs and trigger actions in the same way, only the callback transport changes. Hyperlane transport is useful when:
- A chain does not yet support the Callback Proxy
- You need additional routing flexibility
- You want to integrate Reactive Contracts with existing Hyperlane-based systems
Hyperlane Mailboxes
Hyperlane Demo
See our Hyperlane Demo to understand how to deploy contracts and send messages with Hyperlane mailboxes.
| Chain | Chain ID | Hyperlane Mailbox | RPC |
|---|---|---|---|
| Ethereum | 1 | 0xc005dc82818d67AF737725bD4bf75435d065D239 | Chainlist |
| BSC | 56 | 0x2971b9Aec44bE4eb673DF1B88cDB57b96eefe8a4 | Chainlist |
| Avalanche | 43114 | 0xFf06aFcaABaDDd1fb08371f9ccA15D73D51FeBD6 | Chainlist |
| Base | 8453 | 0xeA87ae93Fa0019a82A727bfd3eBd1cFCa8f64f1D | Chainlist |
| Sonic | 146 | 0x3a464f746D23Ab22155710f44dB16dcA53e0775E | Chainlist |
| Reactive | 1597 | 0x3a464f746D23Ab22155710f44dB16dcA53e0775E | https://mainnet-rpc.rnk.dev/ |