In Progress

2026-09-04

Ouroboros Peras

This week we continued our efforts in several directions:

  • Delivered the August public demo. You can find more information here.

  • Completed the initial process of extracting changes from our integration branch into PRs targeting main. The latest changes in the pipeline include:

    From here, our integration branch only contains changes that depend on details that have not yet crystallized, and we will continue extracting PRs for review by the Consensus team as soon as they are ready.

  • Continued the investigation into Genesis and how Peras must be adapted to fit into it. Specifically:

    • We discovered the need for a PerasMaxCandidateBlockAge constant that will directly impact the Genesis window size.

    • We discovered the need to forecast the PerasEpochContext in some cases to be able to validate certs that must be taken into account for Genesis. This implies changes to the PerasEpochContextResolver, and we are currently evaluating several possible implementation options. Notably, we are considering anchoring it to the immutable tip of the chain instead of the volatile tip.

  • The Historical Certificates team now has a better understanding of the requirements for the historical certificate DB, and its implementation will start soon.

  • As for the Ledger integration, we summarized the status of this epic here. Concretely, we are slowly making progress towards integrating the changes needed to use properly-plumbed public/private BLS keys.

  • The Network team continued their efforts on caught-up detection/reporting for the ObjectDiffusion mini protocol.

  • The Testnet team made further progress on the observability front, now focusing on debugging/validating the behavior the the weighted Fait-Accompli voting committee selection algorithm.

  • On the documentation side:

    • Work continued on the Constitution update proposal about the governable parameters required for Peras. In parallel, we started preparing the ground for the Ledger changes needed to implement them as soon as the proposal stabilizes.
    • We started preparing an up-to-date, high-level architecture description of the current Peras components, including details about how they interact with one another.