[ZK Stack] - initcode too large

[sachanayush47]

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.80.1

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

I was trying to deploy Zk stack on holesky and I encountered this error:
Im using Alchemy's growth plan. Please check the below image.

Edit: Tutorial Im following: https://code.zksync.io/tutorials/custom-zk-chain

Thanks

Expected Behavior

Contracts get deployed

Current Behavior

Contracts not getting deployed.

Repository Link (if applicable)

No response

Additional Details

No response

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[gleenai[bot]]

It appears you are encountering an issue with the initcode size being too large when trying to deploy ZK Stack on the Holesky testnet. This is a common problem when the bytecode generated by the compilation of smart contracts exceeds the limits that the network can handle.

To address this issue, you can try the following solution:

• Optimize Bytecode Size: Modify your hardhat.config.ts file to include the mode: 3 flag, which optimizes the bytecode size during compilation. This can help reduce the size of the generated bytecode, making it possible to deploy your contracts within the size limits of the network.

For more detailed guidance on optimizing your contract's bytecode, you can refer to the hardhat-zksync-solc configuration.

If you continue to face issues, please ensure that your contracts do not inherently exceed the size limits due to their complexity. In such cases, consider simplifying the contracts or splitting them into smaller modules.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[ischasny]

Hello, thanks for the report.

To confirm my understanding - are you running the zk_toolbox and selecting Holesky as the L1 chain? zk_toolbox is using foundry-rs to deploy the L2 contracts to Holesky. I'd recommend ensuring that foundry-rs is properly installed.

Have you tried deploying your contracts to a local node? Does that work?

[dutterbutter]

Thanks for the detailed steps! I was using Infura paid service but seems I hit my daily requests with my reproduction here but I was able to reproduce! So let me investigate further.

[dutterbutter]

@sachanayush47 for the base token (e.g. 0xf2D41a7642d6F62BB3F927e1bA86F0b144ae92AA) did you follow the basic ERC20 example provided in the tutorial? Or is it more custom?

[sachanayush47]

@sachanayush47 for the base token (e.g. 0xf2D41a7642d6F62BB3F927e1bA86F0b144ae92AA) did you follow the basic ERC20 example provided in the tutorial? Or is it more custom?

@dutterbutter It is same as example in the tutorial.

[dutterbutter]

It looks like others have intermittently experienced a similar issue and was resolved using a holsky eth rpc with bigger limits and creating new docker containers. I can confirm using Ankr paid plan. Please see: matter-labs/zksync-era#2726 issue is isolated to Holesky RPC rather then zk_inception.