Skip to content

Commit 82f5852

Browse files
authored
Minor edits (#535)
1 parent 0100108 commit 82f5852

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

site/news/2025-09-01-weekly-progress-summary.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This week marked a significant milestone with the formal publication of the Ouro
1111

1212
### CIP proposal publication
1313

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.
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 assignment of a CIP number 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.
1515

1616
### Second technical report release
1717

@@ -27,23 +27,23 @@ Key findings from the bandwidth analysis indicate that 100 Mbps represents a con
2727

2828
### Network degradation resilience analysis
2929

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.
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.
3131

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.
32+
The degradation experiments demonstrated that the proposed Leios protocol continues to operate correctly even when 87% of network connections are lost, with the network diameter increasing from 5 to 8 hops and the 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.
3333

3434
## Validation performance analysis
3535

3636
### Quantile regression analysis
3737

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.
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.
3939

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.
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. At the same time, 'reapply' operations must complete before new reference blocks (RBs) and EBs can build upon newly certified EBs.
4141

4242
## CIP documentation enhancements
4343

4444
### Updated figures and regression validation
4545

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.
46+
The team regenerated comprehensive figures for CIP inclusion using the upgraded `sim-cli` version 1.3.0, which included 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.
4747

4848
## Next steps
4949

0 commit comments

Comments
 (0)