You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/zkEVM/architecture/high-level/smart-contracts/overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,6 @@
2
2
comments: true
3
3
---
4
4
5
-
The skeleton-class diagram below reveals the smart contract architecture of rollup and CDK stacks.
6
-
7
-

8
-
9
5
## Polygon smart contract architecture
10
6
11
7
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
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.
49
45
50
46
<center>
@@ -55,6 +51,10 @@ In the L1 network, the bridge also manages the complex exit root mechanism gover
55
51
56
52
## Global exit roots
57
53
54
+
The class diagram below describes the exit root interactions.
System state as a whole is stored on binary trees with data and/or exit roots written into their leaves.
59
59
60
60
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