Cardano Leios dey Target Three to Five Times of Current Capacity

Input Output outline their plans on October 20 to introduce Ouroboros Leios through Cardano Dijkstra hard fork. The protocol go first target three to five times today transaction data capacity, and later parameter updates go aim reach ten to fifteen times the current level. Activation go follow after stake pool registration once the fork don happen.

Leios Go Add Capacity When Cardano Traffic Don Full

Ouroboros Linear Leios dey designed to process more transactions when demand pass the capacity wey existing Praos blocks fit handle. E still keep those blocks and add endorser blocks wey get references to extra transactions.

The protocol still expand the mempool, the place wey nodes dey keep transactions wey dey wait make dem process. This one give the network more space to accept pending transactions during busy time.

Capacity dey measured in kilobytes of transaction data per second. The number of transactions wey dem fit process depend on their size and computational requirements.

Stake Pools Must Register Leios Voting Keys

After Dijkstra, stake pool operators go register BLS keys to join Leios voting. Input Output estimate say activation go need registered pools wey represent about 90% to 95% of delegated ADA, based on final protocol parameters.

Under the configuration wey dem describe, participating pools dey validate endorser blocks and dey cast votes wey dem weight by the ADA wey dem represent. Certification need votes wey cover at least 75% of total active stake. BLS signatures go combine those votes into one compact certificate.

Pools wey no register keys fit still dey produce Praos blocks but dem no go fit vote on Leios endorser blocks.

Mainnet Tests Go Guide Further Leios Increases

MusashiNet 41-day Earth phase reach one peak of 26.8 kilobytes of transaction data per second, compare with Praos mainnet ceiling of about 4.51. The test involve synthetic traffic and participating operators. The team report fixes for implementation faults wey testing uncover, including synchronization problems and invalid-certificate handling.

After mainnet activation, controlled traffic bursts go measure block propagation, voting performance, certificate reliability, and spare node capacity.

At least two other parameter updates dey planned, each one need separate governance approval inside constitutional limits. These changes no go need another hard fork. The October 20 announcement no specify Dijkstra activation date.

Each capacity proposal go need measurements from the previous operating level, to give governance evidence whether the live network fit support the extra load before dem approve higher limit.