[Question] When a new chain's op-batcher run in flag of `--data-availability-type=callData` , Is there have some potential problems?

If my op-batcher set the flag of `--data-availability-type=callData ` , that means the op-batcher does not put the batch data into the blob, but put in the callData. It no need to configure the L1 beacon in the op-node and op-challenger. Is there have some potential problems , about op-node and op-challenger?

Start by tracing the --data-availability-type=callData configuration across op-batcher, op-node, and op-challenger, then review the relevant data-availability documentation and configuration checks. Done means documenting whether beacon configuration is required for each component and identifying any limitations or compatibility concerns.

Written by the indexing model from the issue text.