Cardano developers merged key Leios consensus and networking components, advancing a plan to raise transaction capacity as much as 15 times. The first stage targets a three-to-fivefold increase, while later stages depend on testing and governance approvals.
Cardano developers have merged key Leios code as the network pursues a planned 15-fold increase in transaction capacity. The consensus team integrated Praos2, which combines Cardano's existing consensus protocol with the Leios scaling system, into its main development branch, according to a development report.
The team also merged LeiosNotify and LeiosFetch components, which help network nodes exchange information needed to process additional transaction batches. However, work on selecting and retrieving those batches, known as endorser blocks, remains outstanding.
Rollout depends on the Dijkstra hard fork
Input Output (IOG) plans to introduce Leios through Cardano's forthcoming Dijkstra hard fork, targeting an initial three-to-fivefold increase in processing capacity. Under its rollout plan, IOG intends to raise capacity to between 10 and 15 times the network's current ceiling through at least two subsequent adjustments.
Those increases will depend on performance testing and separate governance approvals, so the timing of the full scaling plan remains uncertain.
Cardano has also yet to begin testing Dijkstra's new protocol rules on its public testnet. On Oct. 24, Intersect reported that the testnet, restarted three days earlier, was running under Cardano's existing Conway rules using node version 11.1.3. Moving to Dijkstra's protocol version 12 requires the upcoming node 11.2 prerelease and a hard-fork initiation action.
Throughput targets and approval thresholds
IOG estimates that Ouroboros Praos has a throughput ceiling of approximately 4.5 kilobytes of transaction data per second. The initial Leios rollout targets approximately 13.5 to 22.5 kilobytes per second, with later increases potentially raising that figure to between 45 and 67.5 kilobytes.
The proposed expansion begins with a constitutional amendment that requires support from delegated representatives controlling at least 75% of the relevant voting stake and two-thirds of the Constitutional Committee. Intersect said the proposal, known as CAP-12, reached its fourth draft in October, although several provisions remained unsettled.
The hard fork itself needs separate approval from delegated representatives representing 60% of stake, stake-pool operators representing 51%, and two-thirds of the committee. Each later capacity adjustment requires 67% support from delegated representatives, 51% from stake-pool operators and two-thirds approval from the committee.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
