Skip to content

Commit 293ecd9

Browse files
updating some diagrams
1 parent 8daa407 commit 293ecd9

File tree

6 files changed

+11
-9
lines changed

6 files changed

+11
-9
lines changed
355 KB
Loading
652 KB
Loading
-258 KB
Binary file not shown.
-5.88 KB
Loading

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/bridging-class-diagram.png)
1+
The class diagram below describes how the exit root contracts communicate with the bridge and the rollup manager.
2+
3+
![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/exit-root-class-diagram.png)
24

35
An exit tree is a binary, append-only, sparse Merkle tree (SMT) whose leaf nodes store bridging data. The exit trees have a depth of 32.
46

docs/zkEVM/architecture/high-level/smart-contracts/overview.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,6 @@
22
comments: true
33
---
44

5-
The skeleton-class diagram below reveals the smart contract architecture of rollup and CDK stacks.
6-
7-
![Polygon Solidity smart contract architecture full view](../../../../img/cdk/high-level-architecture/overview-class-diagram.png)
8-
95
## Polygon smart contract architecture
106

117
Chain stacks at the node level direct transaction data to the L2 and L1 networks via smart contract calls. The system stores state in binary tree structures containing verifiable local and global exit roots.
@@ -14,10 +10,6 @@ The diagram below details the Polygon Solidity smart contract architecture minus
1410

1511
![Polygon Solidity smart contract architecture](../../../../img/cdk/high-level-architecture/smart-contracts-full-view.png)
1612

17-
And here is the class diagram for the unified bridge and exit roots activity.
18-
19-
![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/bridging-class-diagram.png)
20-
2113
There are four key contract types built into the system design:
2214

2315
- The [consensus contract set](#consensus-contracts).
@@ -45,6 +37,10 @@ The [PolygonRollupManager.sol](https://github.com/0xPolygonHermez/zkevm-contract
4537

4638
## Bridge
4739

40+
The class diagram below describes the unified bridge interactions.
41+
42+
![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/bridging-class-diagram.png)
43+
4844
The unified bridge contract [PolygonZkEVMBridgeV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMBridgeV2.sol) is responsible for bridging and claiming activity across L1 and L2 chains.
4945

5046
<center>
@@ -55,6 +51,10 @@ In the L1 network, the bridge also manages the complex exit root mechanism gover
5551

5652
## Global exit roots
5753

54+
The class diagram below describes the exit root interactions.
55+
56+
![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/exit-root-class-diagram.png)
57+
5858
System state as a whole is stored on binary trees with data and/or exit roots written into their leaves.
5959

6060
Local updates at the leaf-level trigger exit root updates at the top of the trees which are then available to the global exit root trees and the consensus contracts via the L1 bridge contract.

0 commit comments

Comments
 (0)