You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/learn/agglayer.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ Here's what happens in the AggLayer when users interact with individual Polygon
82
82
83
83
7. Optionally, the aggregated proof can also guarantee that a list of updated state roots $S_i$ is valid.
84
84
85
-
After producing the aggregated proof $\pi_{\text{final}}'$, the AggLayer posts that proof to Ethereum, along with a commitment to the message lists $M_i$.
85
+
After producing the aggregated proof $\pi_{\text{final}}'$, the AggLayer posts that proof to Ethereum, along with a commitment to the message lists $\{M_i\}$.
86
86
87
87
The above procedure is depicted in the simplified diagram below.
88
88
@@ -95,7 +95,7 @@ The above procedure is depicted in the simplified diagram below.
95
95
96
96
There's a subtle detail about validiums that needs to be noted.
97
97
98
-
For all rollup chains, we have all data necessary to retrieve the proof of inclusion for a particular message in some list $M_i$.
98
+
For all rollup chains, we have all data necessary to retrieve the proof of inclusion for a particular message in some list $\{M_i\}$.
99
99
100
100
But this is not so with validium chains. For instance, there could be a 'data withholding' attack.
0 commit comments