Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Commit a32996b

Browse files
committed
update sequencing
1 parent 9f6692a commit a32996b

1 file changed

Lines changed: 26 additions & 4 deletions

File tree

learn/sequencing/single.md

Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,16 @@ A single sequencer is the simplest sequencing architecture for a Rollkit-based r
55
## How the Single Sequencer Model Works
66

77
1. **Transaction Submission:**
8-
- Users submit transactions directly to the sequencer node via RPC or other interfaces.
9-
2. **Transaction Ordering:**
10-
- The sequencer collects transactions from users and orders them into blocks according to the rollup's rules.
8+
- Users submit transactions to the execution environment via RPC or other interfaces.
9+
2. **Transaction Collection and Ordering:**
10+
- The execution environment collects incoming transactions.
11+
- The sequencer requests a batch of transactions from the execution environment to be included in the next block.
1112
3. **Block Production:**
12-
- The sequencer produces new blocks at regular intervals or when enough transactions are collected.
13+
- **Without lazy mode:** the sequencer produces new blocks at fixed intervals.
14+
- **With lazy mode:** the sequencer produces a block once either
15+
- enough transactions are collected
16+
- the lazy-mode block interval elapses
17+
More info [here](/learn/config#lazy-mode).
1318
- Each block contains a batch of ordered transactions and metadata.
1419

1520
4. **Data Availability Posting:**
@@ -19,6 +24,23 @@ A single sequencer is the simplest sequencing architecture for a Rollkit-based r
1924
5. **State Update:**
2025
- The sequencer updates the rollup state based on the new block and makes the updated state available to light clients and full nodes.
2126

27+
## Transaction Flow Diagram
28+
29+
```mermaid
30+
sequenceDiagram
31+
participant User
32+
participant ExecutionEnv as Execution Environment
33+
participant Sequencer
34+
participant DA as Data Availability Layer
35+
36+
User->>ExecutionEnv: Submit transaction
37+
Sequencer->>ExecutionEnv: Request batch for block
38+
ExecutionEnv->>Sequencer: Provide batch of transactions
39+
Sequencer->>DA: Post block data
40+
Sequencer->>ExecutionEnv: Update state
41+
ExecutionEnv->>User: State/query response
42+
```
43+
2244
## Advantages
2345

2446
- **Simplicity:** Easy to set up and operate, making it ideal for development, testing, and small-scale deployments.

0 commit comments

Comments
 (0)