From 8728d419c8acfef29f25de810e0a7b6944abda9f Mon Sep 17 00:00:00 2001 From: Ivan Litteri <67517699+ilitteri@users.noreply.github.com> Date: Wed, 27 Nov 2024 14:38:41 -0300 Subject: [PATCH] chore(l2): prioritize Validium over Based Rollup (#1298) --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 98cc63a3f..688efdf0b 100644 --- a/README.md +++ b/README.md @@ -295,8 +295,8 @@ At a high level, the following new parts are added to the node: | 6 | Support multiple L2s sharing the same bridge contract on L1 for seamless interoperability. | ❌ | | 7 | The L2 can also be deployed using a custom native token, meaning that a certain ERC20 can be the common currency that's used for paying network fees. | ❌ | | 8 | The L2 has added security mechanisms in place, running on Trusted Execution Environments and Multi Prover setup where multiple guarantees (Execution on TEEs, zkVMs/proving systems) are required for settlement on the L1. This better protects against possible security bugs on implementations. | ❌ | -| 9 | The network can be run as a Based Rollup, meaning sequencing is done by the Ethereum Validator set; transactions are sent to a private mempool and L1 Validators that opt into the L2 sequencing propose blocks for the L2 on every L1 block. | ❌ | -| 10 | The L2 can be initialized in Validium Mode, meaning the Data Availability layer is no longer the L1, but rather a DA layer of the user's choice. | ❌ | +| 9 | The L2 can be initialized in Validium Mode, meaning the Data Availability layer is no longer the L1, but rather a DA layer of the user's choice. | ❌ | +| 10 | The network can be run as a Based Rollup, meaning sequencing is done by the Ethereum Validator set; transactions are sent to a private mempool and L1 Validators that opt into the L2 sequencing propose blocks for the L2 on every L1 block. | ❌ | ### Milestone 0 @@ -416,7 +416,11 @@ The L2 has added security mechanisms in place, running on Trusted Execution Envi | Support verifying multiple different zkVM executions on the `onChainProposer` L1 contract. | ❌ | | Support running the operator on a TEE environment | ❌ | -### Milestone 9: Based Contestable Rollup +### Milestone 9: Validium + +The L2 can be initialized in Validium Mode, meaning the Data Availability layer is no longer the L1, but rather a DA layer of the user's choice. + +### Milestone 10: Based Contestable Rollup The network can be run as a Based Rollup, meaning sequencing is done by the Ethereum Validator set; transactions are sent to a private mempool and L1 Validators that opt into the L2 sequencing propose blocks for the L2 on every L1 block. @@ -428,10 +432,6 @@ The network can be run as a Based Rollup, meaning sequencing is done by the Ethe TODO: Expand on this. -### Milestone 10: Validium - -The L2 can be initialized in Validium Mode, meaning the Data Availability layer is no longer the L1, but rather a DA layer of the user's choice. - #### Status | Task Description | Status |