Roadmap editing review

Author: olgahryniuk

site/docs/roadmap.md

@@ -1,99 +1,98 @@
 # Roadmap
 
-Leios is about maturing a consensus protocol design from a research paper
-through multiple [software readiness
-levels](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/technical-roadmap/project-cards-explained/software-readiness-level)
-and ultimately deploy it as a consensus upgrade onto the Cardano network.
+Leios focuses on maturing a consensus protocol design from a research paper through multiple [software readiness
+levels](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/technical-roadmap/project-cards-explained/software-readiness-level), and ultimately deploying it as a consensus upgrade on the Cardano network.
 
 ## Objectives
 
-Following our [strategy](./strategy.md), we identified several key
-**objectives** along the way which are roughly in order, but not strictly
-sequential. Instead, each will give rise to a list of **marketable features**,
-which we going to identify, progress and deliver throughout the whole lifecycle
-of this project. These objectives and features make up the actual product
-roadmap, which we are going to update and [report on every
-month](./development/monthly-reviews.md) via [this github
-project](https://github.com/orgs/input-output-hk/projects/167).
+Following our [strategy](./strategy.md), several key objectives were identified. These are broadly ordered, but not strictly sequential. Each objective gives rise to a set of marketable features that will be defined, developed, and delivered throughout the project lifecycle.
+
+Together, these objectives and features form the product roadmap, which will be updated and [reported on monthly](./development/monthly-reviews.md) via this [GitHub project](https://github.com/orgs/input-output-hk/projects/167).
 
 <a href="https://github.com/orgs/input-output-hk/projects/167">
 
 ![](./roadmap-preview.png)
 
 </a>
 
-### Improvement Proposal (CIP)
+### Cardano Improvement Proposal (CIP)
 
-> As the Cardano community, we want to learn as early as possible about what is proposed to change, so that it can be discussed across various groups and committees, and referenced in later on-chain governance.
+> As a community, Cardano participants seek early visibility into proposed changes so they can evaluate, discuss, and reference them in subsequent on-chain governance decisions.
 
-Create a Cardano Improvement Proposal (CIP) that addresses the [Cardano Problem Statement (CPS) about Greater Transaction Throughput (CPS-18)](https://github.com/cardano-scaling/CIPs/blob/master/CPS-0018/README.md). The proposed protocol design shall be applicable to Cardano and feasibility is proven by relevant analysis and simulations.
+To address the [Cardano Problem Statement (CPS-18)](https://github.com/cardano-scaling/CIPs/blob/master/CPS-0018/README.md) on greater transaction throughput, a Cardano Improvement Proposal (CIP) should define a protocol design applicable to Cardano, with feasibility demonstrated through analysis and simulation.
 
-Creating a CIP is standard procedure to disseminate and discuss protocol changes on Cardano. It will clearly motivate, specify and provide rationale of a concrete change to the Cardano consensus. The discussion will uncover potential blind spots and allow a broad audience to raise their concerns or signal agreement with the changes. The provided evidence in the form of simulation results and cost analysis will build early confidence about the feasibility of the proposed change and pave the way for required governance decisions to rollout the protocol update in a [hard-fork](#hard-fork).
+Publishing a CIP is the standard mechanism for proposing and reviewing protocol changes. It sets out the motivation, specification, and rationale for modifications to the Cardano consensus protocol. Open discussion helps identify blind spots, surface risks, and gather community feedback or support. Supporting evidence, including simulation results and cost analysis, builds confidence in the feasibility and informs governance decisions required to implement the upgrade through a hard fork.
 
 #### Scope
 
-- Refine the protocol design from what was [published by research](https://eprint.iacr.org/2025/1115.pdf) into possible variants
-- Create simulators to empirically explore protocol variants and trade-offs
-- Cost analysis and threat modeling
-- Propose a CIP to solve CPS-18 on [cardano-foundation/CIPs](https://github.com/cardano-foundation/CIPs)
-- Discuss and incorporate feedback into the CIP
+- Refine the protocol design [published by research](https://eprint.iacr.org/2025/1115.pdf) into concrete, implementable variants
+- Develop simulators to empirically evaluate protocol variants and explore trade-offs
+- Conduct cost analysis and threat modeling
+- Propose a CIP to address CPS-18 in the [Cardano Foundation CIP repository](https://github.com/cardano-foundation/CIPs)
+- Discuss feedback publicly and incorporate revisions into the CIP.
 
-This is a joint effort between innovation and engineering teams from Input Output Research (IOR) and Input Output Engineering (IOE) respectively.
+This work is a joint effort between the innovation and engineering teams at Input Output. 
 
 ### Technical specification
 
-> As a node developer, I want to understand in detail how the Leios protocol works and whether my node implementation is correct.
+> As a node developer, I want to understand in detail how the Leios protocol works and verify that my node implementation is correct.
+
+Produce comprehensive design documents, formal specifications, and conformance test suites for developers of all relevant Cardano node implementations.
 
-Create design documents, formal specifications and conformance test suites usable by developers of all relevant Cardano node implementations.
+Leios introduces a new consensus protocol and therefore requires a precise technical specification to ensure correct and consistent implementation. This applies to the Cardano node Haskell implementation as well as emerging consensus clients such as `amaru`.
 
-Leios is a novel consensus protocol and therefore requires a detailed technical specification to ensure that it is implemented correctly by all relevant Cardano node implementations. This includes the `cardano-node` Haskell implementation, but also other emerging consensus nodes like `amaru`. Node diversity is crucial for the security and resilience of Cardano, and therefore it is important that all implementations can be verified against an understandable and precise specification using conformance test suites.
+Node diversity strengthens Cardano’s security and resilience. Clear specifications, combined with executable conformance test suites, enable independent teams to validate correctness against a common standard and reduce the risk of consensus divergence.
 
 #### Scope
 
-- Node-level design, architecture and impact analysis documents
-- Threat modeling and security analysis
-- Formal specifications using Agda or similar
-- Conformance test suites that can be used by node developers to verify their implementations
-- Participate in node diversity workshops and contribute to the `cardano-blueprint`
+- Produce node-level design, architecture, and impact analysis documents
+- Conduct threat modeling and security analysis
+- Develop formal specifications in Agda or a comparable formal methods framework
+- Deliver conformance test suites that enable node developers to verify correctness
+- Participate in node diversity workshops and contribute to the `cardano-blueprint` project.
 
 ### Showcase 1k TPS
 
-> As a potential builder, I want to experience the capability of the proposed consensus upgrade and be convinced that it is as secure as claimed.
+> As a potential builder, I want to experience the capability of the proposed consensus upgrade and assess whether it meets its security claims.
 
-Demonstrate 200 TkB/s in a controlled environment using a network prototype, but also validate any assumptions and threat mitigations.
+Demonstrate 200 TkB/s in a controlled network prototype, while validating underlying assumptions and threat mitigations.
 
-A key milestone in the development of Leios is to demonstrate that it can achieve the order of magnitude higher throughput (200 TxkB/s) using real network of nodes albeit in a controlled environment. This will build confidence in the protocol design and its implementation, as well as provide a tangible demonstration of the capacity increase to the broader Cardano community. It also provides an opportunity to validate any assumptions made in the design process. In particular, having an early prototype that exercises the network layer will allow further studies of adversarial scenarios and their mitigations. It will also allow us to identify any potential blind spots or weaknesses in the protocol that need to be addressed before it can be deployed on a more public network.
+A key milestone for Leios is to demonstrate an order-of-magnitude increase in throughput, targeting 200 TkB/s, in a real network of nodes operating in a controlled environment. This provides measurable evidence of capacity gains and strengthens confidence in both the protocol design and its implementation.
+
+An early prototype that exercises the full network layer also enables validation of design assumptions under realistic conditions. It supports structured adversarial testing, assessment of mitigation strategies, and identification of weaknesses that must be resolved before deployment on a public network.
 
 #### Scope
 
-- Network prototype that can be deployed in a controlled environment
-- Visually demonstrate throughput increase over Praos
-- Early load testing and performance measurements
-- Early transaction validation benchmarks and optimizations
-- Test adversarial scenarios of stake-based and network-based attacks
-- ΔQ modeling and validating protocol parameter selection
-- Develop / integrate cryptographic primitives and prepare for audit
-- Validate understanding of required changes in key components
+- Develop a network prototype deployable in a controlled environment
+- Demonstrate throughput improvements over Praos using clear visual comparisons
+- Conduct early load testing and performance measurements
+- Benchmark and optimize transaction validation
+- Evaluate adversarial scenarios, including stake-based and network-based attacks
+- Perform ΔQ modeling and validate protocol parameter selection
+- Develop or integrate required cryptographic primitives and prepare them for audit
+- Confirm and document required changes across key system components.
 
 ### Leios testnet
 
-> As an SPO and Cardano developer, we want a dedicated network for testing and measuring the performance of Leios, so that we can update relevant infrastructure and ensure it can handle increased throughput reliably without compromising security.
+> As an SPO and Cardano developer, we want a dedicated network to test and measure Leios' performance, so we can update infrastructure and confirm it handles increased throughput without compromising security.
+
+Establish a larger-scale public test network to validate parameter selection, conduct continuous load testing, and support ecosystem integration with Leios.
 
-A larger scale public network that can be used to validate parameter selection, continuous load tests and allow everyone to integrate with Leios changes.
+Although Leios introduces limited structural changes, it modifies consensus and therefore warrants early deployment on a dedicated testnet. A public Leios network would provide a realistic environment to validate protocol behavior at scale and under sustained load.
 
-Although we believe that Leios is quite limited in structural changes, it is a consensus change nontheless and will benefit from having a dedicated testnet available as early as possible. A public network specifically for Leios will provide a realistic environment to validate the protocol under more realistic conditions and at a larger scale. It will allow SPOs, developers and other stakeholders to integrate with the changes introduced by Leios and ensure that their infrastructure can handle the increased throughput reliably. The testnet will also provide an opportunity to conduct large-scale experiments, repeated load tests and gather data on the performance of the protocol in a more realistic setting.
+It would enable SPOs, developers, and infrastructure providers to integrate Leios-related changes, assess operational impact, and verify that systems remain reliable under higher throughput. The network would also support large-scale experiments, repeated load tests, and systematic data collection to inform parameter tuning and readiness for mainnet deployment.
 
 #### Scope
 
-- Bootstrap and advertise a public testnet dedicated to Leios
-- Provide one or more node implementations that work on the testnet
-- Create tools and documentation to help SPOs and developers integrate with Leios changes
-- Continuous load testing and performance measurements
-- Monitor community infrastructure compatibility
-- Run large-scale experiments with varying load and parameter settings
+- Bootstrap and promote a public testnet dedicated to Leios
+- Provide one or more compatible node implementations for the testnet
+- Deliver tools and documentation to support SPO and developer integration
+- Conduct continuous load testing and performance measurement
+- Monitor infrastructure compatibility across the community
+- Run large-scale experiments under varying load conditions and parameter configurations.
 
 ### Hard fork
 
-> As an SPO and dRep, we want to have a mature Cardano node implementation that enables Leios and have it made available to all users of Cardano.
+> As an SPO and a DRep, we want a mature Cardano node implementation that enables Leios and is available to all Cardano users.
 
-Create a `cardano-node` release candidate and mature the feature set through `preview`, `preprod` and eventually enable it with a hard-fork on `mainnet`.
+Create a `cardano-node` release candidate and mature the feature set through `preview` and `preprod` environments, and eventually enable it with a hard fork on `mainnet`.