Skip to main content

Origins & Destinations Image

Overview​

Reactive contracts can listen to event logs on one chain and trigger actions on another. To describe that flow, we use two roles:

  • Origin: the chain where events happen and event logs are read from (the event source).
  • Destination: the chain where Reactive Network delivers a callback transaction (the chain where state changes occur).

Origins and destinations don’t have to be the same. A single reactive contract can subscribe to events from multiple origin chains, and it can send callbacks to one or more destination chains. Your Solidity logic can also choose the destination conditionally.

Callback Proxy Address​

Callbacks are delivered by Reactive Signer, which posts transactions to destination chains. These transactions pass through a callback proxy contract, which makes them verifiable and safe for destination-side contracts.

A destination contract can validate a callback by checking that msg.sender is the relevant callback proxy and the original sender from Reactive Network is Reactive Signer.

Mainnet Chains​

Origin/Destination

Origin is the chain where events originate (and are read from). Destination is the chain where callbacks are delivered in response to those events. Mainnets and testnets must not be mixed: if the origin is a mainnet, the destination must also be a mainnet.

ChainOriginDestinationChain IDCallback ProxyRPC
Arbitrum ✅✅421610xaee8d2deBaB5bE353bfec167C58a549923892e11Chainlist
Avalanche ✅✅431140x8bdfC7e564B90b31c49Cf1079d4c44400F4e14B4Chainlist
Base ✅✅84530xCc780DdE33f56f55dE778D42c930959374a4a068Chainlist
BSC ✅✅560xfc41eE9d3A836b41399BEcce83b06B3e5650f3BBChainlist
Ethereum ✅✅10xFCE1F192F489c988392aBC16E91e359d540d94FeChainlist
HyperEVM ✅✅9990x754120EC7a6eF81E4c5c835AA603C63Da64693E6Chainlist
Reactive ✅✅15970x8888888888888888888888888888888888888888https://mainnet-rpc.rnk.dev/
Robinhood ✅✅46630x476F44b11F5C942c58f4c8E3d0300E5710743585Chainlist
Unichain ✅✅1300x754120EC7a6eF81E4c5c835AA603C63Da64693E6Chainlist

Testnet Chains​

Origin/Destination

Origin is the chain where events originate (and are read from). Destination is the chain where callbacks are delivered in response to those events. Mainnets and testnets must not be mixed: if the origin is a testnet, the destination must also be a testnet.

ChainOriginDestinationChain IDCallback ProxyRPC
Base Sepolia✅✅845320x476F44b11F5C942c58f4c8E3d0300E5710743585Chainlist
Ethereum Sepolia✅✅111551110xAa14d9Cd0f788Ca23d11805986C1d8bd035D23b4Chainlist
Reactive Lasna✅✅53180070x8888888888888888888888888888888888888888https://lasna-rpc.rnk.dev/
Unichain Sepolia✅✅13010x775c9B990ADe401060B78D0e98684eEf8d2466C1Chainlist