Skip to content

Commit cce0368

Browse files
Merge branch 'main' into cip/review
2 parents 2e4b28e + 1b034f0 commit cce0368

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

site/news/2025-06-17-weekly-progress-summary.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,13 @@ This week, the Leios team conducted extensive experiments using the previously d
1010
## CDDL specification draft
1111

1212
- Created initial CDDL specifications for core Leios components:
13-
- Input Blocks with VRF lottery and single IB/slot limits
14-
- Endorser Blocks as new aggregation block type
15-
- Ranking Blocks as Conway extension with optional certificates
13+
- Input blocks with VRF lottery and single IB/slot limits
14+
- Endorser blocks as a new aggregation block type
15+
- Ranking blocks as Conway extension with optional certificates
1616
- BLS voting system with persistent/non-persistent voters and key registration
17-
- Follows crypto-benchmarks implementation approach while maintaining Conway CDDL compatibility
18-
- Established foundational structures in first draft covering common base components
19-
- Future iterations will add detailed specifications for design variants including full sharding, overcollateralization, and protocol extensions.
17+
- Followed crypto-benchmarks implementation approach while maintaining Conway CDDL compatibility
18+
- Established foundational structures in the first draft covering common base components
19+
- Future iterations will add detailed specifications for design variants, including full sharding, overcollateralization, and protocol extensions.
2020

2121
## Formal methods
2222

@@ -28,24 +28,24 @@ This week, the Leios team conducted extensive experiments using the previously d
2828

2929
- Conducted empirical bandwidth measurements using `iperf3` between data centers in North America and Europe
3030
- Measured bidirectional connections across multiple cloud providers (OVH, AWS, CenturyLink)
31-
- Results ranged from 95 Mbps to 973 Mbps depending on geographic distance and provider
31+
- Results ranged from 95 Mbps to 973 Mbps, depending on geographic distance and the provider
3232
- Identified 100 Mbps as a conservative lower bound for inter-datacenter connections
3333
- Observed 5-20% reduction in individual link speeds when multiple simultaneous connections are active.
3434

3535
## Large-scale network experiments
3636

3737
- Conducted comprehensive experiments using both the 750-node and 10,000-node network topologies with Haskell and Rust simulations
3838
- Studied transaction and IB throughput limits for realistic scenarios up to 300 TPS and 32 IB/s
39-
- Key findings from the 750-node mini-mainnet experiments documented in [analysis results](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w24/analysis.ipynb) and [summary slides](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w24/summary.pdf):
39+
- Key findings from the 750-node mini-mainnet experiments are documented in [analysis results](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w24/analysis.ipynb) and [summary slides](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w24/summary.pdf):
4040
- The 750-node mini-mainnet serves as a suitable replacement for the 10,000-node pseudo mainnet for performance measurements
4141
- Substantial agreement between Haskell and Rust simulations for mini-mainnet scenarios
4242
- Block propagation times under one second, consistent with empirical observations from pooltool.io
4343
- Protocol can support 25 MB/s throughput with 1 Gb/s links before degradation
44-
- Mean transaction time from mempool to ledger approximately 150 seconds
44+
- Mean transaction time from mempool to ledger is approximately 150 seconds
4545
- Achieved 80% disk-space efficiency with ~20% network traffic overhead
46-
- Six-core VM sufficient for peak demand at 300 TPS, with average demand under two cores
47-
- Results from 10,000-node pseudo-mainnet experiments available in [analysis documentation](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w23/analysis.ipynb) and [presentation slides](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w23/summary.pdf):
46+
- Six-core VM is sufficient for peak demand at 300 TPS, with average demand under two cores
47+
- Results from 10,000-node pseudo-mainnet experiments are available in [analysis documentation](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w23/analysis.ipynb) and [presentation slides](https://github.com/input-output-hk/ouroboros-leios/blob/main/analysis/sims/2025w23/summary.pdf):
4848
- Average transaction lifecycle of 100 seconds from mempool to ledger
4949
- Approximately 80% efficiency for both disk and network usage
50-
- Six CPU cores sufficient for peak load handling even at high TPS rates
50+
- Six CPU cores are sufficient for peak load handling even at high TPS rates
5151
- Block propagation time averaged under one second across the large network.

0 commit comments

Comments
 (0)