Skip to content

Commit

Permalink
Merge pull request #156 from 0xPolygon/0xgraciegrace-patch-1
Browse files Browse the repository at this point in the history
Update lxly-bridge.md
  • Loading branch information
EmpieichO authored Jan 16, 2024
2 parents 3e19c44 + 3455231 commit a8d3e4c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
Binary file added docs/img/zkEVM/lxly-bridge-diagram.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 4 additions & 4 deletions docs/zkEVM/architecture/protocol/lxly-bridge.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Once sequenced batches have been verified, the _Global Exit Tree_ gets updated,

The Rollup Manager manages the following lists of availability;

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

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

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

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

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

## Conclusion

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

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

Expand Down

0 comments on commit a8d3e4c

Please sign in to comment.