Skip to content

Commit ac5de4e

Browse files
making pics viewable
1 parent 44e5969 commit ac5de4e

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/zkEVM/architecture/high-level/smart-contracts/exit-roots.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ The global exit tree root of the L1 info tree is, therefore, the source of truth
1111
The L2 bridge contract manages a special Merkle tree called a local exit tree for each network that participates in bridging and claiming which is updated by the [PolygonZkEVMGlobalExitRootL2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/feature/etrog/contracts/PolygonZkEVMGlobalExitRootL2.sol) contract.
1212

1313
<center>
14+
1415
![Local exit tree for network participant](../../../../img/cdk/high-level-architecture/local-exit-tree.png)
16+
1517
</center>
1618

1719
Data from `bridgeAsset()` and `bridgeMessage()` calls on the bridge is stored in leaf nodes on the local exit trees.
@@ -28,7 +30,9 @@ Data from `bridgeAsset()` and `bridgeMessage()` calls on the bridge is stored in
2830
The roots of the L2 local exit trees feed into a single exit tree that manages state from all participating L2 rollups.
2931

3032
<center>
33+
3134
![Exit tree for rollups](../../../../img/cdk/high-level-architecture/exit-tree-for-rollups.png)
35+
3236
</center>
3337

3438
The L2 local exit root is accessible on the rollup manager by calling the [`getRollupExitRoot()`](https://github.com/0xPolygonHermez/zkevm-contracts/blob/b2a62e6af5738366e7494e8312184b1d6fdf287c/contracts/v2/PolygonRollupManager.sol#L1620) method.
@@ -38,7 +42,9 @@ The L2 local exit root is accessible on the rollup manager by calling the [`getR
3842
Every time there is a call to `bridgeAsset()` and `bridgeMessage()` on the bridge at the L1 Ethereum level, the data is stored in a leaf node on the L1 local exit tree.
3943

4044
<center>
45+
4146
![L1 local exit tree](../../../../img/cdk/high-level-architecture/l1-ethereum-exit-tree.png)
47+
4248
</center>
4349

4450
## L1 info tree
@@ -50,7 +56,9 @@ All subtrees exit roots feed into the leaves of the L1 info tree, which contains
5056
The GER is the fingerprint of the information stored in all trees, and thus represents the true state of the system.
5157

5258
<center>
59+
5360
![Exit tree for rollups](../../../../img/cdk/high-level-architecture/l1-info-tree.png)
61+
5462
</center>
5563

5664
## Exit leaves

0 commit comments

Comments
 (0)