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

Commit 1527dfb

Browse files
committed
updated sequencing docs
1 parent 9fe5df4 commit 1527dfb

3 files changed

Lines changed: 1 addition & 17 deletions

File tree

learn/sequencing/forced-inclusion.md

Lines changed: 0 additions & 3 deletions
This file was deleted.

learn/sequencing/overview.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,6 @@ It mainly consists of:
2323
## Sequencing Implementations {#sequencing-implementations}
2424

2525
An implementation of the sequencing interface mainly acts as a middleware that connects Rollkit rollup and the sequencing layer. It implements the sequencing interface functions described above.
26-
There are several implementations of the sequencer:
26+
There are several implementations of the sequencer but for now only one is available in Rollkit.
2727

2828
* [single-sequencer](/learn/sequencing/single.md) - The simplest and most widely used sequencing model, where a single node (the sequencer) is responsible for ordering transactions and producing blocks.
29-
30-
* [based-sequencer](/learn/sequencing/based.md) - A more decentralized model where multiple sequencers work together to order transactions and produce blocks, improving censorship resistance (Not available yet).
31-
32-
* [forced-inclusion-sequencer](/learn/sequencing/forced-inclusion.md) - A model that ensures all transactions are included in the rollup, even if they are not ordered by the sequencer, providing strong guarantees against censorship. (Not available yet).

learn/sequencing/single.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,18 +24,9 @@ A single sequencer is the simplest sequencing architecture for a Rollkit-based r
2424
- **Simplicity:** Easy to set up and operate, making it ideal for development, testing, and small-scale deployments.
2525
- **Low Latency:** Fast block production and transaction inclusion, since there is no consensus overhead among multiple sequencers.
2626

27-
## Considerations
28-
29-
- **Centralization:** The sequencer is a single point of control. However, this is often acceptable for many applications, especially in early stages or permissioned environments.
30-
- **No Fault Tolerance:** If the sequencer is unavailable, the rollup cannot make progress. High-availability setups and monitoring can mitigate this risk.
31-
3227
## Use Cases
3328

3429
- Production rollups seeking simplicity and performance
3530
- Prototyping and development
3631
- Private or permissioned rollups
3732
- Projects that value deterministic ordering and operational control
38-
39-
## Future-Proofing
40-
41-
While the single sequencer model is robust and production-ready, Rollkit is designed to support more advanced sequencing architectures in the future. Projects can seamlessly upgrade to decentralized sequencing when the technology and their needs mature.

0 commit comments

Comments
 (0)