[OP Stack Deployment] Failed to fetch receipts of L1 block: Response is too big

[dev-jb]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I am getting this issue with op-node. The op-node is stopped working when fetching the receipt of L1 block with hash: 0xea952327a64e94475ace932a3682ce09962fd671735e566198359939f18b44b2. This was working fine for more than a week.

The issue:

WARN [01-24|10:07:17.000] Engine temporary error err="temp: failed to fetch receipts of L1 block 0xea952327a64e94475ace932a3682ce09962fd671735e566198359939f18b44b2:16691990 (parent: 0xcefb6190abadbb0c58be1efcbf696e2d0f6e38f8b4ffbb87ff6c564ddeea1226:16691989) for L1 sysCfg update: Response is too big"

The block details of hash: 0xea952327a64e94475ace932a3682ce09962fd671735e566198359939f18b44b2

{"jsonrpc":"2.0","id":1,"result":{"hash":"0xea952327a64e94475ace932a3682ce09962fd671735e566198359939f18b44b2","parentHash":"0xcefb6190abadbb0c58be1efcbf696e2d0f6e38f8b4ffbb87ff6c564ddeea1226","sha3Uncles":"0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347","miner":"0x0000000000000000000000000000000000000000","stateRoot":"0x0000000000000000000000000000000000000000000000000000000000000000","transactionsRoot":"0xf1d8aed1051064d6be85d4811b2feaf3eafca7e39b9c72f4914028f5d07ac316","receiptsRoot":"0xa223397cfaaee734995855643c0aa57acd85a53f6e8eb3c695eb371e3c03120a","logsBloom":"0x00000000020000000000000000000000000000000000000000000000400000000000000000000000000000000000000000080000000000000000000020000400000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000020000000000000000000800000000000000000000000000000000000000000000000000000040000000080000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000","difficulty":"0x0","number":"0xfeb316","gasLimit":"0x1c9c380","gasUsed":"0x1ab33c6","timestamp":"0x67931d9c","extraData":"0x","mixHash":"0x0000000000000000000000000000000000000000000000000000000000000000","nonce":"0x0000000000000000","baseFeePerGas":"0x5f5e100","withdrawalsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","blobGasUsed":"0x0","excessBlobGas":"0x0","parentBeaconBlockRoot":"0x0000000000000000000000000000000000000000000000000000000000000000","size":"0x789","uncles":[],"transactions":["0x7422a12869601a2bc2f296307e0f310d2887be29411286a75c5e5f270284b07c"],"withdrawals":[]}}

How to increase the size of the response if that is the actual issue? Or is there any way to bypass the l1Origin?

Logs

No response

Additional Information

No response

Feedback

No response

[imtipi]

op-node version?and what l1 rpc you use?

[dev-jb]

op-node version?and what l1 rpc you use?

Tried with both 1.8.0 and 1.9.1. But same issue. Used local L1 RPC node.

[imtipi]

op-node version?and what l1 rpc you use?

Tried with both 1.8.0 and 1.9.1. But same issue. Used local L1 RPC node.

what L1 network it is,local devnet?

[dev-jb]

op-node version?and what l1 rpc you use?

Tried with both 1.8.0 and 1.9.1. But same issue. Used local L1 RPC node.

what L1 network it is,local devnet?

It's Hype EVM Testnet. https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/evm

[opfocus]

https://github.com/ethereum-optimism/optimism/blob/2537f35a184c3bc5137911ac4dcb317d0c8d8ff7/op-service/sources/eth_client.go#L319
This code may be of value, the source of the error seems to point to rpc