I’m exploring ways to reduce the finality time for optimistic rollups on Ethereum. My idea builds upon the `Check-In model`, which has some known cost-related issues when requiring every validator to check in. I propose the following revised approach and would appreciate feedback on its feasibility, potential problems, and any overlooked attack vectors.

  1. Validator Selection: In each epoch, a set of validators is chosen to be responsible for submitting check-ins for rollup batches.
  2. Quorum-Based Validation: If a quorum of the chosen validators submits check-ins without fraud proof, the rollup batch is marked as valid. If any one validator within the quorum submits a fraud proof, the system will handle the fraud proof accordingly.
  3. Concurrent Processing in Execution Client: To efficiently validate rollup batches, I propose introducing a separate queue and concurrent thread handling mechanism in the execution client. This would allow for the validation of multiple rollup batches concurrently (up to X threads for X batches), minimizing the impact on the main execution process.

Questions

  • Would this model be effective in reducing the finality time for rollups?
  • What are the potential issues, such as cost, security, or operational concerns?
  • Could this approach introduce new attack vectors, such as validators withholding check-ins or spamming fraud proofs to disrupt the network?

Any insights or suggestions for improvement would be greatly appreciated.

submitted by /u/DebRC99
[link] [comments]

This post was originally published on this site