ZKsync Chain addresses

To enable seamless interoperability of the ZKsync Chain ecosystem, the Bridgehub, SharedBridges and Chain Type Managers (CTMs) are deployed on L1 and L2 to manage communication between ZKsync Chain contracts.

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

Getting the Chain Type Manager for a ZKsync Chain

The Bridgehub smart contract has the read methods getAllZKChains , that returns all registered chains, and getZKChain that expects a chain ID as an argument and returns the address of the ZKsync Chain contract address.

Mainnet

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

CTM (official)

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

name	chain_id	Address
ZKsync Era	324	0x32400084c286cf3e17e7b677ea9583e60a000324

Learn how to get the Chain Type Manager for a ZKsync Chain

Testnet (Sepolia)

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

CTM (official)

Chains:

name	chain_id	address
ZKsync Sepolia testnet	300	0x9A6DE0f62Aa270A8bCB1e2610078650D539B1Ef9

Learn how to get the Chain Type Manager for a ZKsync Chain

CTM (custom)

ZKsync Chains:

name	chain_id	address
Cronos testnet	282	0xeBf961DC3904725ec916678D875B9625d5F7C29f

Transaction filtering

Learn how to filter transactions on the ZKsync 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.