[OP Stack Deployment] <unavailable miner_setMaxDASize RPC on OP-Geth>

[iujiban]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

After successfully running both op-node and op-geth and inserting a new L2 unsafe block, I attempted to connect the OP-Batcher (version v0.1.12.0, matching the op-node version).
However, during startup, the batcher immediately shuts down with the following error:

ERROR[03-25|07:47:25.636] SetMaxDASize rpc unavailable or broken, shutting down. Either enable it or disable throttling. err="the method miner_setMaxDASize does not exist/is not available"

This suggests that miner_setMaxDASize RPC method is expected by the batcher, but the current op-geth node does not expose this method.

Additionally, I’m seeing context cancellation errors when the batcher tries to query L1 and L2:

Logs

batcher

ERROR[03-25|07:47:25.636] SetMaxDASize rpc unavailable or broken, shutting down. Either enable it or disable throttling. err="the method miner_setMaxDASize does not exist/is not available"
INFO [03-25|07:47:25.637] Stopping Batch Submitter
ERROR[03-25|07:47:25.637] Failed to query L1 tip                   err="getting latest L1 block: Post \"https://eth-sepolia.g.alchemy.com/v2/gzTLBFP7R5_FwISjQRiG-xFV0IdfPxiv\": context canceled"
ERROR[03-25|07:47:25.637] Error publishing tx to l1                err="getting latest L1 block: Post \"https://eth-sepolia.g.alchemy.com/v2/gzTLBFP7R5_FwISjQRiG-xFV0IdfPxiv\": context canceled"
INFO [03-25|07:47:25.637] Loading range of multiple blocks into state start=39273 end=39278
WARN [03-25|07:47:25.637] Failed to load block into state          err="getting L2 block: Post \"http://localhost:8547\": context canceled"

Additional Information

[Version Used]
op-node: 1.12.0
op-geth: v1.1.105030

[Command Arguements]
From Op-Geth

./build/bin/geth \
  --datadir ./datadir \
  --http \
  --http.corsdomain="*" \
  --http.vhosts="*" \
  --http.addr=0.0.0.0 \
  --http.api=web3,debug,eth,txpool,net,engine \
  --ws \
  --ws.addr=0.0.0.0 \
  --http.port=8547 \
  --ws.port=8548 \
  --ws.origins="*" \
  --ws.api=debug,eth,txpool,net,engine \
  --syncmode=full \
  --gcmode=archive \
  --nodiscover \
  --maxpeers=0 \
  --port=30306 \
  --networkid=11155420 \
  --authrpc.vhosts="*" \
  --authrpc.addr=0.0.0.0 \
  --authrpc.port=8551 \
  --authrpc.jwtsecret=./jwt.txt \
  --rollup.disabletxpoolgossip=true

From Op-Node

./bin/op-node \
  --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=9545 \
  --p2p.disable \
  --rpc.enable-admin \
  --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY \
  --l1=$L1_RPC_URL \
  --l1.rpckind=$L1_RPC_KIND \
  --l1.beacon=$L1_BEACON_URL

Feedback

No response

[opfocus]

--http.api=web3,debug,eth,txpool,net,engine,miner
--ws.api=debug,eth,txpool,net,engine,miner \

[SZU-CEIE-student]

I‘ve met thes same problem,your method do help!!!