Skip to main content

Origins & Destinations Image

Overview

The Reactive Network reads event streams and enables transactions across different ecosystems. An Origin acts as an event log provider, delivering events to reactive contracts within the Reactive Network. A Destination is the ecosystem where the actual state transition (transaction) takes place.

Origins and destinations don't have to be the same. Reactive contracts can be configured to work with multiple origins, and the system allows for multiple destinations, enabling conditional selection of which destination ecosystem will be used.

Chains

Callbacks

Not all origin chains are compatible as destination chains. Please refer to the table below before implementing callbacks.

ChainOriginDestinationChain IDCallback Proxy AddressRecommended RPC URL
Ethereum Sepolia111551110x33Bbb7D0a2F1029550B0e91f653c4055DC9F4Dd8https://rpc.sepolia.org
Ethereum Mainnet1https://ethereum-rpc.publicnode.com
Avalanche C-Chain431140x76DdEc79A96e5bf05565dA4016C6B027a87Dd8F0https://api.avax.network/ext/bc/C/rpc
Arbitrum One42161https://arb1.arbitrum.io/rpc
Manta Pacific1690x9299472A6399Fd1027ebF067571Eb3e3D7837FC4https://pacific-rpc.manta.network/http
Binance Smart Chain56https://bsc.drpc.org
Polygon PoS137https://polygon.drpc.org/
Polygon zkEVM1101https://zkevm-rpc.com
opBNB Mainnet204https://opbnb-rpc.publicnode.com
Kopli Testnet53180080x0000000000000000000000000000000000FFFFFFhttps://kopli-rpc.rkt.ink