| 
 | 1 | +---  | 
 | 2 | +title: Weekly Summary – September 1, 2025  | 
 | 3 | +authors:  | 
 | 4 | +- will  | 
 | 5 | +tags: [progress, update, weekly, cip-publication, technical-report, network-analysis, proposed-leios, simulation-analysis]  | 
 | 6 | +---  | 
 | 7 | + | 
 | 8 | +This week marked a significant milestone with the formal publication of the Ouroboros Leios CIP proposal, complemented by the release of the second comprehensive technical report and extensive network performance analysis. The team successfully delivered the definitive protocol specification and supporting evidence to the Cardano Foundation for formal review.  | 
 | 9 | + | 
 | 10 | +## Major milestone achievement  | 
 | 11 | + | 
 | 12 | +### CIP proposal publication  | 
 | 13 | + | 
 | 14 | +The team published the [Ouroboros Leios CIP proposal](https://github.com/cardano-foundation/CIPs/pull/1078) to the Cardano Foundation CIPs repository, representing the culmination of extensive research, analysis, and specification development. The proposal has been submitted for formal review and is pending CIP number assignment at the next CIP meeting. This submission provides the definitive technical specification for the proposed Leios protocol implementation, establishing the foundation for community review and potential integration into the Cardano ecosystem.  | 
 | 15 | + | 
 | 16 | +### Second technical report release  | 
 | 17 | + | 
 | 18 | +The team completed and released the [second technical report](https://github.com/input-output-hk/ouroboros-leios/blob/main/docs/technical-report-2.md), capturing comprehensive modeling, simulation, and analysis findings from March to August 2025. This substantial document covers network protocols, threat model analysis, simulation experiments, test network topologies, empirical Cardano network measurements, analytic studies of proposed Leios behavior and performance, and extensive technical observations. The report provides provisional findings and conclusions acknowledging the evolving nature of the protocol design during the study period.  | 
 | 19 | + | 
 | 20 | +## Network infrastructure analysis  | 
 | 21 | + | 
 | 22 | +### Inter-datacenter bandwidth measurements  | 
 | 23 | + | 
 | 24 | +The team conducted extensive inter-datacenter bandwidth measurements using `iperf3` for bidirectional testing between locations across North America and Europe. The comprehensive analysis examined bandwidth between OVH, AWS, and CenturyLink infrastructure across multiple geographic regions, establishing empirical baselines for network performance expectations in distributed deployment scenarios.  | 
 | 25 | + | 
 | 26 | +Key findings from the bandwidth analysis indicate that 100 Mbps represents a conservative lower bound for inter-datacenter connectivity, with significant variation based on geographic distance and infrastructure provider combinations. The measurements revealed bandwidth ranges from 95 Mbps (CenturyLink Colorado to OVH Canada) to 973 Mbps (AWS Oregon to OVH Oregon), providing critical input for proposed Leios deployment planning and parameter optimization.  | 
 | 27 | + | 
 | 28 | +### Network degradation resilience analysis    | 
 | 29 | + | 
 | 30 | +The team completed comprehensive [network degradation experiments](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/degraded/) examining proposed Leios behavior under severely constrained network topologies. The analysis systematically reduced network connections by up to 87% from original mainnet-like topology configurations, testing protocol resilience under extreme network degradation scenarios.  | 
 | 31 | + | 
 | 32 | +The degradation experiments demonstrated that proposed Leios continues operating correctly even when 87% of network connections are lost, with network diameter increasing from 5 to 8 hops and average connections per node dropping from 23.5 to 6.0. The protocol maintained functionality under both honest scenarios and adversarial conditions where attackers delay transaction and EB releases, indicating robust operation under degraded network conditions.  | 
 | 33 | + | 
 | 34 | +## Validation performance analysis  | 
 | 35 | + | 
 | 36 | +### Quantile regression analysis  | 
 | 37 | + | 
 | 38 | +The team extended [ledger operation analysis](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/timings/ReadMe.ipynb) with comprehensive quantile regressions at 50th, 95th, and 99th percentiles for ledger "apply" and "reapply" operations. This analysis addressed concerns about validation time interference between EB reapplication and Praos block release timing.  | 
 | 39 | + | 
 | 40 | +The quantile analysis provides predictions for full EBs with varying Plutus script intensities, demonstrating that "apply" operations occur distributed across multiple slots and computational threads, while "reapply" operations must complete before new Reference Blocks (RBs) and EBs can build upon newly certified EBs.  | 
 | 41 | + | 
 | 42 | +## CIP documentation enhancements  | 
 | 43 | + | 
 | 44 | +### Updated figures and regression validation  | 
 | 45 | + | 
 | 46 | +The team regenerated comprehensive figures for CIP inclusion using the upgraded `sim-cli` version 1.3.0 with updated diffusion and voting duration configurations. The [regression experiment analysis](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/regression/analysis.ipynb) compared performance across simulator versions, revealing minimal discrepancies but slightly reduced performance with version 1.3.0 compared to previous versions.  | 
 | 47 | + | 
 | 48 | +## Next steps  | 
 | 49 | + | 
 | 50 | +- Monitor CIP review process and respond to community feedback  | 
 | 51 | +- Continue protocol parameter refinement based on ongoing analysis  | 
 | 52 | +- Extend network analysis to additional deployment scenarios    | 
 | 53 | +- Develop implementation guidelines based on technical report findings.  | 
0 commit comments