Skip to content

Commit f72382c

Browse files
will-break-itrphair
authored andcommitted
Update docs/cip/README.md
cip: apply review Co-authored-by: Robert Phair <[email protected]>
1 parent 8c70329 commit f72382c

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

docs/cip/README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,12 @@ Ouroboros Praos cannot support the high transaction volume needed to generate th
7878

7979
To understand the ledger design challenges, it's essential first to understand the key components of the Leios protocol:
8080

81-
**Five-Stage Pipeline**: The protocol operates through a structured five-stage pipeline: (1) **Propose** - IBs generated uniformly, (2) **Deliver 1** - IB diffusion using freshest-first strategy, (3) **Deliver 2** - complete IB delivery, (4) **Endorse** - EBs generated at stage start, (5) **Vote** - voting on EBs and certificate creation. This pipeline approach enables concurrent transaction processing while maintaining deterministic ordering and conflict resolution.
81+
**Five-Stage Pipeline**: The protocol operates through a structured five-stage pipeline:
82+
1. **Propose** - IBs generated uniformly
83+
2. **Deliver 1** - IB diffusion using freshest-first strategy
84+
3. **Deliver 2** - complete IB delivery
85+
4. **Endorse** - EBs generated at stage start
86+
5. **Vote** - voting on EBs and certificate creation
8287

8388
**Input Blocks (IBs)**: Transaction-containing blocks produced at a uniform rate during the "Propose" stage of each [pipeline](#pipeline). IBs are generated by stake pools that win VRF-based [sortition](#sortition), with the protocol utilizing approximately one-third of available network bandwidth for IB traffic. Multiple IBs can be produced concurrently across the network.
8489

0 commit comments

Comments
 (0)