This week we focused on the following topics:

Peras design
- Started preparing a document aimed at the Cardano Steering Committee with options and considerations for the crypto implementation needed by Peras on mainnet.
- Continue revising Peras CIP and Peras design document so they are up to date with recent developments.
Testnet
- Launched an initial testnet setup with the latest Peras code enabled and started debugging some of the preliminary issues that popped up, most of them related to tweaking parameter to adjust Peras to the testnet’s faster pace.
- Continued working on integration of Prometheus support.
- Continued working on polishing the testnet UX.
Ledger
- Opened cardano-ledger#6126 with the changes needed to forecast the Peras protocol parameters of the current epoch. This will be followed by changes in Consensus to shift the validation context resolver by one epoch into the past and use forecasting for the present one.
- Opened cardano-base#700 and cardano-base#701 to start migrating part of the code in Consensus that needs to be made available to Ledger.
Consensus
- Finished implementing historical certificate database prototype (MVP), which is currently under internal review.
  - Wrote a comprehensive test suite for the database (to be updated to account for recent changes).
- Started working on ticking the extended ledger state at the start of Peras rounds, independently of processing new blocks.
- Opened #2326 for internal review, which replaces PerasCertTicketNo with PerasRoundNo in the VolatilePerasCertDB.
- Isolated commits related to certificate size restrictions from the Peras working branch, and opened Peras #73 against main.
Networking
- Continued waiting for a review of #5431 from the Network team, with Peras 71 and Peras 72 now approved (in spirit) and ready to be integrated against it.
- Started working on allowing certificate diffusion download validatable certificates only.
- Started working on changes to signal the next round number in the outstanding FIFO.

2026-10-09