Open Teamvalid opened 3 weeks ago
Provide a clear and concise description of the bug.
Run the zkSync for testnet Holsky. I gave "https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB" as my L1 RPC URL. Upon deployment I get the following error mentioned in log output.
│ Stderr: │ Error: │ Failed to send transaction │ Context: │ - server returned an error response: error code -32000: invalid: initcode too large │
zkSync should get deployed on Sepoli/Holsky L1 testnet.
Getting error as mentioned above.
Any relevant environment details.
Add any other context about the problem here. If applicable, add screenshots to help explain.
◓ Accepting admin... ◇ Accepting governance... done in 26.427566456 secs │ ◇ Accepting admin... done in 103.801456444 secs │ ◇ Updating token multiplier setter... done in 31.829787283 secs │ │ ■ Command failed to run: forge script deploy-scripts/DeployL2Contracts.sol --legacy --ffi --rpc-url=https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB --broadcast --private-key=71abce8005cdc18fff97e1381c974497ccd24f0d85b5b3d82c4885f90519c73c ──╮ │ │ │ Status: │ │ exit status: 1 │ │ Stdout: │ │ No files changed, compilation skipped │ │ Script ran successfully. │ │ │ │ ## Setting up 1 EVM. │ │ │ │ ========================== │ │ │ │ Chain 17000 │ │ │ │ Estimated gas price: 0.304858025 gwei │ │ │ │ Estimated total gas used for script: 4491042 │ │ │ │ Estimated amount required: 0.00136913019431205 ETH │ │ │ │ ========================== │ │ ## │ │ Sending transactions [0 - 5]. │ │ │ │ Transactions saved to: │ │ /home/xvalx/zk_chain/zksync-era/contracts/l1-contracts/broadcast/DeployL2Contracts.sol/17000/run-latest.json │ │ │ │ Sensitive values saved to: │ │ /home/xvalx/zk_chain/zksync-era/contracts/l1-contracts/cache-forge/DeployL2Contracts.sol/17000/run-latest.json │ │ │ │ │ │ │ │ Stderr: │ │ Error: │ │ Failed to send transaction │ │ │ │ Context: │ │ - server returned an error response: error code -32000: invalid: initcode too large │ │ │ │ │ ├───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ ■ Command failed to run: forge script deploy-scripts/DeployL2Contracts.sol --legacy --ffi --rpc-url=https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB --broadcast --private-key=71abce8005cdc18fff97e1381c974497ccd24f0d85b5b3d82c4885f90519c73c │ Error: │ Failed to send transaction │ │ Context: │ - server returned an error response: error code -32000: invalid: initcode too large │ │ ▲ 0: Command failed to run: forge script deploy-scripts/DeployL2Contracts.sol --legacy --ffi --rpc-url=https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB --broadcast --private-key=71abce8005cdc18fff97e1381c974497ccd24f0d85b5b3d82c4885f90519c73c │ └ Failed to run command
Update.. This issue was solved using a holsky eth rpc with bigger limits and creating new docker containers.
🐛 Bug Report
📝 Description: Command failed to run: forge script deploy-scripts/DeployL2Contracts.sol --legacy --ffi --rpc-url=https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB --broadcast --private-key=71abce8005cdc18fff97e1381c974497ccd24f0d85b5b3d82c4885f90519c73c
Provide a clear and concise description of the bug.
🔄 Reproduction Steps: Error found while deploying zkSync era on Holsky testnet.
Run the zkSync for testnet Holsky. I gave "https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg_SUk3KB" as my L1 RPC URL. Upon deployment I get the following error mentioned in log output.
│ Stderr:
│ Error:
│ Failed to send transaction
│ Context:
│ - server returned an error response: error code -32000: invalid: initcode too large
│
🤔 Expected Behavior
zkSync should get deployed on Sepoli/Holsky L1 testnet.
😯 Current Behavior
Getting error as mentioned above.
🖥️ Environment
Any relevant environment details.
📋 Additional Context
Add any other context about the problem here. If applicable, add screenshots to help explain.
📎 Log Output