Jan Zhanal

Zatim jednoduchy workaround pro motylek i one-man-realy je vlozit to qe jako "jednousekove" stafety. Mam to vyzkousene. Parujes jen zavodnika a jesho cislo(trat) z ocadu. Cela finta je, ze v...

Asi bych to po procteni diskuze udelal tak, ze budou jine krabicky na cestu zpet a muzes pouzit ten sql dotaz... J. > Díky, to vyzkouším. Co když budou závodníci...

Same issue as @tmeinlschmidt with base and reth 1.2.0. Will try with --l2.enginekind=geth as suggested.

@exp0nge it did help to pass the problematic place, but got stuck then as you wrote... Now running without zfs, caught up, waiting for a week to confirm setup... I...

reth: > ``` node -vvv --chain=base --rollup.sequencer-http=https://mainnet-sequencer.base.org --rollup.disable-tx-pool-gossip --config=/path/reth.toml --datadir=/path --http --http.addr=localhost --http.port={{ chain_vars.ports.rpc }} --http.corsdomain="*" --http.api=debug,eth,net,trace,txpool,web3,rpc,reth,ots,flashbots --authrpc.addr=localhost --authrpc.port=port --authrpc.jwtsecret=/path/jwt.txt --port 30302 --metrics localhost:port --discovery.port port --engine.persistence-threshold 10 --engine.memory-block-buffer-target 10...

Yes, its running OK.

Same issue here, can we please get some support? ``` sendRawTransaction {"jsonrpc":"2.0","error":{"code":-32016,"message":"over rate limit"} ```

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