Closed wy51084915 closed 7 months ago
It seems your l1 rpc service is rate-limited.
It seems your l1 rpc service is rate-limited.
yes! i have found the error on docs.infura.io. Thanks! But this may not be the real reason. I am using the l1 rpc service on infura and i have checked the requests sent to the infura node. All batch requests failed while other requests survived. i guess the point is that "batch item count exceeded", i will try to limit the batch-size tomorrow.
@wy51084915 You can fine tune the batch size by the l1.rpc-max-batch-size
parameter.
@wy51084915 You can fine tune the batch size by the
l1.rpc-max-batch-size
parameter.
yes! That is what i planed to do yesterday and that worked! Thanks for your reply!
Bug Description i was trying to build my own first L2 OP Chain in the guide of the optimism docs, and when i finally launch op-geth and op-node, an error occurred. the code is on the branch: tutorials/chain
Expected behavior i guess in the normal way, the op-node is responsible for getting blocks from L1, but now there is some problems between their jsonrpc conmmunication. The message they sent to each other seems mismatch their expectation.
Environment Information:
Configurations:
./bin/op-node --l1.rpc-max-batch-size=200 --l2=http://localhost:8551 --l2.jwt-secret=./jwt.txt --sequencer.enabled --sequencer.l1-confs=5 --verifier.l1-confs=4 --rollup.config=./rollup.json --rpc.addr=0.0.0.0 --rpc.port=8547 --p2p.disable --rpc.enable-admin --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY --l1=https://sepolia.infura.io/v3/673923aa4cc74918af3b0a2ef3a3ad5a --l1.rpckind=infura
Logs:
does anyone have some idea? Thanks!