Cardano Peras Moves Certificate Handling Into Protocol Code

Ouroboros Peras is moving beyond protocol specifications into the code paths that determine how Cardano nodes store certificates, synchronize them with peers and reserve block space for consensus data. Tweag reported the work alongside testnet updates and a review of the cryptographic voting analysis. Peras remains planned for a later Dijkstra phase, with no announced mainnet activation date.

Peras Certificate Storage Moves Into Consensus Code

An initial implementation of ImmutablePerasCertDB has been submitted through pull request 2293 in the Ouroboros Consensus repository. The database is designed to provide persistent storage for Peras certificates and is currently undergoing internal review.

Peras extends Ouroboros Praos with stake based voting and block certification. Its certificates aggregate evidence that participating stake has endorsed a block, giving nodes additional information when evaluating settlement confidence.

If activated, Peras could allow exchanges, bridges and wallets to reach stronger settlement confidence for ADA transactions after fewer blocks. These services would rely on the settlement guarantees exposed by Cardano nodes rather than handle Peras certificates as a separate user feature.

The ObjectDiffusion implementation has also gained graceful client termination and a method for detecting when certificate synchronization has caught up. That status can be used by Cardano’s governor state machine when coordinating peer connections and network synchronization.

The network design team separately proved that certificates relevant to chain selection should reach a node in ascending Peras round order when the node is connected to at least one honest peer and standard chain quality and network assumptions hold. The ordering result simplifies the planned distribution of historical and recent certificates through ObjectDiffusion.

Cardano Ledger Tests Governable Peras Parameters

The Ledger Integration team is working on the remaining Peras components required before the incoming hard fork reaches code freeze. The work includes defining which Peras protocol parameters could later be modified through Cardano governance.

A prototype has been submitted through pull request 6067 in the Cardano Ledger repository. Finalizing the parameter list will also require an update to the Cardano Constitution so that the governance framework specifies which values can be changed and the limits that apply to them.

The ledger work prepares Cardano for a future Peras deployment. Activation remains assigned to a later Dijkstra phase and will require separate testing, governance approval and a protocol version change.

Developers have also completed an initial method for estimating certificate size before block production. A Peras certificate competes with ADA and native asset transactions for capacity inside the block body, so the forging node must reserve enough space before selecting transactions.

A related pull request reduces the number of selected transactions when a block includes a Peras certificate. The adjustment prevents the node from filling the block before the required consensus data can be added.

Peras Testnet Prepares for Integrated Node Testing

The development team has merged the changes tracked as Peras 67 and Peras 68 after addressing review feedback. Two additional pull requests, Peras 69 and Peras 70, add strictness annotations and correct a query bug that was blocking nightly and testnet runs.

Testnet preparation includes an improved initialization script, centralized collection of logs and metrics and an update of the base branch to the latest Peras code. These changes are intended to make failures easier to trace when consensus, networking and ledger components operate together.

Tweag has also reviewed version 1.1 of the Peras voting analysis produced by researchers from Input Output’s Applied Cryptography team. Questions raised during the review are being used to define the delivery plan for cryptographic components required by a future mainnet implementation.

The planned testnet update will combine four previously separate capabilities: persistent certificate storage, detection of completed certificate synchronization, certificate aware block forging and ledger access to Peras parameters. Reaching that operating state depends on completing the open internal reviews and moving the testnet branch to the latest implementation.