Cardano Leios Testnet Enters Readiness Phase as 1k TPS Showcase Advances but Release Candidate Remains at 0%
Ouroboros Leios is moving toward a dedicated public testnet phase in June 2026, with Cardano preparing to measure Layer 1 scaling through load testing, SPO readiness, developer integration and parameter tuning before any serious mainnet path can be evaluated.
By SongMarketCap
Updated:
Cardano Leios Moves From Monthly Progress to Testnet Readiness
Cardano’s Ouroboros Leios roadmap is entering a more important phase than another development update. After the April Leios Monthly Review showed progress across prototype behavior, benchmarks, Cardano CLI preparation, mempool work and committee design, the next question is no longer only what the engineering teams have built. The question now is whether Leios can move into broader public network testing, where performance, infrastructure requirements and operator readiness can be measured together.
The latest IOG Leios development tracker gives that story a more concrete shape. It currently lists the Leios testnet at 24 percent, the Showcase 1k TPS milestone at 64 percent and the Release Candidate at 0 percent. That combination is important because it shows progress without pretending the upgrade is finished. Leios is no longer just a research idea, but it is also not yet a mainnet-ready release.
Ouroboros Leios is described on the official Leios website as a high throughput protocol for Cardano, designed to improve network bandwidth, accelerate transaction processing and preserve the security properties of Ouroboros. The same source frames Leios as a scaling upgrade that aims to improve throughput by around 50 times while maintaining decentralization. In the proposed CIP specification, the target is more specifically described as a 30 to 50 times throughput increase, from roughly 4.5 TxkB/s to around 140 to 300 TxkB/s.
That distinction matters. The new Leios story is not simply that Cardano is “going to 1,000 TPS.” That number is useful as a benchmark target and public showcase goal, but it should not be treated as a current mainnet result. The more serious story is that Cardano is preparing to test whether its scaling assumptions can hold under public testnet conditions, with real infrastructure, real operators and measurable network data.
This is why the June 2026 testnet window matters. If Leios is going to become one of Cardano’s most important Layer 1 upgrades, it must prove more than raw throughput. It has to show whether higher capacity can be achieved without weakening the decentralization, security and operational accessibility that define the network.
Leios Testnet Will Measure Throughput, Parameters and Network Limits
The Leios roadmap defines the testnet as a larger scale public test network created to validate parameter selection, conduct continuous load testing and support ecosystem integration. It specifically includes SPOs, developers and infrastructure providers as participants who need to evaluate how Leios behaves outside a narrow prototype environment.
That makes the testnet more than a performance demo. A blockchain can publish ambitious throughput targets, but the harder question is whether the system can sustain larger data flow without creating unacceptable tradeoffs in latency, infrastructure requirements, certification behavior or decentralization. For Cardano, that question is central because the network has built its identity around predictable engineering and broad operator participation.
Leios also changes the scaling discussion because it does not simply rely on bigger blocks. The official Leios materials describe a design where block producers can create a standard Praos block and an additional Endorser Block that references extra transactions. Those Endorser Blocks then go through committee validation before the referenced transactions become part of the permanent ledger state.
That architecture creates the need for deeper testing. The network must measure how transaction data moves, how votes propagate, how certification behaves, how latency changes under load and how infrastructure performs across different node and network conditions. A high TPS figure is only meaningful if those supporting layers remain stable.
The roadmap also identifies the parameter work that must happen before any responsible mainnet path. That includes timing parameters such as L_hdr, L_vote and L_diff, along with size limits such as S_EB and S_EB-tx. The planned work includes synthetic load generation, possible condensed mainnet replay, breaking point analysis, operational margin identification and a parameter graduation plan from testnet toward mainnet scale up.
This is the real technical checkpoint. Leios has to show where Cardano can safely increase capacity, where the limits appear and which parameters can be adjusted without creating new risks. A successful testnet will not be judged only by the highest number shown in a benchmark. It will be judged by whether the data is repeatable, transparent and useful enough to guide the next stage of the roadmap.
SPO and Developer Feedback Will Decide the Value of the Testnet
The IOG development tracker shows that Leios remains an active engineering track. It currently lists 4.3K commits in the past year, 5.4K lines of code merged in the past three months, 43 completed tickets and 684,504 lines of code so far. Those numbers do not prove success by themselves, but they show that the project is being tracked through visible engineering work rather than broad scaling claims.
For SPOs, the testnet phase is critical because higher throughput always has an operational cost. Operators need to understand node behavior, resource utilization, monitoring requirements, configuration changes and network stability under sustained load. If Cardano increases capacity but makes participation harder for smaller or independent operators, the network could gain speed while weakening one of its most valuable properties.
For developers, the testnet should clarify how Leios related changes affect wallets, SDKs, explorers, node tooling and application design. Higher throughput only matters if it becomes usable capacity for real products. That means documentation, integration paths, predictable interfaces and enough testing time for builders to understand how their applications behave in a higher capacity Cardano environment.
This is also where the community narrative needs discipline. “1,000 TPS” is an easy number to repeat, but it is not the full measure of Leios. The real test is whether Cardano can connect throughput, latency, committee behavior, certification rate, chain quality, infrastructure compatibility and SPO usability into one coherent scaling path.
The strongest version of the Leios story is not that Cardano has already solved scaling. It is that the network is preparing to expose its next major scaling design to public measurement before mainnet pressure arrives. If the June testnet produces clear benchmark reports, visible operational margins, useful SPO feedback and a credible parameter graduation plan, Cardano will have a stronger case that Leios is moving from theory into engineering evidence. If the tests reveal bottlenecks, that will also be valuable, because this is exactly the kind of upgrade where problems should appear on a dedicated testnet before they ever reach mainnet.