Skip to content

Commit 4285de0

Browse files
0xValerazkzoomer
andauthored
Update docs/src/specs/upgrade_history/v27_evm_emulation/v27_evm_emulation.md
Co-authored-by: zkzoomer <[email protected]>
1 parent 349abc4 commit 4285de0

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/src/specs/upgrade_history/v27_evm_emulation/v27_evm_emulation.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,7 @@
55
The V27 upgrade happened after the gateway preparation upgrade, but before the gateway was deployed. As such the upgrade
66
process did not involve the Gateway parts (upgrading the CTM on GW, etc), it was an L1-only upgrade.
77

8-
Additionally this was not a bridge upgrade, as the bridge and ecosystem contracts didn't have new features, so L1<>L2
9-
bridging was not affected. This meant that only the system components, the Verifiers, Facets and L2 contracts needed to
10-
be upgraded.
8+
Additionally this was not a bridge upgrade, as the bridge and ecosystem contracts didn't have new features, so L1<>L2 bridging was not affected. This meant that only the system components, the Verifiers, Facets and L2 contracts needed to be upgraded.
119

1210
The upgrade process was as follows:
1311

0 commit comments

Comments
 (0)