matter-labs · uF4No · Apr 10, 2026 · Apr 1, 2026 · Apr 1, 2026 · Apr 1, 2026
@@ -90,11 +90,8 @@ bun run lint:eslint
 
 We welcome contributions from the community! Check out the following resources to get started:
 
-- [Contribution Overview](https://docs.zksync.io/zksync-network/contributing/documentation)
-- To get started with the project locally and learn how to submit PRs for the project,
-  read the [Contribution Guidelines](/zksync-network/contributing/documentation/contribution-guidelines)
-- To learn how to write your content for documentation, read the
-  [Documentation Styleguide](https://docs.zksync.io/zksync-network/contributing/documentation/documentation-styleguide)
+- [Contributing to the documentation](https://docs.zksync.io/zksync-network/contributing/)
+- [Contributing to ZKsync Protocol](https://docs.zksync.io/zksync-network/contributing/protocol-contributions)
 
 ### Check out Community Code
 

@@ -6,7 +6,7 @@ We have multiple channels available for you to request help.
 ## Where to get help
 
 If you're in need of help with authoring your content for ZKsync Docs,
-first read through the [Contribution Guidelines](https://docs.zksync.io/zksync-network/contributing/documentation/contribution-guidelines)
+first read through [Contributing to documentation](https://docs.zksync.io/zksync-network/contributing)
 to see if it may help answer some questions.
 If the content there does not solve your problem, submit an [issue in GitHub](https://github.com/matter-labs/zksync-docs/issues)
 and we can try to help resolve the issue.
@@ -19,7 +19,7 @@ that may help with any troubleshooting.
 
 If you have questions related to any of our ZKsync tools,
 we recommend that you submit an Issue related to that project.
-You can find the list of our open-source repositories in the [Contribution Track](https://docs.zksync.io/zksync-network/contributing/code)
+You can find the list of our open-source repositories in [Protocol Contributions](https://docs.zksync.io/zksync-network/contributing/protocol-contributions)
 on our ZKsync Docs site.
 
 ## 🪲 Submit a bug report

@@ -14,11 +14,11 @@ description: Welcome to the ZKsync Docs.
   ::
   ::card
   ---
-  title: Environment
+  title: List of chains
   icon: i-heroicons-rocket-launch-solid
   to: /zksync-network/environment
   ---
-  If you're familiar with Web3 and L2s, jump straight to the environment links
+  Explore the different chains in the Elastic Networks
   ::
 ::
 
@@ -38,50 +38,30 @@ ZKsync chains are designed to look and feel like Ethereum, but with a higher thr
 Just like on Ethereum, smart contracts are written in Solidity/Vyper and can be called using the same clients as in
 other EVM-compatible chains.
 
-You don't need to register a separate private key before using it;
-the **ZKsync Network** supports existing Ethereum wallets out of the box.
-
 ## Main features
-:check-icon Security inherited from Ethereum, with zero reliance on 3rd parties.
 
-:check-icon Permissionless EVM-compatible smart contracts.
+:check-icon Security inherited from Ethereum, with zero reliance on 3rd parties.
 
 :check-icon Preserving key EVM features, such as smart contract composability.
 
-:check-icon Standard Web3 API.
+:check-icon Configurable privacy through [Prividium chains](/zk-stack/prividium), enabling confidential state and selective data disclosure.
 
-:check-icon State updates via transaction outputs (also known as state diffs) which provides significant cost savings
-over transaction inputs.
-
-:check-icon Native account abstraction with improvements over EIP4337 (implemented in Ethereum and other rollups).
-
-You can find [more information about ZKsync Era in L2BEAT](https://l2beat.com/scaling/projects/zksync-era#stage).
+:check-icon Native interoperability across ZKsync chains and Ethereum, without bridges or external trust assumptions.
 
 ## Developer experience
 
-ZKsync chains are built to provide a similar developer experience as Ethereum.
-
-:check-icon Smart contracts can be written in Solidity or Vyper.
+ZKsync chains offer a familiar, Ethereum-native developer experience.
 
-:check-icon Use standard `solc` and `vyper` compilers for EVM bytecode execution via [the EVM Interpreter](/zksync-network/zksync-era/unique-features).
+:check-icon Write smart contracts in Solidity or Vyper.
 
-:check-icon Use custom compilers **[zksolc and
-zkvyper](/zksync-protocol/era-vm/compiler/toolchain)** to compile contracts to native EraVM bytecode for more efficient execution.
-
-:check-icon Most contracts work out of the box so migrating projects is seamless.
+:check-icon Compile with standard `solc` and `vyper` for native EVM bytecode.
 
 :check-icon Use existing frameworks
-like [Hardhat](/zksync-network/tooling/hardhat) and [Foundry](/zksync-network/tooling/foundry), libraries like
-[Ethers](https://docs.ethers.org/v6/), [Viem](https://viem.sh/zksync), or
-[web3.js](https://docs.web3js.org/), and tools like [theGraph](https://thegraph.com/),
+like [Hardhat](https://hardhat.org/) and [Foundry](https://www.getfoundry.sh/), libraries like
+[Ethers](https://docs.ethers.org/v6/), [Viem](https://viem.sh/), and tools like [theGraph](https://thegraph.com/),
 [Thirdweb](https://thirdweb.com/zksync), or
 [Chainlink](https://docs.chain.link/data-feeds/price-feeds/addresses?network=zksync&page=1).
 
-:check-icon Web3 API compatibility enables support of most developer tools.
-
-:check-icon Different **[tools for testing and debugging
-locally](/zksync-network/tooling/local-setup/)**.
-
 ## User experience
 
 Interacting with applications built on **the ZKsync Network** is seamless, cheap and fast.
@@ -90,9 +70,5 @@ On **ZKsync chains**:
 - Transactions have instant confirmations and fast finality on L1.
 - Transaction fees are extremely low ([average transaction costs](https://www.growthepie.xyz/fundamentals/transaction-costs)).
 - Transaction fees can be conveniently paid with ERC20 tokens (e.g. USDC) thanks to
-  **[native account abstraction and paymasters](/zksync-protocol/era-vm/account-abstraction)**.
+  **account abstraction and paymasters**.
 - Support for existing Ethereum-based wallets like Metamask, TrustWallet, Zerion, Rabby, etc.
-
-::callout{icon="i-heroicons-cube-transparent-solid" color="blue"}
-To add ZKsync Era to your wallet, see [Connect to ZKsync Era](/zksync-network/zksync-era/network-details).
-::
@@ -14,7 +14,7 @@ An interop message consists of arbitrary data and has two simple properties:
 One example use case for interop messaging would be to unlock experiences on a chain based on activities on another chain.
 
 For a full step-by-step tutorial for sending and verifying interop messages using `zksync-ethers`,
-check out the [interop messages guide](/zksync-network/sdk/js/ethers/guides/interop-messages).
+check out the [interop messages guide](/zksync-network/unique-features/zksync-connect/interop-messages).
 
 ## Sending a message
 

@@ -1,19 +1,19 @@
 ---
-title: Interop Messages
+title: Interop Messages Guide
 description: A guide for sending and verifying interop messages with ZKsync Connect.
 ---
 
 [ZKsync Connect](/zksync-network/unique-features/zksync-connect) enables sending and verifying messages across ZKsync chains via ZKsync Gateway.
 It is the first phase of universal interoperability for the Elastic Network.
 
-An interop message consists of arbitrary data and has two simple properties:
+An interop message consists of arbitrary data and has two simple properties:
 
 1. Anyone can send a message.
 1. Anyone can verify that a given message was successfully sent on some chain.
 
 The message itself has no destination chain or address.
 It’s simply a payload created by a user or contract that gets broadcast.
-There is no expiration for when messages can be verified.
+There is no expiration for when messages can be verified.
 
 Messages can only be sent and verified on ZKsync chains that use ZKsync Gateway.
 To set up a local multichain testing environment with Gateway, check out the [Running ZKsync Gateway locally guide](/zk-stack/running/gateway-settlement-layer).
@@ -29,6 +29,10 @@ The full flow for sending and verifying a message looks like this:
 1. Check that the interop root is updated on the target chain.
 1. Verify the message.
 
+::callout{icon="i-heroicons-light-bulb"}
+This guide is for EraVM-powered chains using the `zksync-ethers` SDK.
+::
+
 ## Sending a message
 
 You can use the `InteropClient` along with the `sendMessage` method to send any message.

@@ -388,7 +388,7 @@ For ZKsync-specific features like native account abstraction or paymaster transa
 - Web3.js: [web3-plugin-zksync](https://sdk.zksync.io/js/web3js).
 - Viem: [ZKsync extension](https://viem.sh/zksync).
 
-For other programming languages, please refer to the [SDK documentation](/zksync-network/sdk).
+For other programming languages, please refer to the SDK documentation.
 
 ## Multichain projects