Security - ZKsync Docs

ZKsync Era
ZKsync Stack
ZKsync Protocol
Community Code

Getting started with ZKsync protocol

ZKsync protocol overview Transaction lifecycle Blocks and batches L1 <-> L2 communication Bridging assets

Fee model How L2 gas price works How ZKsync Chains charges for pubdata ZKsync fee structure

Finality Data availability Pubdata compression

Overview Features Data Availability Considerations Frequently Asked Questions

Overview Conventions Ethereum JSON-RPC API Debug JSON-RPC API ZKsync JSON-RPC API PubSub JSON-RPC API

Overview Double Resource Accounting Bootloader Execution Environments System Processing of Transactions System Hooks Runner Flow

Overview Deep Dive

ZKsync contracts

L1 contracts L1 ecosystem contracts Shared bridges

Bootloader System contracts Handling L1->L2 ops on ZKsync Handling pubdata Pubdata post 4844

ZKsync Virtual Machine primer VM formal specification

Overview ZK terminology

Overview Circuit testing CodeDecommitter DemuxLogQueue ECRecover KeccakRoundFunction L1MessagesHasher LogSorter Main VM RAMPermutation Sha256RoundFunction StorageApplication

Overview SortDecommitments StorageSorter LogSorter

Boojum gadgets Boojum function - `check_if_satisfied`

Compiler toolchain overview LLVM framework

Audits Bug bounty Withdrawal delay

EVM instructions Nonces Libraries Precompiles Native AA vs EIP 4337 Contract deployment

Overview EVM bytecode deployment and execution EraVM ↔ EVM Contract Interactions Differences Between the EVM Bytecode Interpreter and Ethereum Technical Architecture of the EVM Interpreter EVM Gas Interpretation Pre Deployed Contracts

Introduction Design Paymasters Building smart accounts Signature validation Extending EIP-4337

Upgrades and migrations

ZKsync Docs

ZKsync Protocol
Protocol security

Edit this page Share feedback Open in ChatGPT Open in Claude

Made with ❤️ by the ZKsync Community