feat: Implement gas relay mode and inclusion data for data attestation #2987
This pull request is big! We’re only showing the most recent 250 commits.
Commits on May 14, 2024
Commits on May 15, 2024
Commits on May 16, 2024
-
-
Merge pull request matter-labs#1962 from matter-labs/sb-sync-main-wit…
…h-sync-layer-stable Sb sync main with sync layer stable
Commits on May 20, 2024
Commits on May 21, 2024
-
Merge pull request matter-labs#1992 from matter-labs/kl/sync-layer-bu…
…mp-contracts-v23 chore: bump contracts
Commits on Jun 18, 2024
Commits on Jun 19, 2024
-
feat(contracts!): Kl/sync layer stable1 (matter-labs#2015)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`. --------- Co-authored-by: Stanislav Breadless <[email protected]> Co-authored-by: Raid Ateir <[email protected]> Co-authored-by: Raid5594 <[email protected]> Co-authored-by: Igor Aleksanov <[email protected]> Co-authored-by: Matías Ignacio González <[email protected]>
6 people authoredJun 19, 2024 -
-
Commits on Jun 21, 2024
Commits on Jun 23, 2024
Commits on Jun 24, 2024
-
-
-
Update contracts (matter-labs#2288)
## What ❔ Brings updates from this PR: matter-labs/era-contracts#541 ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`.
-
-
-
-
-
Commits on Jun 25, 2024
-
Merge pull request matter-labs#2295 from matter-labs/sb-custom-da-wit…
…h-sl feat!: Custom DA with SyncLayer
-
-
-
-
Commits on Jun 26, 2024
-
-
-
-
-
-
-
-
feat: more system contracts support, WIP (matter-labs#2273)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`. --------- Co-authored-by: Raid Ateir <[email protected]> Co-authored-by: Raid5594 <[email protected]> Co-authored-by: Stanislav Breadless <[email protected]>
4 people authoredJun 26, 2024
Commits on Jun 27, 2024
-
-
-
-
-
-
-
feat: blobhash-compilation-fix-support (matter-labs#2336)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`.
-
-
-
feat: bump contracts (matter-labs#2342)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
-
-
-
Merge remote-tracking branch 'origin/sync-layer-stable' into lyova-in…
…tegrate-priority-merkle-tree_
Commits on Jun 28, 2024
-
-
-
-
Merge branch 'sync-layer-stable' of github.com:matter-labs/zksync-era…
… into sb-l3-l1-comms-integration
-
-
Commits on Jun 29, 2024
-
-
-
Merge pull request matter-labs#2335 from matter-labs/lyova-integrate-…
…priority-merkle-tree_ feat: integrate priority tree
-
Commits on Jul 2, 2024
-
feat(pubdata): send call encoded pubdata (matter-labs#2360)
## What ❔ Update server to encode pubdata with parameters for DA validator call. ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
Commits on Jul 7, 2024
Commits on Jul 8, 2024
-
Merge remote-tracking branch 'origin/sync-layer-stable' into lyova-me…
…rged-sync-layer-stable
-
-
-
-
-
-
Commits on Jul 10, 2024
Commits on Jul 12, 2024
Commits on Jul 22, 2024
-
-
-
-
-
-
-
-
Merge pull request matter-labs#2339 from matter-labs/sb-l3-l1-comms-i…
…ntegration feat: L3 L1 comms integration
-
-
Merge remote-tracking branch 'origin/sync-layer-stable' into lyova-me…
…rged-sync-layer-stable
Commits on Jul 26, 2024
Commits on Jul 28, 2024
Commits on Jul 29, 2024
Commits on Jul 30, 2024
-
-
-
-
-
-
-
-
-
-
-
-
Merge pull request matter-labs#2504 from matter-labs/sb-fix-rust-unit…
…-tests fix: Fix rust unit tests
Commits on Jul 31, 2024
-
-
-
-
Merge pull request matter-labs#2395 from matter-labs/lyova-merged-syn…
…c-layer-stable feat(sync-layer): megre main & resolve todos
Commits on Aug 6, 2024
-
-
-
-
-
Merge pull request matter-labs#2597 from matter-labs/sb-merge-main-sy…
…nc-layer-stable chore: Merge main into sync layer stable
Commits on Aug 8, 2024
-
-
-
Merge pull request matter-labs#2619 from matter-labs/sb-resolve-env-hack
chore: Resolve env hack
Commits on Aug 14, 2024
-
-
-
-
Merge pull request matter-labs#2650 from matter-labs/sb-sync-kl-sync-…
…layer-reorg chore: Use contracts from kl sync layer reorg
Commits on Aug 15, 2024
-
-
-
-
-
-
-
-
Merge pull request matter-labs#2664 from matter-labs/sb-merge-main-in…
…to-sync-layer-stable-2 chore: Merge main into sync layer stable 2
Commits on Aug 18, 2024
Commits on Aug 19, 2024
-
-
-
-
-
-
-
-
-
-
-
-
-
Merge pull request matter-labs#2677 from matter-labs/sb-sync-kl-reorg
chore: Contracts from kl/sync-layer-reorg
Commits on Aug 20, 2024
-
-
-
-
Merge pull request matter-labs#2681 from matter-labs/sb-make-owner-in…
…it-footprint-smaller feat: make owner init footprint smaller
Commits on Aug 21, 2024
-
fix: script fixes (matter-labs#2701)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
Commits on Aug 23, 2024
-
Merge pull request matter-labs#2712 from matter-labs/sb-new-env-for-s…
…l-stable chore: Fix setting env
-
-
Commits on Aug 24, 2024
Commits on Aug 26, 2024
-
Merge pull request matter-labs#2710 from matter-labs/sync-layer-stabl…
…e-tjg feat: merge main into sync-layer-stable
-
-
Commits on Aug 27, 2024
-
chore: Port kl sync layer reorg to the stable branch (matter-labs#2747)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
-
-
-
-
-
Commits on Aug 28, 2024
-
-
-
-
-
-
-
-
Merge pull request matter-labs#2762 from matter-labs/sb-merge-contrac…
…ts-dev-into-sl-stable chore: Merge contracts dev into sl stable
Commits on Aug 30, 2024
-
chore: message-root-support (matter-labs#2706)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. --------- Co-authored-by: Stanislav Breadless <[email protected]>
Commits on Sep 5, 2024
-
feat(eth-watch): redesign to support Gateway (matter-labs#2775)
Signed-off-by: tomg10 <[email protected]>
Commits on Sep 6, 2024
-
feat(contracts): Remove priority op info from gw (matter-labs#2813)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
Commits on Sep 12, 2024
Commits on Sep 13, 2024
-
-
-
-
-
feat: add da clients (matter-labs#2743)
This PR changes the approach to managing 3rd party DA clients. It was assumed before that they will be stored in a separate repository (hyperchain-da), but to simplify the processes and solve a recursive dependency problem, we decided to manage those within `zksync-era`. The config now defines which DA client will be used, for proto-based configuration it requires adding these lines to general.yaml: ``` da_client: avail: api_node_url: wss://turing-rpc.avail.so/ws bridge_api_url: undefined seed: SEED_PHRASE app_id: 82 timeout: 3 max_retries: 5 ``` for env-based: ``` DA_CLIENT="Avail" DA_API_NODE_URL="localhost:12345" DA_BRIDGE_API_URL="localhost:54321" DA_SEED="SEED_PHRASE" DA_APP_ID=1 DA_TIMEOUT=2 DA_MAX_RETRIES=3 ``` If no config is provided - the default behavior is to use NoDA client (same as now). The `da_client` config might be merged with `da_dispatcher` at some point as the second depends on the first one, so their separation does not make much sense (apart from simplification of the configs). But I'd prefer to do it as a separate PR in case we decide to merge them. The client was reimplemented using only lightweight libraries from crates.io, so it doesn't have any visible impact on build time. To enable seamless integration with 3rd party DA clients in `zksync-era`. <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. -
-
-
Merge pull request matter-labs#2858 from matter-labs/sb-sync-main-sl-…
…stable chore: Sync gateway with main
-
Commits on Sep 17, 2024
-
feat: Kl split-asset-router-support (matter-labs#2790)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
-
chore: bump contracts (matter-labs#2902)
## What ❔ <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`.
Commits on Sep 18, 2024
Commits on Sep 24, 2024
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.