FeedProjects
Developers
Settings
🎉 A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
ZKSync

Insights

Proposals

Discussions

Members

Information

Reports

Create Proposal

ZKSync

InsightsProposalsDiscussionsMembersInformationReports
Proposal
Back to Proposals
executedEnds a year ago Â·  Protocol Governor

[ZIP-8] Upgrade Chain Creation Params

By 0xc118...ffaD2C
TitleUpgrade Chain Creation Params
Proposal TypeZIP
One Sentence Summary:This proposal fixes the ChainCreationParams for the chain after the ZIP-6 upgrade.
Proposal AuthorMatter Labs, point of contact is @StanislavBreadless
Proposal Sponsor:Cyfrin
Date Created:6-March-2025
Versionv1
Summary of ActionUpdating the genesisBatchHash, genesisBatchCommitment as well as genesisUpgrade
Link to contractshttps://github.com/matter-labs/era-contracts/pull/1270

[ZIP-8] Upgrade Chain Creation Params

Summary

This ZIP proposes updating the chain creation parameters for new chains to enable chain creation after ZIP6 as well as the setting the new genesisUpgrade contract.

Abstract

When setting ChainCreationParams for a protocol version, we derive genesisBatchHash and genesisBatchCommitment from the zksync-era repository, where these values are continuously tested.

It is expected that system contracts and predeployed contracts (e.g., L2NativeTokenVault) retain the same hashes at genesis as those in the era-contracts repository. However, due to a configuration issue in foundry.toml, the generated hashes varied depending on the presence of the node_modules folder – despite no dependencies being used from it.

This discrepancy resulted in genesisBatchHash and genesisBatchCommitment using contracts that were compiled without node_modules, while other data was compiled with it, making chain initialization impossible.

This upgrade ensures consistency by aligning genesisBatchHash and genesisBatchCommitment with the rest of the contracts, resolving the issue.

Separately, a small issue was found in the genesis upgrade that led to the default wrapped base token having always having the generic “Wrapped Base Token”/“WBT” name and symbol, respectively. This was caused by the genesis upgrade calling itself, which is not possible since it is executed in the context of a diamond proxy. This is also fixed in this release.

Motivation

The main objective is to unblock the creation of new chains after the ZIP6 upgrade. The secondary objective is to fix with the low severity L1GenesisUpgrade issue.

Specification

The new genesisBatchHash and genesisBatchCommitment were taken from the zksync-era after adjusting the compilation to be the same as in the era-contracts repo:

  • genesisBatchHash should be equal to 0x7bdb3d822ad837a3611c436d3be457363a08d06d83b74469831482353a7d8277.
  • genesisBatchCommitment should be equal to 0x81f5e324a4019e4161fb9dc5058a588aa364a551fdd5c0e8788521e64e7ad596.

Also, the new L1GenesisUpgrade contract was deployed at address 0x107e92E7360e595d8129B522ABD458361f32f66C. Its bytecode corresponds to the code from this PR: https://github.com/matter-labs/era-contracts/pull/1270 at commit 37238f745cf7b0bafbbb041601b5549552465893.

Rationale

The upgrade approach chosen ensures that no new protocol version (even patch version) is introduced, which ensures that no actions are needed from the existing chains.

Backwards Compatibility

No issues with backwards compatibility.

Security Considerations

The new genesisBatchHash and genesisBatchCommitment have been already tested on testnet.

The new L1GenesisUpgrade corresponds to the code at commit 37238f745cf7b0bafbbb041601b5549552465893. Its code has been reviewed by OpenZeppelin at commit e3dd33ceee8f803510cbd0debb8ed55fef4007e8.

The diff between the commits can be seen here. Neither L1GenesisUpgrade nor any of its dependencies have been amended.

Continue Reading
Connect Wallet to Add Note
0
Never Miss a ProposalSign up for ZKSync notifications
Cast Vote
Votes 3373
VoterCast PowerVote & Rationale
0x0000...A359De
85.168M

FOR

0x1B68...88eeaD
84.864M

FOR

0x9e0D...Bf986e
61.902M

FOR

0x3FB1...2d4C8A
57.131M

FOR

404 DAO
52.458M

FOR

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Thu March 06 2025, 03:42 pmPublished Onchain 0xc118...ffaD2C
  • Sun March 09 2025, 03:42 pmVoting Period Starts
  • Mon March 17 2025, 07:20 pmEnd Voting Period
  • Mon March 17 2025, 07:29 pmQueue Proposal
  • Mon March 17 2025, 07:36 pmExecute Proposal
Current Results

1-FOR

701.439M

99.78%

2-ABSTAIN

1.476M

0.21%

3-AGAINST

68,504.78

0.01%
Quorum 702.983M/630M
DocumentationBrandingContact Us
Press space bar to start a drag. When dragging you can use the arrow keys to move the item around and escape to cancel. Some screen readers may require you to be in focus mode or to use your pass through key