Our endpoints are deployed on several chains, and this list is constantly growing. This page shows only the networks supporting the last version of our protocol.
Proxy Contract Address
Proxy Contract wraps the verification logic of the submitted data. After verifying the data, it feeds the verified parts into the corresponding storage contracts. Each pair has its own Storage Contract, and you can use Retrieving Storage Address to access the Storage of the pair you are interested in.
Proxy Contract has the same address on most of the chains, and it is 0xF27E6e2Ad3e3c24c44adC271fC8576357474BAE0. Currently, you can use it on: Arbitrum, Automata, Avalanche, Base, Berachain, Ethereum Sepolia, Monad Testnet, Optimism, Sonic.
For the chains in the list below, the Proxy Contract Address is different from the default one:
This section is relevant only for the access protocol from the chains with an outdated interface.
Feeder Contract in general is wrapped by the Proxy Contract. You aren't supposed to use it directly unless there's something wrong with the Proxy Contract. You can use it in the same manner as the Proxy Contract for Retrieving Storage Address.
Storages keep track of particular pairs' data. Since we are continuously adding new pairs to our feed, we gave up on posting every storage contract's address in the docs. Instead, we implemented a view method of the Proxy Contract. Visit Retrieving Storage Address for more info.