[ZK Stack] - Request rejected with status code 413

[sachanayush47]

Team or Project

Validium

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.82.0

Operating System

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

Issue Description

We are trying to deploy zksync chain on hoodi testnet but server genesis phase fails because RPC rejects the request with status 413 which mean payload too large. I have experience this issue with both QuickNode and Alchemy. I request team to make appropriate changes to zksync-era to resolve this issue.

Expected Behavior

Request should be successful and server genesis on the database should happen without any issue.

Current Behavior

Unable to perform genesis on the database

Repository Link (if applicable)

No response

Additional Details

Prior Research

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

[JackHamer09]

Looking into the issue!

[JackHamer09]

@sachanayush47 would you be able to share more details, like your full chain configuration? I asked some knowledgeable people and they say the response should be really small, consisting of only 1 log, so the 413 error is quite unexpected.

[sachanayush47]

ayushsachan@fedora:~$ curl -X POST \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc": "2.0",
    "method": "eth_getLogs",
    "params": [{
      "fromBlock": "0x45829",
      "toBlock": "latest",
      "address": "0x85bd0cc71c3b33caa339722542903c6240e7b44",
      "topics": [
        ["0xc5902263211386c79097c5eef7ce2067f0e13359623233314cfa01a5534d1"],
        ["0x00000000000000000000000085bd0cc71c3b33caa339722542903c6240e7b44"]
      ]
    }],
    "id": 1
  }' \
  https://ethereum-hoodi.quiknode.pro/xxxxxxxxxxxxxxxxxxxxxxxxx/
{"jsonrpc":"2.0","id":1,"error":{"code":-32614,"message":"eth_getLogs is limited to a 10,000 range"}}

[JackHamer09]

I'll try to reproduce and get back to you!
In the meantime perhaps you can try to deploy against Ethereum Sepolia testnet, if that's an option for you.

[sachanayush47]

We are at early stage so using sepolia is not feasible for us and sepolia will also have same rate limiting restrictions as of hoodi.

[sachanayush47]

We have been able to fix the issue but now encountering another issue is: Error: One or more tasks failed: ["Task commitment_generator panicked: assertion left == rightfailed: L2 L1 logs tree root mismatch\n left: 0x86df2 62a501f23de307c63e219e624fa2d43fbdc0143c71f192e04d0f64aebd7\n right: 0xb7be8576210b98d3fc1f221dda0fd18dcfaa44086f387d11419d87b0cea5a347"]

I think it is because we have handled the error at server start but server genesis still fails at genesis phase with 413 status code.

[cytadela8]

@sachanayush47 This is issue is typically indicative of an issue with zkstack contract compliation. Please:

• update zksync-foundry
• rm -r contracts; git restore contracts; git submodule update --init --recursive # clean completely the contracts directory
• zkstack dev contracts to recompile

[sachanayush47]

We have fixed the issue.
We have used 2 RPC providers i.e infura and quicknode.
Step 1: Deployed the ecosystem and chain using quicknode
Step 2: For the genesis, we switched to infura as it doent have any rate limits for get_ethlogs function or code knows how to handle this error from infura.
Step 3: Switched back to quicknode and started the server.

You might question why we are using quicknode and infura. We first tried with infura but zkstack fails to gather transactions receipts from infura so then we switched to quicknode.