zkSync Era: A ZK Rollup For Scaling Ethereum

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.

License

zkSync Era is distributed under the terms of either

Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Official Links

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 bounties 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.

Comments

[RESUBMIT] Use era-boojum-cuda batch inverses

Resubmit of https://github.com/matter-labs/era-shivini/pull/5 with signed commits. Companion to https://github.com/matter-labs/era-boojum-cuda/pull/9.

opened by mcarilli 0
Configure Renovate
Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

Cargo.toml (cargo)

.github/workflows/basic_build.yaml (github-actions)

.github/workflows/cargo-license.yaml (github-actions)

.github/workflows/ci.yaml (github-actions)

.github/workflows/secrets_scanner.yaml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

Start dependency updates only once this onboarding PR is merged

Show all Merge Confidence badges for pull requests.

Enable Renovate Dependency Dashboard creation.

Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.

Ignore node_modules, bower_components, vendor and various test/tests directories.

Group known monorepo packages together.

Use curated list of recommended non-monorepo package groupings.

Apply crowd-sourced package replacement rules.

Apply crowd-sourced workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

chore(deps): update actions/checkout digest to f43a0e5

Schedule: ["at any time"]

Branch name: renovate/actions-checkout-digest

Merge into: main

Upgrade actions/checkout to f43a0e5ff2bd294095638e18286ca9a3d1956744

chore(deps): update trufflesecurity/trufflehog digest to 273f107

Schedule: ["at any time"]

Branch name: renovate/trufflesecurity-trufflehog-digest

Merge into: main

Upgrade trufflesecurity/trufflehog to 273f1077af403043af698c8b3b05c3dd435b0212

chore(deps): update actions/checkout action to v4

Schedule: ["at any time"]

Branch name: renovate/actions-checkout-4.x

Merge into: main

Upgrade actions/checkout to 8ade135a41bc03ea155e62e844d188df1ea18608

Upgrade actions/checkout to v4

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate. View repository job log here.
opened by renovate[bot] 0