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/zkEVM/architecture/protocol/etrog-upgrade.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
@@ -65,7 +65,7 @@ The crucial alterations made in the Etrog upgrade are therefore on; the _one blo
65
65
66
66
67
67
68
-
## Blocks in the Etrog upgrade
68
+
## Etrog Blocks
69
69
70
70
Up until the dragonfruit upgrade, each L2 block contains a single transaction. The same approach taken by Optimism.
71
71
@@ -81,7 +81,7 @@ The below figure displays blocks of the Etrog upgrade vis-à-vis those of the Dr
81
81
82
82
83
83
84
-
## Timestamps in Etrog upgrade
84
+
## Etrog Timestamps
85
85
86
86
In order to circumvent the above-mentioned issue related to the _one timestamp for many blocks_ problem, each block in the Etrog upgrade's batch receives its own unique timestamp. This is in addition to allowing more than one transaction per block.
0 commit comments