From 7ef91ea4cdeb5b5c37d792616759f9f6f5f4645a Mon Sep 17 00:00:00 2001 From: Ivan Litteri <67517699+ilitteri@users.noreply.github.com> Date: Thu, 2 Jan 2025 17:02:46 -0300 Subject: [PATCH] chore(docs): update README.md (#1599) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a5d0da7326..cddfaf5676 100644 --- a/README.md +++ b/README.md @@ -312,7 +312,7 @@ At a high level, the following new parts are added to the node: | 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 | Use our own EVM implementation | 🏗️ | -| 5 | The L2 supports native account abstraction following EIP 7702, allowing for custom transaction validation logic and paymaster flows. | ❌ | +| 5 | The L2 supports native account abstraction following [EIP 7701](https://eips.ethereum.org/EIPS/eip-7701) and [EIP 7702](https://eips.ethereum.org/EIPS/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. | ❌ | @@ -391,7 +391,7 @@ Finish our own EVM implementation (`levm`) to be able to add custom behaviour to ### Milestone 5: Account Abstraction -The L2 supports native account abstraction following EIP 7702, allowing for custom transaction validation logic and paymaster flows. +The L2 supports native account abstraction following EIPs [7701](https://eips.ethereum.org/EIPS/eip-7701) and [7702](https://eips.ethereum.org/EIPS/eip-7702), allowing for custom transaction validation logic and paymaster flows. #### Status