High level summary​

After spending the last months on improving DBSync and releasing 13.1.0.0 the DBSync team focused the last weeks on integrating upstream changes and tech debt. This includes integrating CHaP, the new leger core and ghc-9.2.4

Lower level summary​

• Integrate CHaP #1331
• Integrate new ledger core 0.1.1.1 and ghc-9.2 #1332
• Technical debt: Add code formatter fourmolu #1334
• Preparing and tracking Conway and UTxO integration

High-level summary​

Since last weekly update before christmas, the Hydra team worked on the technical specification, closed gaps in hydra-plutus scripts, made the unique headId available to Hydra clients through the API, allow the hydra-node to explicitly synchronize from genesis (if configured), and fixed smaller log and build issues reported by new users.

Besides this, a retrospective blog post was published by Matthias Benkort (CF) on Hydra, summarizing our progress made in 2022 also an outlook where Hydra is headed for in 2023. Also, the team had some first sessions on the voting project with Catalyst and the CF.

A full digest monthly digest for December 2022 can be found on the hydra website.

What did the team achieve this week​

• Had some first sessions on the voting project with Catalyst and CF
• Published retrospective blog post by Matthias Benkort (CF) on Hydra, summarizing our progress made in 2022 also an outlook where Hydra is headed for in 2023.
• Worked on the LaTeX spec for HydraHeadV1, not final or published yet - latest version in this repository.
• Add unique headId to API and hence make it available to clients.
• Allow hydra-node to explicitly synchronize from genesis using --start-chain-from 0.
• Closed gaps in hydra-plutus scripts
  • bounded transaction validity (ADR21)
  • enforcing contract continuity via state token in output
• Fixed JSON for some logs and smaller build issues reported by new users.

What are the goals of next week​

• Reach out to have hydra-tutorial integrated.
• Plan the next couple of months.
• Complete checking reimbursing of commits in head validator.
• Align plutus scripts to spec and simplify them (identified some simplifications)
• Improve mutation framework to be sure we fail tests for the right reasons
• Complete the spec except the open points (<5) and also discuss them with researchers.

Node Reelease Update​

2022-11-02 - 2023-01-13​

Executive Summary​

A 1.35.5 release for single relay P2P is nearly completed and should be released this month. This release is based on release/1.35 branch and does not bump cardano-ledger.

The team successfully integrated an interim release bump of ledger and consensus into cardano-node master. This work will not be released in a node version, but will be continued by the current dependency bump in progress.

We anticipate once this dependency bump is completed, regular 2 week releases will be feasible again.

The 1.35.4 release is being ran by more than 70% of stake pools. Planning for the mainnet hard fork date is in progress.

Completed​

• Release 1.35.4

In Progress​

• Release 1.35.5

  • Test Status

High level summary​

During the last 2 weeks we did more improvements on our Test Framework, ran some sanity tests related to the P2P Single Relay functionality.

We also update the Node & DB-Sync sync tets to build with Nix as the prebuilt files are no longer available at PR level.

Workstreams​

Framework improvements:​

• extended the cardano-node-tests with the ability for anybody to fork the repo and run all our System Tests on GitHub Actions
• added 2 new nightly pipelines - nightly-mixed and nightly-p2p - details here
• some optimizations on how our regression tests are scheduled on pytest workers and how cluster instances are assigned to the tests;

=== 743 passed, 67 skipped, 24 xfailed in 9166.64s (2:32:46) === to === 753 passed, 67 skipped, 14 xfailed in 4654.80s (1:17:34) ===

Node:​

• ran a couple of sanity runs of CLI a& sync tests on a local branch with P2P Single Relay enabled
• started the preparations for testing the next tag - details here

DB-Sync:​

• some improvements on db-sync sync tests

High level overview​

The Mithril team has been designing a mechanism for handling seamless updates of the Mithril networks in case of breaking-changes that require synchronous update of the signer nodes. This design has been formalized in an ADR. They have been working on an implementation of a proof of concept to rely on an on-chain transaction to synchronously trigger the version switch of all the signer nodes. They have also worked on implementing prototype solutions to minimize the use of breaking changes where soft updates are possible.

Finally, they have worked on upgrading the devnet and fixing some flakiness in the end to end tests of the CI.

Low level overview​

• Implemented the redaction of an ADR for handling graceful updates of the Mithril Network #671
• Worked on a proof of concept to handle backward compatibilty of exchanged messages with protobuf #677
• Worked on a proof of concept to handle backward compatibilty of exchanged messages with avro #678
• Worked on a proof of concept for reading/writing era activation markers with a Cardano chain transaction #672
• Worked on upgrading the Cardano node of the Mithril devnet, as well as fixing flakiness of the CI #523
• Prepared and tested the new 2302 distribution pre-release 2302.0-prerelease
• Updated the documentation for SPO to build a signer node in order to better reflect the new release process #681