Skip to content

Commit a8d3e4c

Browse files
authored
Merge pull request 0xPolygon#156 from 0xPolygon/0xgraciegrace-patch-1
Update lxly-bridge.md
2 parents 3e19c44 + 3455231 commit a8d3e4c

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed
207 KB
Loading

docs/zkEVM/architecture/protocol/lxly-bridge.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Once sequenced batches have been verified, the _Global Exit Tree_ gets updated,
8282

8383
The Rollup Manager manages the following lists of availability;
8484

85-
- Rollup consensus mechanisms. The list may consists of Consensus contracts such as PolygonZkEVM.sol or zkValidium.sol.
85+
- Rollup consensus mechanisms. The list may consist of Consensus contracts such as PolygonZkEVM.sol or zkValidium.sol.
8686
- Verifier contracts. For example, the PolygonZkEVM.sol uses the _Verifier.sol_ SC for verification of batches.
8787

8888
Governance SC oversees Consensus mechanisms and Verifiers that can be added to the respective lists.
@@ -104,7 +104,7 @@ The [Rollup Manager SC](https://github.com/0xPolygonHermez/zkevm-contracts/blob/
104104

105105
- The developer selects the Consensus and Verifier for the required rollup amongst those available in the Rollup Manager's lists,
106106
- Requests creation of a rollup with the selected specifications,
107-
- Governance SC invokes the Rollup Manager's `AddNewRollupType()` function,
107+
- Governance SC invokes the Rollup Manager's `addNewRollupType()` function,
108108
- Once, a rollup is created, the transfer of assets can be processed in the usual manner.
109109

110110
### Overall flow of events
@@ -118,11 +118,11 @@ The below diagram captures the following flow of events, most of which are handl
118118
- Verification of batches,
119119
- Updating the Global Exit Root.
120120

121-
![Figure 3: Events flow related to RollupManager.sol](../../../img/zkEVM/lxly-3-flow-rollupmanager.png)
121+
![Figure 3: Events flow related to RollupManager.sol](../../../img/zkEVM/lxly-bridge-diagram.png)
122122

123123
## Conclusion
124124

125-
Although the LXLY Bridge is still a work in progress, it is designed to be Polygon's talisman for accomplishing multi-chain interoperability.
125+
Although the LXLY Bridge is still in development, it is a central component to Polygon's aggregaton layer which offers multi-chain interoperability.
126126

127127
The LXLY Bridge currently works with the Polygon zkEVM as the L2 and the Ethereum network as L1.
128128

0 commit comments

Comments
 (0)