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/cdk/architecture/high-level-views.md
+14-21Lines changed: 14 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,23 +25,21 @@ The following diagram is a sequential depiction of the user data flow for the CD
25
25
#### Sequential interactions
26
26
27
27
1. User sends a transaction to the CDK Erigon RPC node.
28
-
2. The Erigon RPC node proxies the data to the CDK Erigon sequencer node.
28
+
2. The CDK Erigon RPC node proxies the data to the CDK Erigon sequencer node and syncs the batch data between the sequencer and the RPC nodes.
29
29
3. The sequencer sequences the transaction batches.
30
-
4. The sequencer puts the batches into the data streamer component.
31
-
5. The data streamer component streams the data into the sequence sender. It streams data into the aggregator and AggLayer for rollup and validium mode stacks.
32
-
6. In validium mode, the sequencer sender persists transaction data into the DAC nodes.
33
-
7. In both modes, the sequencer sender sequences the batches into the L1 smart contracts.
34
-
8. In both modes, the aggregator sends the batches to the prover and the prover returns the proofs.
35
-
9. The aggregator batches the proofs.
36
-
10. The aggregator submits the final proof to the AggLayer.
37
-
11. The AggLayer submits the final proof to the L1 smart contract domain.
30
+
4. The sequencer sender reads batches from the RPC node.
31
+
5. In validium mode only, the sequencer sender persists transaction data into the DAC nodes.
32
+
6. The sequencer sender sequences the batches into the L1 smart contracts.
33
+
7. The aggregator reads batches from the sequencer data stream.
34
+
8. The aggregator sends batches to the provers.
35
+
9. The aggregator submits the final proof to the AggLayer.
36
+
10. The AggLayer submits the final proof to the L1 smart contract domain.
38
37
39
38
```mermaid
40
39
sequenceDiagram
41
40
participant User
42
41
participant ErigonRPC as CDK Erigon RPC Node
43
42
participant Sequencer as CDK Erigon Sequencer Node
44
-
participant DataStreamer as Data Streamer
45
43
participant SeqSender as Sequence Sender
46
44
participant Aggregator
47
45
participant AggLayer
@@ -50,18 +48,13 @@ sequenceDiagram
50
48
participant L1 as L1 Smart Contracts
51
49
52
50
User->>ErigonRPC: Send transaction
53
-
ErigonRPC->>Sequencer: Proxy transaction data
51
+
ErigonRPC->>Sequencer: Proxy and sync transaction data
0 commit comments