Skip to content

Commit c0aba5b

Browse files
committed
site: weekly updatepwd
1 parent 0858589 commit c0aba5b

File tree

3 files changed

+121
-0
lines changed

3 files changed

+121
-0
lines changed

Logbook.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,12 @@
22

33
## 2025-08-08
44

5+
## CIP Progress
6+
7+
- The draft of the specification section is now complete, except for the network and incentives components.
8+
- The motivation and abstract have been refined for clarity.
9+
- The first of the four main rationale subsections has been fully drafted.
10+
511
### Another Haskell vs Rust comparison
612

713
The experiment [analysis/sims/202532b](analysis/sims/202532b) compares Haskell vs Rust simulation output at newer commits. Results indicate that a previous discrepancy in vote diffusion has been resolved.
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
title: Weekly Summary – July 28, 2025
3+
authors:
4+
- will
5+
tags: [progress, update, weekly, linear-leios, simulation-comparison, network-topology, stage-length, haskell-simulation, rust-simulation]
6+
---
7+
8+
This week, the Leios team focused on comparative analysis between simulation implementations and conducted experiments examining the impact of protocol parameters and network topology on Linear Leios performance. The team made progress in cross-validation between Haskell and Rust simulations while investigating protocol behavior under different network conditions.
9+
10+
## Cross-simulation analysis
11+
12+
### Haskell vs Rust Linear Leios comparison
13+
14+
The team completed a comprehensive comparison between the early draft Haskell simulator and the more mature Rust simulator for Linear Leios. Key findings from the analysis documented in [analysis/sims/2025w31b/analysis.ipynb](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w31b/analysis.ipynb) revealed several discrepancies requiring investigation:
15+
16+
- CPU usage patterns differed between implementations
17+
- Network usage showed variations across simulators
18+
- Vote diffusion behavior exhibited inconsistencies
19+
- [Active investigation](https://github.com/input-output-hk/ouroboros-leios/pull/466) underway to resolve implementation differences.
20+
21+
## Protocol parameter experiments
22+
23+
### Stage length analysis for "No IBs" Leios
24+
25+
The team conducted experiments varying the stage-length protocol parameter from 5 to 12 slots per stage in "No IBs" Leios. Results documented in [analysis/sims/2025w31/analysis.ipynb](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w31/analysis.ipynb) showed:
26+
27+
- Settlement time remains relatively stable across the tested parameter range
28+
- Stage length has minimal impact on transaction processing times within 5-12 slot range
29+
- Larger stage lengths result in less frequent voting periods
30+
- Protocol performance appears robust to moderate stage length variations.
31+
32+
## Network topology validation
33+
34+
### Mini-mainnet vs pseudo-mainnet comparison
35+
36+
The team completed a comparative analysis of Linear Leios performance across different network topologies using the Rust simulator. Key findings from [analysis/sims/2025w30b/analysis.ipynb](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w30b/analysis.ipynb) include:
37+
38+
- The 750-node mini-mainnet network proved slightly more stressful to the protocol than the 10,000-node pseudo-mainnet
39+
- No substantial differences in simulation results between the two network configurations
40+
- Both networks produce equivalent findings and conclusions for protocol analysis
41+
- Validation confirms the mini-mainnet topology as a suitable proxy for larger-scale analysis.
42+
43+
## Rust simulation enhancements
44+
45+
### Linear Leios attack modeling
46+
47+
- Added equivocation voting delay functionality to Linear Leios implementation
48+
- Implemented attack scenario modeling where endorser block (EB) diffusion is deliberately delayed until the last moment
49+
- Enhanced simulation capabilities for security analysis and adversarial behavior testing.
50+
51+
## Next steps
52+
53+
- Continue investigation of discrepancies between Haskell and Rust Linear Leios implementations
54+
- Expand parameter sensitivity analysis for additional protocol variants
55+
- Refine attack modeling capabilities for comprehensive security assessment
56+
- Apply lessons from network topology comparison to future experimental design.
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Weekly Summary – August 4, 2025
3+
authors:
4+
- will
5+
tags: [progress, update, weekly, cip, plutus, simulation-analysis, linear-leios, haskell-simulation, rust-simulation]
6+
---
7+
8+
This week, the Leios team made significant progress on the Cardano Improvement Proposal (CIP) documentation, conducted extensive Plutus validation experiments, and resolved outstanding discrepancies between simulation implementations. The team successfully demonstrated Linear Leios performance under various Plutus workloads and completed comprehensive protocol parameter analysis for CIP inclusion.
9+
10+
## CIP development progress
11+
12+
The team completed substantial portions of the Leios CIP draft, bringing it closer to submission readiness. The specification section is now complete except for network and incentives components, with the motivation and abstract refined for clarity. The first of four main rationale subsections has been fully drafted, providing evidence-based arguments for Leios necessity and viability.
13+
14+
## Plutus validation experiments
15+
16+
The team conducted comprehensive experiments examining Linear Leios performance under varying Plutus computation loads using 6-vCPU nodes at 100 TPS. Key findings from the [Plutus validation analysis](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w31c/analysis.ipynb) include:
17+
18+
- Linear Leios successfully supported doubling the Plutus per-transaction budget
19+
- Protocol breakdown occurred at sixfold increases in Plutus budgets due to validation bottlenecks
20+
- Endorser blocks could handle approximately 5,000 execution steps of Plutus computation, representing 250 times the current Praos per-block budget
21+
- This capacity could support either a handful of transactions with 20x greater Plutus budgets or increasing every Plutus transaction budget by 50%
22+
- Late diffusion of Plutus-heavy transactions poses potential risks to EB adoption timing.
23+
24+
The analysis revealed significant variability in CPU time requirements for Plutus scripts relative to their execution steps, highlighting the need for careful resource planning in high-throughput scenarios.
25+
26+
## Simulation improvements and comparisons
27+
28+
### Cross-simulation validation
29+
30+
The team completed another comprehensive comparison between Haskell and Rust simulations at [analysis/sims/202532b](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/202532b), successfully resolving previous discrepancies in vote diffusion behavior. This validation ensures both simulation implementations produce consistent results for protocol analysis.
31+
32+
### Protocol parameter optimization
33+
34+
The [2025w32 experiment](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w32/) established a comprehensive set of protocol parameters and throughput scenarios for inclusion in the CIP Evidence section:
35+
36+
- **Protocol variant**: Linear Leios with conservative resource allocation
37+
- **Resource requirements**: 4 vCPU per node, 10 Mb/s bandwidth
38+
- **Stage configuration**: 7 slots each for voting and diffusion stages
39+
- **Block limits**: Maximum 12 MB transaction references per EB
40+
- **Transaction size**: 1,500 bytes per transaction with normal Plutus frequency
41+
42+
Key performance findings demonstrate that modest computational resources adequately support throughput up to 0.3 TxMB/s, with 7-slot stages providing sufficient diffusion time while minimizing EB discard probability. The 12 MB EB limit allows occasional peak utilization to compensate for unlucky sortition periods.
43+
44+
## Implementation enhancements
45+
46+
### Haskell simulation
47+
48+
The team addressed head-of-line blocking issues in Linear Leios by implementing message slicing capabilities in the mini-protocol multiplexer, eliminating unexpected delays in vote diffusion. Additional work focused on developing new mini-protocols for enhanced Linear Leios simulation fidelity, with ongoing refinements to balance protocol granularity and sophistication.
49+
50+
### Rust simulation
51+
52+
Implementation of transaction withholding attack scenarios for Linear Leios, where EB producers delay transaction publication until EB release. The simulation also received updates to improve handling of late transactions, EBs, and RBs in Linear Leios scenarios.
53+
54+
## Next steps
55+
56+
- Complete remaining network and incentives sections of the CIP specification
57+
- Finalize mini-protocol designs for enhanced simulation accuracy
58+
- Continue investigation of mempool rule adequacy for high-throughput scenarios
59+
- Expand Plutus validation analysis to cover additional execution budget scenarios.

0 commit comments

Comments
 (0)