Fault Proof support for hybrid DA

[qizhou]

Currently, we do not support fault-proof

• some parameters (e.g., enablel2blob) are passed via CLI, which should be in the rollup config
• some parameters should be moved out of rollup config (e.g., DAC lists)

sub issues:

• move enablel2blob away from CLI #56
• make DAC lists out of rollup config #57
• implement BLOB DA #58

[blockchaindevsh]

I think to enable BLOB challenge, we need to insert a BLOB challenge module into the pipeline, similar to how AltDA works now:

1. This module M should be inserted after BatchQueue module.
2. M needs to parse the Batch and record all BLOBs and corresponding L1 Origin block.
3. M needs to record all BLOB challenges within BLOB challenge window.
4. If M detects expired challenge for some BLOBs, it should record it and then trigger a reorg, and finally when deriving the batch a second time, it should exclude those BLOB txs from the batch.
   1. M needs to fix up parent hash of subsequent batches.(can reference how steady batch derivation works)

Question:
If both AltDA challenge and BLOB challenge are enabled, what's the expected relationship between AltDA window and BLOB window? My intuition is the effective window should be max(AltDA window, BLOB window).

[qizhou]

Question: If both AltDA challenge and BLOB challenge are enabled, what's the expected relationship between AltDA window and BLOB window? My intuition is the effective window should be max(AltDA window, BLOB window).

I think we can just reuse the same parameters (challengeWindow, resolveWindow) for both of them.

[qizhou]

We need specific sub-issues and assignees for the subtask.

[blockchaindevsh]

We need specific sub-issues and assignees for the subtask.

Updated .