From 823221b4b11312a262477562aeb8220fb8b6c36d Mon Sep 17 00:00:00 2001 From: Luca Donno <30298476+lucadonnoh@users.noreply.github.com> Date: Tue, 7 May 2024 15:51:26 +0200 Subject: [PATCH 1/2] Remove duplicated section on "prove anything" in main aggregator tex The section was duplicated. I felt like the first version reads better so I kept that one --- .../architecture/aggregator/sections/main-aggregator.tex | 1 - 1 file changed, 1 deletion(-) diff --git a/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex b/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex index a967cfe..3ad25e4 100644 --- a/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex +++ b/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex @@ -71,7 +71,6 @@ \section{``Prove Anything'' Paradigm} The \textit{prove anything} approach allows us to implement an anti-censorship measure called \textbf{forced batches}. Using these approach, an user can take the role of a sequencer for getting its L2 transactions into the virtual state in case the trusted sequencer is not doing so. The main use case is to allow a user to send bridge transactions in order to withdraw assets from L2 without the risk of censorship (which will make it impossible to withdraw the funds). Since it is an (untrusted) user who is sending the L2 batch data, we must be sure that we can prove anything that the user sends. The forced batches mechanism will be explained later on (when describing the different security measures implemented in the zkEVM). -The ``prove anything'' method enables the implementation of an anti-censorship measure known as \textbf{forced batches}. By using this method, A user may operate as a sequencer by shifting its L2 transactions to the virtual state in case the trusted sequencer don't sequence it. The main goal is to allow a user to submit bridge transactions to withdraw assets from L2 without the risk of being censored by the trusted sequencer, thereby preventing the withdrawal of user funds from the network. Take into account that we must authenticate all information provided by the untrusted actor sending the L2 batch data. The forced batches technique will be explained in the part that covers the security mechanisms incorporated into the zkEVM. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From e839329a52b8168ed99eef028f9f4f95fd6241cd Mon Sep 17 00:00:00 2001 From: Luca Donno <30298476+lucadonnoh@users.noreply.github.com> Date: Tue, 7 May 2024 15:53:18 +0200 Subject: [PATCH 2/2] fix small typo --- .../architecture/aggregator/sections/main-aggregator.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex b/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex index 3ad25e4..7b3830a 100644 --- a/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex +++ b/knowledge-layer/architecture/aggregator/sections/main-aggregator.tex @@ -69,7 +69,7 @@ \section{``Prove Anything'' Paradigm} Figure \ref{fig:invalid-batch} shows that when a batch processing fails, the state remains unchanged $S_{i+1}=S_i$ and a proof of this lack of state change is produced. This occurrence should be infrequent yet it is possible. -The \textit{prove anything} approach allows us to implement an anti-censorship measure called \textbf{forced batches}. Using these approach, an user can take the role of a sequencer for getting its L2 transactions into the virtual state in case the trusted sequencer is not doing so. The main use case is to allow a user to send bridge transactions in order to withdraw assets from L2 without the risk of censorship (which will make it impossible to withdraw the funds). Since it is an (untrusted) user who is sending the L2 batch data, we must be sure that we can prove anything that the user sends. The forced batches mechanism will be explained later on (when describing the different security measures implemented in the zkEVM). +The \textit{prove anything} approach allows us to implement an anti-censorship measure called \textbf{forced batches}. Using these approach, a user can take the role of a sequencer for getting its L2 transactions into the virtual state in case the trusted sequencer is not doing so. The main use case is to allow a user to send bridge transactions in order to withdraw assets from L2 without the risk of censorship (which will make it impossible to withdraw the funds). Since it is an (untrusted) user who is sending the L2 batch data, we must be sure that we can prove anything that the user sends. The forced batches mechanism will be explained later on (when describing the different security measures implemented in the zkEVM).