Tweag Dey Test Latest Peras Code for Cardano Testnet

According to their October 9 development report, Tweag don bring up initial Cardano testnet wey get di latest Peras code enabled. Di proposed consensus upgrade dey designed to shorten di time wey person go wait to get high confidence say ADA transaction go remain for di accepted chain.

Peras Voting Target Faster Cardano Settlement

Di first issues wey dem meet for di testnet mainly need parameter adjustments to fit di faster pace. Developers still continue to integrate Prometheus for operational monitoring and to improve how di test environment take easy to use.

Ouroboros Peras add voting join Cardano Praos consensus protocol. When votes for one block reach di required quorum, dem go form certificate wey go increase di block weight for chain selection. This one dey reduce di chance say di block and di ones before am go roll back.

For exchanges, blockchain bridges and partner chains, settlement confidence na wetin determine when transfer fit be recognized and used. Peras aim to provide that confidence earlier for transactions wey involve ADA and other Cardano assets. Dem specify im voting mechanism for CIP-0140.

Cardano Ledger Add Peras Support

On October 13, Cardano Ledger merge one change wey supply di consensus layer with Peras parameters wey dem need for validation inside di current epoch. Di integration connect di software wey dey maintain Cardano state and rules with di component wey dey responsible to select di accepted chain.

Developers still start work to update protocol state for di beginning of each Peras voting round, independent of new block arrivals. This one allow di implementation to follow di voting schedule between blocks.

Di work still remain part of protocol development. CIP-0140 still keep im proposed status, and Tweag report no give any mainnet activation date.

Peras Certificate Storage Enter Review

Tweag report say di minimum viable implementation of di historical certificate database don complete and e dey undergo internal review. Dem don write comprehensive test suite, but updates still dey needed to reflect recent code changes.

Di proposed database dey preserve certificates once di blocks wey dem reference don become immutable for di node storage. At that point, di certificates no dey influence chain selection again but dem still dey available as historical consensus records. Di implementation wey join am still be draft pull request.

Im storage design include integrity checks and quarantine handling for missing, incomplete or corrupted files. One node fit identify di affected certificate records and request dem from other peers, to provide recovery path when im local archive get gaps.