ZK Chain addresses - ZKsync Docs

To enable seamless interoperability of the ZK Chain ecosystem, the Bridgehub, SharedBridges and State Transition Managers (STMs) are deployed on L1 and L2 to manage communication between ZK Chain contracts.

Learn more about Shared Bridges in the ZK Stack section. To understand the concept of ZK Chains, learn more on ZK Chains.

Getting the State Transition Manager for a ZK Chain

The Bridgehub smart contract has a read method stateTransitionManager that expects a chain ID as an argument. The return value is the address of the StateTransition (a.k.a ZK Chain) contract address.

Mainnet

Description	Address
Bridgehub	0x303a465B659cBB0ab36eE643eA362c509EEb5213
Shared Bridge	0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB
STM (official)	0xc2eE6b6af7d616f6e27ce7F4A451Aedc2b0F5f5C

STM (official)

This STM, is where the official Era chain lives, and all the chains here have the same security guarantees. For chains on other STMs - the security guarantees might differ, please do your own research.

name	chain_id	Address
ZKsync Era	324	0x32400084c286cf3e17e7b677ea9583e60a000324
Cronos	388	0x7b2DA4e77BAE0e0d23c53C3BE6650497d0576CFc

Testnet (Sepolia)

Description	Address
Bridgehub	0x35A54c8C757806eB6820629bc82d90E056394C92
SharedBridge	0x3E8b2fe58675126ed30d0d12dea2A9bda72D18Ae
STM (official)	0x4e39E90746A9ee410A8Ce173C7B96D3AfEd444a5
STM (custom)	0x762b5F15CAd9880ace81776f9046d6a52DD67a9b

STM (official)

Chains:

name	chain_id	address
ZKsync Sepolia testnet	300	0x9A6DE0f62Aa270A8bCB1e2610078650D539B1Ef9
Gravity testnet	326	0x0e4Bd2E8D953a0234Fb1122FFB848B49522308eC
Abstract testnet	11124	0x8aD52ff836A30f063dF51A00C99518880B8b36ac
Sophon testnet	531050104	0xDd02368f378EeD3779B358D2020a77e4D022236D
obsolete	444	0x2F45Fc02ec23e6D335fdE7B5a5083F053C8C2aD3
obsolete	327	0xB484A3F98bCbAAf50d66292463203c0247B4f3F6

STM (custom )

ZK Chains:

name	chain_id	address
Cronos testnet	282	0xeBf961DC3904725ec916678D875B9625d5F7C29f

Transaction filtering

Learn how to filter transactions on the ZK chain, including L1→L2 and L2 transactions.

Getting started with ZKsync protocol

Dive deep into ZKsync Protocol, covering everything from rollups to system contracts and fee structures.