mains sequencing structure

Author: kmurphypolygon

docs/img/cdk/high-level-architecture/smart-contracts-full-view.png

@@ -41,5 +41,5 @@ When complete, this section will include information on:
 
 ### Currently out of scope
 
-- The bridge service.
+- The in-development bridge service.
 - AggLayer.

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

@@ -0,0 +1 @@
+How bridging works: Bridge contracts -> keeping things in sync between chains L1 L2, sequencer, state db, local/global exit roots

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

@@ -0,0 +1,26 @@
+Transactions flowing through the system reach the smart contract environment after one of two contract call use cases; sequencing or verifying batches.
+
+This section of the docs takes a closer look at the sequencing workflow.
+
+## `sequenceBatches(...)`
+
+The rollup sequencer component calls the [`sequenceBatches`](https://github.com/0xPolygonHermez/zkevm-contracts/blob/1ad7089d04910c319a257ff4f3674ffd6fc6e64e/contracts/v2/lib/PolygonRollupBaseEtrog.sol#L425) function on the [`PolygonZkEVMEtrog.sol`](https://github.com/0xPolygonHermez/zkevm-contracts/blob/1ad7089d04910c319a257ff4f3674ffd6fc6e64e/contracts/v2/consensus/zkEVM/PolygonZkEVMEtrog.sol) contract which inherits the function from [PolygonRollupBaseEtrog](https://github.com/0xPolygonHermez/zkevm-contracts/blob/1ad7089d04910c319a257ff4f3674ffd6fc6e64e/contracts/v2/lib/PolygonRollupBaseEtrog.sol).
+
+The function takes an array of `BatchData` structs containing transactions. 
+
+```solidity
+struct BatchData {
+    bytes transactions;
+    bytes32 forcedGlobalExitRoot;
+    uint64 forcedTimestamp;
+    bytes32 forcedBlockHashL1;
+}
+```
+
+The function checks them, organizes them, and appends them to the sequence correctly, eventually emitting a `SequenceBatch` event which sends a newly sequenced batch of transactions to the `PolygonRollupManager.sol` contract via the `onSequenceBatches(...)` function.
+
+### `onSequenceBatches(...)`
+
+This function takes the sequenced batches and adds them to the correct stack and updates the batch count.
+
+## `sequenceBatchesValidium(...)`

…level/smart-contracts/exit-root-trees.md …ecture/high-level/smart-contracts/api.mddocs/zkEVM/architecture/high-level/smart-contracts/exit-root-trees.md renamed to docs/zkEVM/architecture/high-level/smart-contracts/api.md docs/zkEVM/architecture/high-level/smart-contracts/exit-root-trees.md renamed to docs/zkEVM/architecture/high-level/smart-contracts/api.md

@@ -0,0 +1,37 @@
+## `PolygonRollupManager.sol`
+
+The [PolygonRollupManager.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonRollupManager.sol) contract is responsible for managing rollups and verifying batches. It creates and updates rollup stacks by storing hash-sequenced data as newly sequenced batches arrive.
+
+It is responsible for the verification workflow by supplying updated exit root data to the [[PolygonZkEVMGlobalExitRootV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMGlobalExitRootV2.sol)](#polygonzkevmglobalexitrootv2sol) contract.
+
+### Key functionality
+
+- Defining and adding rollup types which contains consensus implementation details and compatibility checks.
+- Defining the [`RollupData`](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonRollupManager.sol#L70s) struct.
+- Initializes the trusted aggregator process for verifying multiple batches.
+- Gets exit root data by computing all local exit roots of all rollups.
+- Calculates batch rewards.
+
+## `PolygonZkEVMBridgeV2.sol`
+
+The [PolygonZkEVMBridgeV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMBridgeV2.sol) is the main communication mechanism between the L1 and L2 realms. It manages bridging and claiming of assets and messages across environments.
+
+### Key functionality
+
+- Bridging assets with the `bridgeAsset(...)` function.
+- Bridging messages with a choice of `bridgeMessage(...)` functions for various scenarios.
+- Claiming assets with the `claimAsset(..)` function.
+- Claiming messages with the `claimMessage(...)` function.
+- Verifying state and updating the global exit root with state changes.
+- Providing access to the global exit root manager via the `IBasePolygonZkEVMGlobalExitRoot`.
+- Interacting with the `PolygonZkEVMGlobalExitRootL2.sol` contract which exists in the L2 space as part of the bridge functionality.
+
+## `PolygonZkEVMGlobalExitRootV2.sol`
+
+The [PolygonZkEVMGlobalExitRootV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMGlobalExitRootV2.sol) contract manages the L1 info tree that represents the current state of the system by updating global exit roots on state changes. It does this task across multiple networks and layers.
+
+### Key functionality
+
+- Updating the L1 info tree by emitting the `UpdateL1InfoTree(...)` event.
+- Updating exit roots.
+- Retrieving latest exit roots and leaf values.

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

@@ -1,2 +1,21 @@
-!!! warning
-    Coming soon.
+<!-- https://excalidraw.com/#json=JKZp9QEihifF_B7Z41Dfv,FVNhqQKi9PA1jM0kzUoCsQ" -->
+
+## Polygon smart contract architecture
+
+The diagram below shows the Polygon smart contract architecture and how the consensus mechanism works through sequencing and verification activity.
+
+The stacks direct transaction data into the L2 and L1 realms via Solidity smart contract calls, which then record the system state in binary tree structures that store local and global exit roots of the system.
+
+### Smart contracts topology
+
+![Polygon Solidity smart contract architecture](../../../../img/cdk/high-level-architecture/smart-contracts-full-view.png)
+
+### Rollup contracts
+
+The main contracts for the zkEVM rollup stack are [PolygonRollupManager.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonRollupManager.sol) which is responsible for managing rollup and validium batches; the bridge contract [PolygonZkEVMBridgeV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMBridgeV2.sol) which is responsible for bridging and claiming activity across L1 and L2 chains; and the [PolygonZkEVMGlobalExitRootV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMGlobalExitRootV2.sol) contract which manages the exit roots across multiple networks at the Ethereum L1 level.
+
+### Valdium contracts 
+
+The CDK validium stacks use the [cdk-validium-contracts](https://github.com/0xPolygon/cdk-validium-contracts/tree/main) which has slightly adjusted behavior to take account of validium components, such as in the [PolygonZkEVMGlobalExitRootL2.sol](https://github.com/0xPolygon/cdk-validium-contracts/blob/main/contracts/PolygonZkEVMGlobalExitRootL2.sol) contract for example. 
+
+The CDK repo is a fork of the zkEVM main contracts repo and all contracts, therefore, extend from common interfaces.