Rate limit on eth_sendRawTransaction
We experienced an issue with eth_sendRawTransaction
method=eth_sendRawTransaction reqid=1 t=736.988486ms err="429 Too Many Requests: {\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32016,\"message\":\"over rate limit\"},\"id\":14292317}\n"
after debugging we found that this limitation comes from a sequencer
'--rollup.sequencerhttp=https://mainnet-sequencer.base.org'
here we found some information about it
Important: Make sure to configure the --rollup.sequencerhttp flag to point to your sequencer node. This HTTP endpoint is crucial because op-geth will route eth_sendRawTransaction calls to this URL. The OP Stack does not currently have a public mempool, so configuring this is required if you want your node to support transaction submission.
Can we extend this limit, such as a paid subscription etc?
bump
We've been experience this error quite often after the last mandatory [v0.12.3] mainnet update. execution-1 | WARN [05-15|10:38:36.546] Served eth_sendRawTransaction conn=172.18.0.1:53002 reqid=8410787160515896 duration=103.012189ms err="429 Too Many Requests: {"jsonrpc":"2.0","error":{"code":-32016,"message":"over rate limit"},"id":62944}\n" execution-1 | WARN [05-15|10:38:36.554] Served eth_sendRawTransaction conn=172.18.0.1:33478 reqid=3825524845664033 duration=100.697104ms err="429 Too Many Requests: {"jsonrpc":"2.0","error":{"code":-32016,"message":"over rate limit"},"id":62945}\n" execution-1 | WARN [05-15|10:38:36.569] Served eth_sendRawTransaction conn=172.18.0.1:46968 @wbnns
Same issue here, can we please get some support?
sendRawTransaction
{"jsonrpc":"2.0","error":{"code":-32016,"message":"over rate limit"}
How many transactions are you sending?
Hello @danyalprout, I'm sorry but I have no such a metrics but I would expect max 1-2/s. But the issue is not appearing often now (not triggering our monitoring) after we doubled amount of nodes used...
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue was closed because it has been inactive for 5 days since being marked as stale.