Cardano ProjectsCardano Projects
In Progress

2026-10-02

Ouroboros Peras

This week we focused on the following topics:

  • Design

    • We engaged in some back and forth discussions with the Peras researchers after receiving their official recommendation about the concrete crypto requirements for mainnet. We will provide a concrete update on this matter after some final internal discussions.
    • We continued exploring the design space around the interaction between Genesis and the need for historical certificates. In addition, we analyzed if a recently proposed alternative design and implementation for Peras could avoid the need for historical certificate, which was later confirmed unsuitable after some discussion with the Peras researchers.
    • We started updating the Peras design document and original CIP-0140 to reflect all the knowledge gathered so far during the implementation.

  • Network

    • The team has looked into the best way to expose internal state to the densityDisconnector. They have settled on a design that’s almost ready for review and are evaluating the best way forward.

  • Consensus

    • Finished the PR in charge of reducing the transaction payload when a certificate must be included in a block. This is currently under internal review.
    • Finished the initial prototype for the PerasImmutableCertDB, still pensing some cleanup before it’s ready for internal review. Tests for this components are currently under development in a separate PR.
    • Started working on a quarantine mechanism allowing to ask for corrupted or incomplete certificates from peers. The design of this component is still subject to change depending on recent research informed requirements.
    • Tweaked the PerasCertDiffusion and PerasCertDB to index over monotonically increasing PerasRoundNos, as opposed to the previously more relaxed PerasCertTicketNo cursor.
    • Created a small patch to bypass the Peras state ticking in the upcoming release. This is to avoid having to enforce new Peras-specific constraints before all the functionality is ready for mainnet.

  • Ledger

    • Addressed final reviews and merged the initial implementation of the Peras protocol parameters.
    • Started working on forecasting support for the Peras protocol parameters to allow for validation of objects into the future from the point of view of the immutable chain tip.
    • Continued working on moving the Peras base types needed by Ledger to cardano-base.

  • Testnet