Skip to content

Commit 9d63ac1

Browse files
committed
site: update faqs
1 parent fb5cc84 commit 9d63ac1

File tree

1 file changed

+111
-23
lines changed

1 file changed

+111
-23
lines changed

site/docs/faq.md

Lines changed: 111 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -4,36 +4,124 @@ sidebar_position: 6
44

55
# FAQs
66

7-
## What are the benefits of Leios?
7+
## What is Ouroboros Leios?
88

9-
Ouroboros Leios is a blockchain protocol that improves transaction throughput and
10-
latency by using a pipelined endorsing process. Simply put, Leios is a way to
11-
process transactions faster.
9+
Ouroboros Leios is a next-generation blockchain consensus protocol designed to improve transaction throughput and reduce latency by using a pipelined endorsing process. It builds upon the core Ouroboros principles (as used by Cardano), introducing separate input blocks (IBs) for transactions and endorser blocks (EBs) that reference those transactions, thus enhancing scalability.
10+
11+
## What are the key benefits of Leios compared with traditional Ouroboros?
12+
13+
Leios offers several significant advantages:
14+
15+
- Higher throughput and lower latency. By splitting transaction processing into IB and EB stages, Leios handles more transactions in parallel.
16+
- Flexible diffusion strategies. Nodes can choose different block-propagation methods, such as 'freshest-first' or 'oldest-first.'
17+
- Enhanced cryptography. Leios uses BLS (Boneh–Lynn–Shacham) signatures for aggregated verification and verifiable random functions (VRFs) for leader selection.
18+
- Robust simulations and formal methods. Rust and Haskell simulations measure real-world performance, and executable specifications help ensure correctness.
19+
- Scalable cost model. A cost calculator enables node operators to estimate expenses (for example, storage amortization and CPU usage).
20+
21+
## What are IBs, EBs, and RBs in Leios?
22+
23+
Leios uses three distinct block types:
24+
25+
- IB (input block): a block that contains transactions. Produced by nodes that win the IB sortition lottery.
26+
- EB (endorser block): a block that references one or more IBs, providing endorsements. Produced by nodes that win the EB sortition lottery.
27+
- RB (ranking block): a block that ranks or orders other blocks as part of the consensus mechanism.
28+
29+
Each block type plays a distinct role in moving transactions from submission to final confirmation.
30+
31+
## How does Leios handle voting stages, and what is 'send-recv' voting?
32+
33+
Leios finalizes blocks through a structured voting mechanism. Nodes may adopt:
34+
35+
- Single-stage voting: all votes are broadcast in one phase, possibly resulting in a longer CPU usage 'tail' during high throughput.
36+
- Send-recv (two-stage) voting: votes are first sent, then a follow-up receive phase ensures broader propagation before final tallies.
37+
38+
You can configure voting through parameters such as leios-vote-send-recv-stages in simulation environments.
39+
40+
## What is sortition in Leios, and how does 'Fait Accompli sortition' work?
41+
42+
Sortition is a probabilistic method for selecting nodes (based on stake) to produce blocks or issue votes. In Leios, it is referred to as 'Fait Accompli sortition' because once a node proves it was selected to produce a block or vote (using a cryptographic proof), no conflicting claims can arise.
43+
44+
## What are the different block diffusion strategies, and why do they matter?
45+
46+
Leios supports multiple strategies for propagating blocks and votes:
47+
48+
- Oldest-first: prioritizes older blocks or transactions
49+
- Freshest-first: focuses on the newest blocks or transactions first
50+
- Peer-order: requests blocks in the order peers announce them
51+
52+
Your choice of strategy can affect latency, network load, and overall throughput.
53+
54+
## Can the system be sharded or self-regulate?
55+
56+
Not in its current design. Every node validates the entire chain. Thus, adding more nodes does not inherently increase throughput in the same way sharded protocols do. The community votes on protocol parameters (for example, block size), and the system's load is the same for all. Future research may explore sharding, but it is not yet part of Leios.
57+
58+
## What improvements in cryptography are used in Leios?
59+
60+
Leios incorporates multiple cryptographic techniques to ensure security and efficiency:
61+
62+
- BLS signatures: allows efficient aggregation of many signatures into one, reducing verification overhead
63+
- Mithril or Musen protocols: used for voting and proof aggregation, depending on the context
64+
- VRFs: ensures fair selection of nodes for block production
65+
66+
Recent benchmarking shows that aggregated BLS verification significantly speeds up certificate validation.
67+
68+
## How do I estimate node operating costs for Leios?
69+
70+
Leios provides an online cost calculator that considers:
71+
72+
- CPU usage and the number of cores
73+
- Bandwidth consumption
74+
- Storage (including the default assumption of 50% disk compression)
75+
- Perpetual storage cost amortization
76+
77+
It also supports hyperscale and discount cloud providers. For example, you can model single-relay or multi-relay deployments at variable bandwidths.
78+
79+
## What is the current status of Leios simulations?
80+
81+
Two primary simulation frameworks (Rust and Haskell) are maintained to:
82+
83+
- Test network topologies and measure real or simulated latencies (using the DeltaQ model)
84+
- Evaluate CPU usage for blocks and transactions under varying loads
85+
- Visualize block diffusion (IBs, EBs, and RBs) using different strategies
86+
- Compare ideal conditions vs realistic mainnet-like topologies
87+
88+
Developers continually refine these simulations based on real-world data.
89+
90+
## Are there recommended parameters for running Leios nodes?
91+
92+
Based on preliminary internal testing and simulations:
93+
94+
- Block size: commonly set to about one-third of the available link capacity for IBs
95+
- Voting stages: choose single-stage or send-recv, depending on reliability and speed requirements
96+
- Diffusion strategy: many operators use 'freshest-first,' though 'peer-order' may help maintain compatibility with older setups
97+
98+
Operators can adjust these parameters, which evolve through community votes.
99+
100+
## How do I keep track of Leios's progress and updates?
101+
102+
You can follow:
103+
104+
- Weekly progress updates on the Ouroboros Leios site
105+
- Technical reports for deeper insights
106+
- Leios glossary for definitions of commonly used terms
107+
- Public GitHub repositories that host source code and simulations
108+
109+
These resources provide transparency and regular updates on ongoing development.
12110

13111
## What are downstream effects of deploying Leios?
14112

15-
Ongoing internal discussions - we will publish an answer/link here to our
16-
findings.
113+
Leios changes how transactions are validated and how blocks and memory pools operate, potentially affecting:
17114

18-
## Could the mempool be sized to the throughput of the system?
115+
- Wallets and SDKs, which need to accommodate new block types (IBs and EBs)
116+
- Explorers, which must handle higher throughput and multi-block referencing
117+
- Indexers and APIs, which will see more granular block and vote data
19118

20-
That's already the case. Default mempool size is a small multiple of current
21-
block size.
119+
Weekly progress updates provide deeper analysis of these topics, including how advanced indexing and potential sharding solutions might eventually mitigate challenges.
22120

23-
## Can the system be sharded according to resources (small nodes vs. big nodes)?
121+
## Could the mempool be sized to the throughput of the system?
24122

25-
Leios' current design does not involve sharding in a sense of different resource
26-
requirements for different nodes. In short, the Leios design does not involve
27-
sharding. These are ideas in research and require more work. As of now, each
28-
node has to validate all blocks, hence in a traditional sense, adding more nodes
29-
does not increase throughput. Each node must cope with the throughput of the
30-
whole system.
123+
That's already the case. Default mempool size is a small multiple of current block size.
31124

32-
## Can the system self-regulate instead of manually fine tuning?
125+
## Is Leios production-ready?
33126

34-
The current system's load is imposed on each node through the protocol
35-
parameters. Thus, it remains a democratic vote, not a choice made locally by
36-
nodes or automatically. Given that the load is imposed on each node through the
37-
choice of the protocol parameters, it remains a democratic vote to drive
38-
adaptation. In a sharded approach this could be different. But in the current
39-
system there is no local or automatic choice to be made by individual nodes.
127+
Leios remains an active research and development protocol. It is backed by a robust formal methods framework and two major simulation environments. However, it has not reached full production status. Watch the official progress updates and technical reports for major release announcements.

0 commit comments

Comments
 (0)