This (short) week we focused on a couple of topics:
-
We delivered the April Peras Demo/Update session. Check out the Demo section for more information.
-
Voting committees:
- Released Peras 26 covering concrete Peras votes and certificates for review of the Consensus team.
- Addressed an initial review on Peras 23, which in turn led to the creating of Peras Peras 22.5 and Peras Peras 22.75 with some touch ups on the recently-merged generic voting committee API.
- The rest of the PRs in this stack (Peras 24, 25, and 26) are currently in stand-by awaiting for review, but we keep them up-to-date after any requested change in one of its ancestors.
-
HardFork Combinator support for Peras:
- We started documenting the temporal dependencies of the different Peras operations (e.g., forging and validating Peras votes and certificates). Notably, some are era-dependent and can be handled directly by the HardFork Combinator, while others are epoch-dependent and need to be handled in different ways depending on the context.
- We aim to have a concrete implementation plan fairly soon.
-
Peras certificates in blocks:
- Coordinated with the Ledger team to enhance the exiting placeholder for Peras certificates in block bodies with an opaque
ByteArraypayload. - Started looking into extending the block-forging logic in the Consensus side to accept an optional Peras certificate (subject to the certificate inclusion rules implemented in Peras 19).
- Coordinated with the Ledger team to enhance the exiting placeholder for Peras certificates in block bodies with an opaque