Supported Networks
Support for new blockchains is added through the development of new “data connections.” We define “data connections” as support for reading the state of two distinct Ethereum blockchains (L1s and/or L2s). Data connections can be one-directional or bi-directional.
For example, reading Ethereum Goerli from zkSync Era Goerli is a one-directional data connection as it enables reading arbitrary Ethereum Goerli on-chain data on zkSync Era Goerli. Please note that this is a one-directional connection, as reading zkSync Era Goerli data from Ethereum Goerli is not supported at this time.
Our goal is to enable bi-directional data connections between all Ethereum ecosystem blockchains.
The origin chain is the source which the on-chain data is retrieved from. The destination chain is where we want to access origin chain data from.
Origin | Destination |
|---|---|
Ethereum Goerli* | Starknet Goerli Alpha* |
Ethereum Goerli* | zkSync Era Goerli* |
*Test network
Origin | Destination |
|---|---|
Starknet | Starknet |
Starknet Goerli Alpha* | Starknet Goerli Alpha* |
Starknet Goerli Alpha* | Ethereum Goerli* |
Optimism* | Starknet Goerli Alpha* |
Optimism* | zkSync Era Goerli* |
Ethereum Goerli* | Optimism* |
Arbitrum* | Starknet Goerli Alpha* |
Arbitrum* | zkSync Era Goerli* |
Polygon* | Starknet Goerli Alpha* |
Polygon* | zkSync Era Goerli* |
Ethereum Goerli* | Ethereum Goerli* |
*Test network
If the origin chain and destination chain are the same, arbitrary historical data can be accessed in a verifiable way on that chain. This data can be located in any block, all the way back to the blockchain's first block.
We anticipate support for our first mainnet connections to be available by the fourth quarter of this year. Audits for our codebases will be completed around that time as well.
Last modified 2mo ago