Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(core): add levm to milestones #1176

Merged
merged 3 commits into from
Nov 21, 2024
Merged

docs(core): add levm to milestones #1176

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
38c1837
Add levm to milestones
jrchatruc Nov 14, 2024
341eb2e
Update milestones
jrchatruc Nov 21, 2024
9e7a1ef
Merge branch 'main' into add-levm-milestone
jrchatruc Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 30 additions & 15 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,13 +287,14 @@ At a high level, the following new parts are added to the node:
| 0 | Users can deposit Eth in the L1 (Ethereum) and receive the corresponding funds on the L2. | ✅ |
| 1 | The network supports basic L2 functionality, allowing users to deposit and withdraw funds to join and exit the network, while also interacting with the network as they do normally on the Ethereum network (deploying contracts, sending transactions, etc). | ✅ |
| 2 | The block execution is proven with a RISC-V zkVM and the proof is verified by the Verifier L1 contract. | 🏗️ |
| 3 | The network now commits to state diffs instead of the full state, lowering the commit transactions costs. These diffs are also submitted in compressed form, further reducing costs. It also supports EIP 4844 for L1 commit transactions, which means state diffs are sent as blob sidecars instead of calldata. | ❌ |
| 4 | The L2 supports native account abstraction following EIP 7702, allowing for custom transaction validation logic and paymaster flows. | ❌ |
| 5 | Support multiple L2s sharing the same bridge contract on L1 for seamless interoperability. | ❌ |
| 6 | 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. | ❌ |
| 7 | 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. | ❌ |
| 8 | 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. | ❌ |
| 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. | ❌ |
| 3 | The network now commits to state diffs instead of the full state, lowering the commit transactions costs. These diffs are also submitted in compressed form, further reducing costs. It also supports EIP 4844 for L1 commit transactions, which means state diffs are sent as blob sidecars instead of calldata. | 🏗️ |
| 4 | Use our own EVM implementation | 🏗️ |
| 5 | The L2 supports native account abstraction following EIP 7702, allowing for custom transaction validation logic and paymaster flows. | ❌ |
| 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. | ❌ |

### Milestone 0

Expand Down Expand Up @@ -345,13 +346,27 @@ It also supports EIP 4844 for L1 commit transactions, which means state diffs ar

| Task Description | Status |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ |
| The sequencer sends state diffs to the prover instead of full transaction data. | ❌ |
| The sequencer sends state diffs to the prover instead of full transaction data. | ✅ |
| On the prover, prove the state diffs compression | ❌ |
| On the `proposer`, send the state diffs through a blob in a EIP 4844 transaction. | ❌ |
| On the `proposer`, send the state diffs through a blob in a EIP 4844 transaction. | ✅ |
| Adapt the prover to prove a KZG commitment to the state diff and use the point evaluation precompile to show that the blob sent to the L1 is indeed the correct one through a proof of equivalence protocol | ❌ |
| Add a command to the CLI to reconstructing the full L2 state from all the blob data on the L1. | ❌ |

### Milestone 4: Account Abstraction
### Milestone 4: Own EVM Implementation

Finish our own EVM implementation (`levm`) to be able to add custom behaviour to the network (like account abstraction below).

#### Status

| Task Description | Status |
| ---------------------------------------------------- | ------ |
| Implement all opcodes | ✅ |
| Pass all execution (non-precompile) EF tests | 🏗️ |
| Implement all precompiles | 🏗️ |
| Pass all execution EF tests | 🏗️ |
| Full Ethereum Rust Integration (pass all Hive tests) | 🏗️ |

### Milestone 5: Account Abstraction

The L2 supports native account abstraction following EIP 7702, allowing for custom transaction validation logic and paymaster flows.

Expand All @@ -362,7 +377,7 @@ The L2 supports native account abstraction following EIP 7702, allowing for cust
| Add support for `SET_CODE_TX_TYPE` transactions (i.e. implement EIP 7702). | ❌ |
| Add examples of WebAuthn signing and paymaster flows using EIP 7702 | ❌ |

### Milestone 5: L2s interoperability
### Milestone 6: L2s interoperability

Support multiple L2s sharing the same bridge contract on L1 for seamless interoperability.

Expand All @@ -375,7 +390,7 @@ Support multiple L2s sharing the same bridge contract on L1 for seamless interop

TODO: Expand on tasks about proper interoperability between chains (seamlessly bridging between chains, etc).

### Milestone 6: Custom Native token
### Milestone 7: Custom Native token

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.

Expand All @@ -387,7 +402,7 @@ The L2 can also be deployed using a custom native token, meaning that a certain
| On the `commonBridge`, for custom native token deposits, `msg.value` should always be zero, and the amount of the native token to mint should be a new `valueToMintOnL2` argument. The amount should be deducted from the caller thorugh a `transferFrom`. | ❌ |
| On the CLI, add support for custom native token deposits and withdrawals | ❌ |

### Milestone 7: Security (TEEs and Multi Prover support)
### Milestone 8: Security (TEEs and Multi Prover support)

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.

Expand All @@ -399,7 +414,7 @@ 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 8: Based Contestable Rollup
### Milestone 9: 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.

Expand All @@ -411,7 +426,7 @@ The network can be run as a Based Rollup, meaning sequencing is done by the Ethe

TODO: Expand on this.

### Milestone 9: Validium
### 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.

Expand Down
Loading