Development Requirements for Substrate-based OP-Rollup

[Acaishiba]

Project Name: Substrate OP-Rollup SDK Alpha Version Development Issue Type: Feature Request Detailed Description: We are outlining key development requirements for our Substrate-based OP-Rollup project, which are crucial for the next phase of our development:

• [ ] 1. Block Time: The system should ensure a block time of 1 second.
• [ ] 2. Epoch Duration: Each epoch should be 3600 seconds, equivalent to 3600 blocks.
• [ ] 3. Checkpoint Interval: Checkpoints need to be established at every 1 seconds or 1 blocks.
• [ ] 4. Sequencer Assignment: At the start of each epoch, sequencers responsible for each checkpoint should be predetermined.
• [ ] 5. Sequencer Election Algorithm: A specific algorithm for electing sequencers needs to be determined.
• [ ] 6. Sequencer Candidates: The candidates for the sequencer role should be current Validators.
• [ ] 7. Checkpoint Processing: Upon reaching a checkpoint, the respective Sequencer should execute the block Batch and submit it to Avail (DA Layer).
• [ ] 8. Challenge Period: Set the challenge period to 1 hour during testing phases.
• [ ] 9. Monitoring Module: A monitoring module is needed to ensure that Batches are accepted after the challenge period. If confirmed, the blocks associated with these Batches should be marked as finalized.

Expected Outcome: The focus of the development should be on implementing these features while ensuring the system's stability and efficiency. The process of electing sequencers and processing checkpoints efficiently is critical. Moreover, the monitoring module needs to be reliable and effective in maintaining the integrity of the finalized blocks.

[Acaishiba]

7. Checkpoint Processing: Upon reaching a checkpoint, the respective Sequencer should execute the block Batch and submit it to Avail (DA Layer).
   8. Challenge Period: Set the challenge period to 1 hour during testing phases. (According to the current setup of Avail, this feature request is temporarily halted. The arbitration of the dispute will be resolved in our chain)
   9. Monitoring Module: A monitoring module is needed to ensure that Batches are accepted after the challenge period. If confirmed, the blocks associated with these Batches should be marked as finalized.(According to the current setup of Avail, this feature request is temporarily halted. We just need to finalize block based on GRANDPA)

The new workflow is as follows:

1. Our chain generates blocks (BABE)
2. Elect a sequencer every epoch
3. The Sequencer sends transaction data, state_root and extrinsics_root of every block to Avail
4. Arbitrate disputes and finalize Blocks in our chain via GRANDPA.