Rollup-boost occasionally fails to accept flashblock payloads #448
Description
Issue
Seems like rollup-boost occasionally fails to accept a new payload, on the scenario where payload resolution was triggered on the CL. However, since flashblocks have already been broadcasted to the websocket to flashblock subscribers, these FB payloads wont actually be accepted in the full payload and will become invalid.
Is there a better way to increase the reliability of transaction pre-confirmations? Will this be to tune up the leeway-time configuration on the op-rbuilders?
2025-11-28T02:03:36.908246Z INFO proxy::call: proxying request to rollup-boost server method="engine_getPayloadV4" 2025-11-28T02:03:36.908277Z INFO get_payload_v4{otel.kind=Server payload_id=0x0352124bdb43fcc2}: rollup_boost::server: received get_payload_v4 2025-11-28T02:03:36.908286Z INFO get_payload_v4{otel.kind=Server payload_id=0x0352124bdb43fcc2}:get_payload_v4{otel.kind=Client target="l2" url=http://op-reth-seq:8552/ payload_id=0x0352124bdb43fcc2}: rollup_boost::client::rpc: Sending get_payload_v4 to l2 2025-11-28T02:03:36.908314Z INFO get_payload_v4{otel.kind=Server payload_id=0x0352124bdb43fcc2}: rollup_boost::server: builder has payload, calling get_payload on builder 2025-11-28T02:03:36.908332Z INFO get_payload_v4{otel.kind=Server payload_id=0x0352124bdb43fcc2}: rollup_boost::flashblocks::service: Returning fb payload 2025-11-28T02:03:36.908343Z INFO get_payload_v4{otel.kind=Server payload_id=0x0352124bdb43fcc2}:fork_choice_updated_v3{otel.kind=Client target="l2" head_block_hash=0xc95b1b2665a1aa7b3e4e5662a60d6b090706156c12ae47921c82790f2b279cb3 url=http://op-reth-seq:8552/}: rollup_boost::client::rpc: Sending fork_choice_updated_v3 to l2 2025-11-28T02:03:36.908401Z ERROR rollup_boost::flashblocks::service: Failed to extend payload error=Invalid index for flashblock payload_id=0x0352124bdb43fcc2 index=1