bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 12쪽 중 1쪽
A network of interoperable chains, secured by ZK.
Explore comprehensive guides, developer tools, and resources to innovate on ZKsync.
Launch Your Chain
Build Apps on ZKsync
Launch your chain
ZKsync Chains
Learn about interoperable ZK rollups connected through a shared Ethereum bridge.
Running a ZKsync Chain
Get your first ZKsync chain running locally using ZK Stack CLI.
Prividium™
Private, permissioned ZK-Rollup with Ethereum-anchored security and enterprise-grade privacy.
Build on the Elastic Network
Quickstart
Build your first app and deploy it on any chain of the Elastic Network.
ZKsync Chain List
Explore all the chains on the Elastic Network.
Local setup
Learn about the recommended paths of testing and debugging your projects on ZKsync.
Join the Community
Developer Updates
Keep up to date with the latest from the ZKsync team on X.
GitHub Discussions
Get help from the community and contribute to the ZKsync project.
ZKsync Discord
Connect with devs and ZKsync enthusiasts on Discord.
## /zksync-network
ZKsync Docs
Introduction
Welcome to the ZKsync Docs.
Developer Quickstart
If you're new to Web3, get started with a set of curated tutorials
List of chains
Explore the different chains in the Elastic Networks
The
ZKsync Network
is a system of interconnected chains (rollups or validiums), also known as the
Elastic Network
.
ZKsync chains use cryptographic validity proofs to provide scalable and low-cost transactions on Ethereum.
The first chain in this network is
ZKsync Era
, a Layer 2
ZK rollup
.
See the full list of chains here
.
In chains of the Elastic Network, computation is performed off-chain and most data is stored off-chain as well.
Transactions are bundled into batches before generating a validity proof.
As all validity proofs are proven on Ethereum, users enjoy the same security
warranties as in the L1.
ZKsync chains are designed to look and feel like Ethereum, but with a higher throughput and lower fees.
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.
Main features
Security inherited from Ethereum, with zero reliance on 3rd parties.
Preserving key EVM features, such as smart contract composability.
Configurable privacy through
Prividium chains
, enabling confidential state and selective data disclosure.
Native interoperability across ZKsync chains and Ethereum, without bridges or external trust assumptions.
Developer experience
ZKsync chains offer a familiar, Ethereum-native developer experience.
Write smart contracts in Solidity or Vyper.
Compile with standard
solc
and
vyper
for native EVM bytecode.
Use existing frameworks
like
Hardhat
and
Foundry
, libraries like
Ethers
,
Viem
, and tools like
theGraph
,
Thirdweb
, or
Chainlink
.
User experience
Interacting with applications built on
the ZKsync Network
is seamless, cheap and fast.
On
ZKsync chains
:
Transactions have instant confirmations and fast finality on L1.
Transaction fees are extremely low (
average transaction costs
).
Transaction fees can be conveniently paid with ERC20 tokens (e.g. USDC) thanks to
account abstraction and paymasters
.
Support for existing Ethereum-based wallets like Metamask, TrustWallet, Zerion, Rabby, etc.
Setup
Get setup with ZKsync testnet or a local node
## /zk-stack
ZK Stack
ZK Stack Overview
This section provides an overview of the ZK Stack as a key tool to launch and operate ZKsync chains
ZK Stack is a developer friendly modular framework that makes it easy for you to customize & deploy your own interoperable ZK-powered blockchains.
All ZKsync chains in the ecosystem share users & liquidity.
ZKsync Chains
Learn about different kinds of ZKsync Chains and the operation modes they support.
Quickstart
Run your own ZKsync chain using ZK Stack tooling.
Protocol Contributions
ZKsync Chains
Delve into the concept of ZKsync chains and rollup clusters.
## /zksync-protocol
ZKsync Docs
Getting started with ZKsync protocol
Dive deep into ZKsync Protocol, covering everything from rollups to system contracts and fee structures.
Welcome to the ZKsync Protocol documentation! This section is your starting point for understanding the core
components and advanced features of ZKsync. It provides an essential overview to help you effectively build
on ZKsync.
Introduction to Rollups
Explore the fundamentals of rollups for enhanced scalability and lower gas costs.
ZKsync OS
Learn about ZKsync OS, the execution layer.
API
Find the specification for ZKsync Web3 API.
Contracts
Understand the contracts managing ZKsync protocol on L1 and L2
Security
Understand the ZKsync security.
Open Source License
Understand ZK Stack open-source licensing.
ZKsync protocol overview
Learn about ZK Rollups
## /zk-stack/zk-chains
ZK Stack
ZKsync Chains
Delve into the concept of ZKsync chains and rollup clusters.
ZKsync chains represent a sophisticated layer of blockchain architecture called a
rollup cluster
,
consisting of parallel-running chains that achieve consensus and finality on Ethereum's Layer 1 (L1) through a shared bridge.
ZKsync chains are fully interoperable within the Elastic Network, facilitating seamless interactions across chains.
ZKsync chains operate with a shared bridge contract on Ethereum's L1 and include native bridges between individual rollups,
enhancing the overall interoperability and efficiency of the network. Key features of ZKsync chains include:
Security and Trust
: All ZKsync chains must utilize the standardized ZK-engine to maintain consistent security and operational standards,
ensuring that trust and security are derived directly from Ethereum.
High Performance
: ZKsync chains are optimized for massive throughput and low latency,
enabling 10,000+ transactions per second and fast transaction finality without compromising security.
Low Costs
: ZKsync's state of the art infrastructure reduces transaction fees to $0.0001 per transaction,
a 99% reduction from Layer 1 solutions.
Trustless Validating Bridges
: Ensures that rollups within the ZKsync protocol are interconnected without requiring additional trust layers.
Asset Transfers
: Interoperability simplifies the transfer of assets, including burning and minting mechanisms, across the ecosystem.
Unified Governance
: Leveraging a shared governance framework on L1,
the ecosystem can coordinate updates or respond collectively to vulnerabilities, much like a traditional blockchain network would handle a fork.
Development and Deployment
ZKsync chains can be developed and deployed by anyone, fostering a diverse and open ecosystem.
However, for a ZKsync chain to remain trusted and fully interoperable within the Elastic Network, it must utilize the ZK Stack.
This requirement ensures consistency in execution and security across different instances of ZKsync chains.
Modular Implementation
ZKsync chains are designed to be modular, meaning developers can select different components of their blockchain systems or implement their own,
with the exception of the zkEVM core.
This modular approach allows for customization and flexibility in blockchain development
while maintaining core standards necessary for network security and interoperability.
How Interop Works
Interop, or interoperability, is a way to communicate and transact between two ZK Stack chains.
It is made possible by smart contracts that verify transactions across chains using Merkle proofs.
It allows you to:
Observe messages
: Track when an interop message (think of it as a special event) is created on the source chain.
Send assets:
Transfer ERC20 tokens and other assets between chains.
Execute calls:
Call a contract on a remote chain with specific calldata and value.
With interop, you automatically get an account (a.k.a.
aliasedAccount
) on each chain, which you can control from the source chain.
Execute bundles of calls:
Group multiple remote calls into a single bundle, ensuring all of them execute at once.
Execute transactions:
Create transactions on the source chain, which will automatically get executed on the destination chain,
with options to choose from various cross-chain Paymaster solutions to handle gas fees.
You can learn more about how interoperability works and how to use it in the
ZKsync Connect
documentation.
Chain Customizations
The ZK Stack offers several customization options for developers looking to tailor a ZKsync chain to specific needs
or create entirely new blockchain architectures.
This modular approach allows for significant flexibility in configuring transaction sequencing, data availability policies, and privacy features.
Sequencing transactions
Centralized sequencer
- Utilizes a single operator to quickly confirm transactions,
ideal for high-frequency trading (HFT) but requires trust in the operator’s reliability and integrity.
Decentralized sequencer
- Employs a consensus algorithm to determine transaction inclusion,
enhancing security and decentralization but potentially at the cost of higher latency.
It can be any algorithm, so developers can reuse existing implementations (e.g. Tendermint or HotStuff with permissionless dPoS).
Priority queue
- Allows transactions to be submitted directly via an L2 or L1 priority queue,
enhancing censorship resistance, particularly useful for governance protocols.
It’s worth noting that the priority queue will always be available as an escape-hatch mechanism
(even if a centralized or decentralized sequencer is employed), to protect users against censorship by a malicious sequencer.
External protocol
- Offers freedom to integrate any external sequencing protocols,
providing further flexibility and potential integration with existing systems.
External protocols such as Shared Sequencers and Shared Builders can be used.
Custom Base Tokens
The ZK Stack supports using ERC20 tokens as the base token for chain fees instead of ETH.
This enables ZKsync chains to use tokens like USDC or custom community tokens as the base currency for transactions.
Data Availability (DA)
Data Availability (DA) is a critical component in ensuring the security and functionality of ZKsync chain.
It governs how transaction data is managed and made accessible, impacting everything from user privacy to transaction speed and cost.
Below, we detail the various DA options available to developers using the ZK Stack, each tailored for specific security, privacy, and scalability needs.
zk-Rollup
zk-Rollup is the recommended DA policy for most ZKsync chain.
It ensures that the values of every changed storage slot are published as calldata (or blobs, depending on what's
cheaper) on Ethereum's Layer 1 (L1). This approach benefits from:
Amortization of Costs
: Changes that net to zero are not posted, reducing unnecessary data and saving costs.
Inherited Security
: Adopts the full security and censorship-resistance properties of Ethereum, providing robust protection against potential attacks.
Validium
A
validium
offers a more flexible architecture ideal for enterprise applications that require both auditability and confidentiality.
Its key characteristics are:
Controlled DA
: The hosting organization controls data availability.
Although the funds held in validiums are secure against theft, they can be frozen if the data becomes unavailable.
This scenario would not only lock users out of their assets but also potentially damage the reputation and operational status of the hosting organization.
User-Level Privacy
:
Prividium™
enables user-level privacy while giving the chain operator full visibility.
Because the host organization controls data availability, it has the power to restrict access.
Lower Cost
: Validiums offer flexibility for operators to save costs when they don't require a high level of security (e.g. a gaming chain).
zkRollup (Self-hosted)
zkRollup (Self-hosted) represents an innovative approach where users manage their own data:
User-hosted Data
: Users store all relevant data for their accounts, significantly enhancing privacy and reducing on-chain data requirements.
Minimal Data Footprint
: Potentially reduces the data footprint to as little as 5 bytes per user interaction, drastically scaling potential.
Complex Implementation
: While offering tremendous benefits,
this option requires sophisticated technical solutions to manage user interactions smoothly and securely.
Privacy
ZKsync chains support various methods to enhance privacy:
Validium Mode
: Naturally provides privacy as long as the data is kept confidential by the operator.
Privacy Protocols
: Specialized L3 protocols like Aztec or Tornado can be integrated to provide user-level privacy
while benefiting from ZKsync Era’s features like account abstraction.
Self-hosted Rollups
: Represent a long-term solution for privacy and scalability, where users manage their data and confirm state transitions off-chain.
ZK Stack Overview
This section provides an overview of the ZK Stack as a key tool to launch and operate ZKsync chains
ZK Stack Components Overview
Overview of components in the ZK Stack
## /zk-stack/running/quickstart
Running a ZK Chain
Launch a ZKsync chain
Launch a ZKsync chain locally using the ZKsync OS Server.
Prerequisites
Make sure you have
Rust
and version
1.5.1
of
anvil
via
foundry
installed.
Local Chain Setup
To setup a local environment for testing,
clone the
zksync-os-server repo
:
git
clone
https://github.com/matter-labs/zksync-os-server.git
Then move into the repo and run the command below to start a local environment with one L2 chain using protocol version
30.2
.
cd
zksync-os-server
./run_local.sh
./local-chains/v30.2/default
You can find all available chain configurations in the
local-chains
folder.
The first time running this can take a few minutes for the dependencies to
compile.
You should now have two local chains running:
a local L1 chain running at port
8545
a local L2 chain running at port
3050
(chain ID
6565
)
Note that once you end this process, the history of each chain will be
completely erased.
These are in-memory nodes, so they do not persist any
storage of the chains.
Funding a test account
The L1 chain has access to all of the default rich wallets configured with
anvil
.
Rich wallets
Same mnemonic rich wallets
However these addresses do not yet have funds bridged to them on the L2 chains.
Before using your chain, use the command below to bridge funds from a local rich wallet on the L1 to the L2 from inside the
zksync-os-server
repo.
Example: Fund a wallet on chain 6565
Run the command below to bridge funds from a local rich wallet on the L1 chain to the L2 chain.
Replace
<0x_YOUR_BRIDGEHUB_ADDRESS>
with the
bridgehub_address
configured in
local-chains/v30.2/default/config.yaml
.
cargo
run
-p
zksync_os_generate_deposit
--
\
--bridgehub
<
0x_YOUR_BRIDGEHUB_ADDRES
S
>
\
--chain-id
6565
\
--l1-rpc-url
http://localhost:8545
\
--private-key
0x7726827caac94a7f9e1b160f7ea819f172f7b6f9d2a97f992c38edeab82d4110
\
--amount
1
After running,
0x36615Cf349d7F6344891B1e7CA7C72883F5dc049
will have 1 ETH available on the L2 chain.
Using your chain RPC
Your server contains both HTTPS as well as WebSocket (WS) RPC services that are fully web3 compatible (and contain some extra ZK Stack functionalities).
Learn more on the
API reference page
.
Using a Block Explorer
A block explorer is a web-app that lets you view and inspect transactions, blocks,
contracts and more. A
free open source block explorer
is available for your ZKsync chain.
Fee withdrawer
Learn about the Fee Withdrawer, a tool that automates the transfer of collected fees from a ZKsync chain to a base layer address.
Ownership Model
An overview of the most important contracts and roles in the ZK Stack ecosystem.
## /zk-stack/prividium/overview
ZK Stack
Prividium™ Overview
Learn about Prividium™.
Prividium™ lets institutions operate a
private
, permissioned blockchain within their own infrastructure or cloud,
while still
anchoring every transaction to Ethereum
for security and finality.
Sensitive data stays entirely off the public chain, but each state update is verified on Ethereum using zero-knowledge proofs.
Prividium™ is a licensed product. Non-production use requires accepting the license terms;
production deployments require a commercial agreement.
For implementation guides and reference documentation, visit the official
Prividium documentation
.
This design solves a core challenge in enterprise blockchain adoption:
how to maintain privacy and control without giving up interoperability with the broader Ethereum ecosystem
.
Figure: High-level design of Prividium™
Key Differentiators of
Prividium™
Privacy with Control:
Transaction data remains offchain, so internal details such as trades and balances stay confidential.
Each block is verified on Ethereum using zero-knowledge proofs.
Chain operators can selectively disclose specific data (for example, bytecode or token supply) to auditors or regulators without exposing the full ledger.
Role-Based Permissioning:
Prividium™ introduces a dynamic permissioning system managed through the
Admin Dashboard
, replacing static YAML files.
Administrators can:
Add and manage users with Okta or crypto-native (SIWE) authentication
Create roles such as
Trader
,
Auditor
, or
Admin
Assign permissions for contracts and functions directly in the UI
Configure selective disclosure for public endpoints
Access control is enforced by the
Proxy RPC
, which validates user tokens against the
Prividium API
before any on-chain call is executed.
Built-in Compliance:
Single sign-on with Okta, address-level identity binding, and fine-grained access policies are integrated out of the box.
Only authenticated and authorized users can interact with the network, enabling compliance with KYC, KYB, and AML requirements from day one.
Ethereum Anchoring and Interoperability:
Each batch of transactions is finalized on Ethereum using a validity proof, ensuring tamper-proof integrity and trustless settlement.
Assets and data can move between Ethereum and other public or private ZKsync Chains
using native zero-knowledge-based bridges without external custodians.
Scalability and Performance:
As a Validium chain, Prividium™ stores state off-chain, achieving high throughput and low latency.
It supports trading, payments, and settlement use cases that demand both privacy and speed.
What Data Is Public
Only the
state roots
and
zero-knowledge proofs
are posted to Ethereum.
No transaction inputs, addresses, or calldata are visible or inferable from public data.
Selective disclosure can optionally expose verified metrics such as total and circulating token supply, or contract bytecode,
through public read-only endpoints.
Interactions with public networks such as deposits or withdrawals remain visible on the receiving chain,
but all other state data is kept private within the Prividium™ database.
To learn more about data availability in the ZK Stack, visit the
Validium page
.
How It Works
Prividium™ enforces privacy and access control using built-in infrastructure within the ZK Stack.
Users authenticate through
Okta SSO
or
Sign-in With Ethereum (SIWE)
.
All calls pass through the
Proxy RPC
, which checks the user’s token and permissions against the
Prividium API
.
Roles and permissions are defined in the
Admin Dashboard
, not static YAML files.
Access is controlled at the contract-function level, with optional restrictions based on function arguments.
Auditors and regulators can use
Selective Disclosure
to view approved on-chain data without accessing the private ledger.
Full RPC and explorer access remain restricted to chain operators and internal systems.
The chain runs as a Validium. It executes transactions privately and stores its state off-chain in a secure database.
Each batch of transactions produces a zero-knowledge proof and a new state root submitted to Ethereum.
This anchors the private chain to Ethereum, ensuring verifia프로젝트로 돌아가기