Overview of sprint 98 and 99​

Cardano-Node 10.6 Release​

We swiftly identified and resolved an issue in the Ouroboros.Network.Server.Simple.with function. This bug broke cardano-tracer component, [on#5224], [on#5223]. The function hasn't been used in cardano-node before. ouroboros-network-framework-0.19.2.0 was released ([chap#1157]).

We'd like to point out that cardano-node-10.6 will come supporting only P2P network stack.

For this coming release, we addressed some corner cases in topology parsing, cn#6304.

DMQ-Node​

We continued working on dmq-node. Recently, an end-to-end test was successfully run using the mithril Rust client, submitting signatures to a dmq-node, which propagated them to another instance of dmq-node. on#5203

We found out and fixed a bug in typed-protocol's annotated driver, which is used by dmq-node: on#5207.

A static build of dmq-node is now also available for the x86_64-linux-musl target:

nix build .#dmq-node-static

The trace & monitoring team is helping us to integrate dmq-node with the cardano-tracer library. The aim is to give SPO the familiar user experience when monitoring dmq-node.

Peer Selection Improvements​

A number of discrepancies were found and fixed in the peer selection logic. The peer-selection and net-sim tests were improved: on#5209, on#5232

WASM support in Ouroboros-Network​

The node team contributed a partial WASM support to ouroboros-network, on#5229.

Technical Debt Reduction​

Ouroboros-Network​

We reorganised the ouroboros-network package structure to improve maintainability and simplify our release process, on#5200.

• cardano-diffusion: everything related to diffusion for Cardano purposes, in particular cardano-node, but not only.
• ouroboros-network-api, ouroboros-network-framework, ouroboros-network-protocols packages are now sublibraries of ouroboros-network. Some Cardano-specific APIs are only present in cardano-diffusion.
• cardano-client package is now just a sublibrary: cardano-diffusion:subscription.
• cardano-ping will become a sublibrary: cardano-diffusion:ping once on#5205 is merged.

Consensus​

We addressed some outstanding TODOs in the ouroboros-consensus-diffusion package, see oc#1660.

High level overview​

This week, the Mithril team continued to implement the first phase of decentralizing the configuration parameters. They also completed enhancements to the client library and CLI, providing access to Cardano database incremental snapshots by epoch. Additionally, they kept working on the design of the snarkification of the certificates.

Finally, the team added a section about compatibility with the Cardano node in the GitHub release notes and worked on adapting to the security changes for NPM package publication.

Low level overview​

Features​

• Completed the issue Provide Cardano database incremental snapshots needed for Amaru bootstrap #2704
• Worked on the issue Decentralization of configuration parameters - Phase 1 #2692
• Worked on the issue Integrate the Haskell DMQ node in the e2e test #2674
• Worked on the issue Release 2543 distribution #2727
• Worked on the design of the snarkification of the certificates

Protocol maintenance​

• Completed the issue Cardano node compatibility in GitHub release notes #2743
• Worked on the issue Implement a common aggregator client - Phase 1 #2640
• Worked on the issue Enhance protocol security page on website #2703
• Worked on the issue Support NPM security changes with trusted publisher tokens #2745

What did the team achieve?​

• Released version 1.0.0 🎉
• Write tests to capture present limit of maximum UTxO before unable to fanout #2270
• Fix partial deposit for tokens #2285

What's next?​

• Release 1.1.0 including deposit improvements #2180
• Continue working on partial fanout #1468
• Merge documentation for committing a script UTxO #1906
• Finish working on HTLC example in Hydra #2080
• Continue working on chain following speedups #2206
• Continue supporting the Glacier Drop

High level overview​

This week, the Mithril team successfully integrated the Haskell DMQ node with Mithril nodes in the end-to-end tests. They continued to implement the first phase of decentralizing the configuration parameters. They also worked on some enhancements to the client library and CLI to provide access to Cardano database incremental snapshots by epoch. Additionally, they updated the signer to ensure it has a unique protocol initializer for each epoch.

Finally, the team fixed some bugs in the CI and completed the first refactoring of the STM cryptographic library that enhances its readability.

Low level overview​

• Completed the issue Enhance STM library readability - 1/2 #2568
• Completed the issue Mithril signer should have a unique protocol initializer for an epoch #2424
• Completed the issue DMQ integration tests are flaky in CI #2728
• Completed the issue Backward compatibility with latest release is broken #2730
• Worked on the issue Decentralization of configuration parameters - Phase 1 #2692
• Worked on the issue Integrate the Haskell DMQ node in the e2e test #2674
• Worked on the issue Implement a common aggregator client - Phase 1 #2640
• Worked on the issue Enhance protocol security page on website #2703
• Worked on the issue Release 2542 distribution #2727

High level summary​

• The scope for the first Consensus Leios demo has been defined and can be accessed via this link. The team has started prototyping the mini-protocols, new components and demo infrastructure, using the actual node as the base for the prototype.
• The ThreadNet tests have been updated in preparation for upcoming work on Peras tests, as well as testing that the node can fork into the next Dijkstra era (#1689).
• Most of the work integrating LSM trees into consensus has been merged into our repository (#1700, #1653, #1652, #1603, #1572). The integration of LSM trees into the node will require only minor consensus modifications, such as exposing new symbols.
• The second Peras PR has been merged (#1674). A new one is now ready for review by the Consensus team (#1678).