#blockchain #zk-sync #contract #encode #ethereum #rollup

zksync_l1_contract_interface

Interfaces for interacting with ZKsync contracts

15 releases (1 unstable)

new 28.9.0-non-semver-compat Jul 9, 2025
28.7.0-non-semver-compat Jun 30, 2025
27.5.2-non-semver-compat May 2, 2025
27.0.0-non-semver-compat Mar 21, 2025
0.1.0 Jul 12, 2024

#391 in Magic Beans

Download history 163/week @ 2025-03-19 46/week @ 2025-03-26 33/week @ 2025-04-02 91/week @ 2025-04-09 81/week @ 2025-04-16 85/week @ 2025-04-23 644/week @ 2025-04-30 317/week @ 2025-05-07 64/week @ 2025-05-14 2/week @ 2025-05-21 158/week @ 2025-06-11 77/week @ 2025-06-18 158/week @ 2025-06-25 161/week @ 2025-07-02

554 downloads per month
Used in 13 crates (4 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

~90MB
~1.5M SLoC