feat(eth_sender): Set fusaka upgrade timestamp #4571
Merged
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
Deniallugo
force-pushed
the
deniallugo-fusaka-timestamp
branch
from
89534a2 to
e93afaa
Compare
Signed-off-by: Danil <[email protected]>
Deniallugo
force-pushed
the
deniallugo-fusaka-timestamp
branch
from
e93afaa to
dd67acc
Compare
perekopskiy
reviewed
Nov 17, 2025
perekopskiy
approved these changes
Nov 17, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 17, 2025
🤖 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]>
Deniallugo
added a commit
that referenced
this pull request
Dec 17, 2025
## 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]>
Deniallugo
pushed a commit
that referenced
this pull request
Dec 17, 2025
🤖 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 ❔
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?
Operational changes
Checklist
zkstack dev fmtandzkstack dev lint.