Merge draft v30 #4589
Merged
Merge draft v30 #4589
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## What ❔ Fixes the development setup docs to accurately reflect some missing information - cargo-nextest must be installed with `--version 0.9.109 --locked` as the latest version does not support rust 1.87 - `zkstack dev contracts` must be run before running unit tests <!-- 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 ❔ Accurate documentation is helpful for new and external contributors to be able to set up a working developer environment <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- The `Why` has to be clear to non-Matter Labs entities running their own ZK Chain --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Is this a breaking change? - [ ] Yes - [x] No ## Operational changes <!-- Any config changes? Any new flags? Any changes to any scripts? --> <!-- Please add anything that non-Matter Labs entities running their own ZK Chain may need to know --> None ## 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 `zkstack dev fmt` and `zkstack dev lint`.
## What ❔ Use upgrade timestamp as well as block for switching to fusaka blobs ## Why ❔ Unfortunately ETH foundation doesn't provide the exact block for fusaka, but they have the exact timestamp. So it was decided to use this timestamp and half an hour before and after this as a safety margin https://blog.ethereum.org/2025/11/06/fusaka-mainnet-announcement#fusaka-activation ## Is this a breaking change? - [ ] Yes - [ ] No ## Operational changes <!-- Any config changes? Any new flags? Any changes to any scripts? --> <!-- Please add anything that non-Matter Labs entities running their own ZK Chain may need to know --> ## 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 `zkstack dev fmt` and `zkstack dev lint`. Signed-off-by: Danil <[email protected]>
🤖 I have created a release *beep* *boop* --- ## [29.6.0](core-v29.5.0...core-v29.6.0) (2025-11-17) ### Features * **api:** add EIP-7966 eth_sendRawTransactionSync method ([#4565](#4565)) ([7c4c428](7c4c428)) * bumping versions ([#4555](#4555)) ([1cd803d](1cd803d)) * **eth_sender:** Set fusaka upgrade timestamp ([#4571](#4571)) ([3b5a9df](3b5a9df)) * Improve proving networks setup ([#4563](#4563)) ([42c3f0f](42c3f0f)) * **zkstack:** ensure priority queue is empty before migrating to gateway ([#4539](#4539)) ([a5e1133](a5e1133)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: zksync-era-bot <[email protected]>
## What ❔ - Add stage metrics for `eth_sendRawTransactionSync` ## Why ❔ - `eth_sendRawTransactionSync` is returning slower than sendTransaction + waitForTransactionReceipt so adding metrics to see what the cause is ## Is this a breaking change? - [ ] Yes - [x] No ## Operational changes <!-- Any config changes? Any new flags? Any changes to any scripts? --> <!-- Please add anything that non-Matter Labs entities running their own ZK Chain may need to know --> ## 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 `zkstack dev fmt` and `zkstack dev lint`.
## What ❔ Supplying the upgrade data for mainnet upgrade fior v29. To generate call for a chain upgrade it should be provided as an input to `zkstack dev generate-v29-chain-upgrade` command. ## Why ❔ To allow generation of calldata for chain upgrades. ## Is this a breaking change? - [ ] Yes - [x] No ## Operational changes None ## 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 `zkstack dev fmt` and `zkstack dev lint`.
Deniallugo
requested review from
zksync-admin-bot2
and removed request for
a team
Contributor
|
Hey there! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details: |
Signed-off-by: Danil <[email protected]>
kelemeno
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
What ❔
Why ❔
Is this a breaking change?
Operational changes
Checklist
zkstack dev fmtandzkstack dev lint.