Cardano Leios Testnet Don Reach Throughput Wey Be Six Times Pass Mainnet
The completed Earth phase produced Leios’ first public throughput measurement under distributed network conditions. Water now moves into parameter testing, a redesigned mempool and broader stake pool operator participation.
By SongMarketCap
Updated:
Public Leios testnet for Cardano reach 26.8 transaction kilobytes per second for the Earth phase wey dem just finish, according to Leios product manager Carlos Lopez de Lara. The rate wey dem observe near six times pass the current Cardano mainnet limit wey be about 4.5 TkB/s.
This result show during the time wey Input Output and community participants dey generate load at the same time, no be formal maximum throughput test. MusashiNet don enter the Water phase now as the team dey prepare different protocol configurations and the governance path wey Leios need to enter Cardano through the Dijkstra hard fork.
Leios Earth Phase Deliver Him First Public Throughput Result
Ouroboros Leios na the base layer scaling protocol wey dem propose for Cardano. E dey run side by side with Ouroboros Praos and e introduce endorser blocks, wey allow larger volume of transaction data to process in parallel while Praos still be the network security and settlement mechanism underneath.
MusashiNet na the public environment wey dem dey use move the Leios prototype from controlled development networks enter infrastructure wey expose am to real latency, hardware and network conditions. The Earth phase focus on to verify whether the complete protocol design still dey function well for that kind setting.
Input Output use one transaction generator wey dem call TX Centrifuge to create enough traffic to activate Leios. Community participants at the same time use TX Firehose, one simpler load generation tool wey dem make available for public testing. The throughput wey dem report happen during one period wey both sources dey generate transactions together.
The measurement no be TPS figure. TkB/s na the volume of transaction data wey dem process per second, while the number of transactions fit vary based on their size and complexity. Because the run no be formal stress test, the rate wey dem observe no establish any published capacity limit for Leios.
The network get 62 block producers during the Earth phase, and the development team release ten versions of the prototype within six weeks. Lopez de Lara still report five incidents, include forks and testnet halts.
According to him update, dem trace each incident to implementation bug wey no show for smaller local environments. The team no identify any one as fundamental failure for the Leios protocol design. Dem analyze the issues, correct them, and release updated prototype versions after.
One dedicated red team still dey test Leios against him threat model, dey attack the system to find weaknesses before dem convert the prototype to production grade code.
Water Phase Add Parameter Testing and SPO Rewards
The Water phase go shift focus from just validating the basic protocol design to explore different configurations. The team go adjust timing settings, block sizes and component implementations to find the combinations wey fit give stable and sustainable throughput.
Testing go include one redesigned mempool wey aim to address limitations wey dey show more under heavy transaction loads. Dem go evaluate the new component alongside further increases in testnet activity.
Input Output don also open the Musashi Testnet Rewards Program for stake pool operators. The program dey reward operators for maintaining infrastructure for MusashiNet and for sharing operational data from their nodes.
The telemetry wey dem request go likely include forging, voting and diffusion logs, node versions, clock offsets and host resources. When dem combine information from multiple operators, e go help the team reconstruct how blocks, votes and certificates dey move through geographically distributed network.
The program fit support up to 100 pools. Operators must show say dem control their pool, register BLS verification key and provide mainnet ADA address for payments. The testnet faucet dey delegate one million test ADA to each registered pool so e fit produce blocks and participate for Leios voting committees.
Applications don open, even though the detailed monthly qualification criteria still dey finalize. The official documentation talk say rewards base on participation and data sharing, no be on technical performance.
Dijkstra Rollout Create One Governance Dependency
Lopez de Lara confirm say dem plan deploy Leios through the Dijkstra era, Cardano next hard fork. Before activation, the team intend to propose one technical update to the Cardano Constitution wey go cover the new protocol parameters and their guardrails.
Dem expect to submit the update between late September and early October. Lopez de Lara talk say e suppose remain limited to technical changes wey Dijkstra require, make dem no join am with other constitutional amendments wey no relate.
The rollout plan still call for conservative initial Leios settings, then gradual capacity increases as operational evidence dey available. Some parameters fit raise later but dem no go fit reduce am without another hard fork, and higher infrastructure requirements go directly increase costs for stake pool operators.
That schedule overlap with Cardano Update Constitutional Committee action. Four of the committee seven seats go expire on September 1. If dem no ratify the replacement action, the committee go fall below the minimum of five members wey normal governance operations require.
Undersized committee go prevent the planned technical constitutional update from advancing until dem restore the committee. Lopez de Lara therefore call on DReps and SPOs to vote on the current action, directly connect the committee decision with the proposed Leios timeline.
Earth close with one functioning public prototype, ten releases and no fundamental protocol failure wey the team identify. Water must now turn the initial throughput result to stable mainnet configuration, while the committee vote and the technical Constitution update go determine whether those parameters fit enter Dijkstra governance on the proposed schedule.