#blockchain #zk-sync

zksync_l1_contract_interface

Interfaces for interacting with ZKsync contracts

27 releases (1 unstable)

new 29.7.0-non-semver-compat Dec 17, 2025
29.6.0-non-semver-compat Nov 17, 2025
29.5.0-non-semver-compat Oct 16, 2025
29.0.0-non-semver-compat Jul 29, 2025
0.1.0 Jul 12, 2024

#10 in #zk-sync

Download history 306/week @ 2025-08-26 249/week @ 2025-09-02 106/week @ 2025-09-09 215/week @ 2025-09-16 349/week @ 2025-09-23 250/week @ 2025-09-30 76/week @ 2025-10-07 259/week @ 2025-10-14 162/week @ 2025-10-21 70/week @ 2025-10-28 73/week @ 2025-11-04 108/week @ 2025-11-11 60/week @ 2025-11-18 78/week @ 2025-11-25 291/week @ 2025-12-02 61/week @ 2025-12-09

511 downloads per month
Used in 15 crates (5 directly)

MIT/Apache

615KB
13K SLoC

ZKsync Era: A ZK Rollup For Scaling Ethereum

Logo

ZKsync Era is a layer 2 rollup that uses zero-knowledge proofs to scale Ethereum without compromising on security or decentralization. Since it's EVM compatible (Solidity/Vyper), 99% of Ethereum projects can redeploy without refactoring or re-auditing a single line of code. ZKsync Era also uses an LLVM-based compiler that will eventually let developers write smart contracts in C++, Rust and other popular languages.

Documentation

The most recent documentation can be found here:

Policies

License

ZKsync Era is distributed under the terms of either

at your option.

Disclaimer

ZKsync Era has been through lots of testing and audits. Although it is live, it is still in alpha state and will go through more audits and bug bounty programs. We would love to hear our community's thoughts and suggestions about it! It is important to state that forking it now can potentially lead to missing important security updates, critical features, and performance improvements.


lib.rs:

Utilities for interacting with the ZKsync L1 contract

Provides utilities both to encode input data for the contract and to decode the data provided by the contract.

This crate utilizes traits provided by the web3 crate to encode and decode data. Tokenizable trait represents items that are encoded via single Token, while Tokenize trait represents items that are encoded via array of Tokens (for example, transaction input).

Dependencies

~98MB
~1.5M SLoC