High level overview​

This week, the Mithril team released the new CIP-137 - Decentralized message queue, which will be used to diffuse Mithril signatures in the future.

The team also implemented usage metrics with a Prometheus endpoint and published the Grafana dashboard for the aggregator. They have respun the testing-sanchonet environment with Cardano node v.10.1 and worked on some refactoring to remove legacy code and make it more readable and maintainable. The team also started exploring solutions for signer registration when multiple aggregators are running on a Mithril network.

Finally, they fixed some flakiness in CI end-to-end tests and made the Cardano stake distribution stable in the client.

Low level overview​

• Published the Mithril aggregator Grafana dashboard
• Completed the issue CIP for Mithril signature diffusion through Cardano network #1775
• Completed the issue Release 2442 distribution #1943
• Completed the issue Create Grafana dashboard for aggregator #2001
• Completed the issue Refactor ChainPoint conversion from pallas Point #2037
• Completed the issue Flakiness in e2e tests in CI #2044
• Completed the issue Remove beacon field in certificate #1958
• Completed the issue Make Cardano stake distribution stable in client #2024
• Completed the issue Add missing successful restoration cardano db in prometheus aggregator #2054
• Completed the issue Upgrade testing-sanchonet for respin with Cardano 10.1.0 #2045
• Worked on the issue Explore Signer Registration Solutions #2029
• Worked on the issue Record aggregator metrics in event store #2023
• Worked on the issue Refactor protocol parameters namings in signer/aggregator #1966
• Worked on the issue Docker nightly builds in GitHub Actions #2026
• Worked on the issue Nightly backward compatibility testing with e2e tests #2027
• Worked on the issue Access registered signers for latest epoch in explorer #1689
• Worked on the issue Remove pending certificate from explorer #2025

Overview of sprint 73​

Ouroboros-Network-0.18 release​

We released ouroboros-network-0.18. The main features are:

• integration with typed-protocols-0.3
• cardano-client library doesn't depend on the non-p2p stack
• We expose connectToWithMux family of function in ouroboros-network which give access to the underlying Mux handle.
• Added NodeToClientV_19: to support new GetLedgerPeerSnapshot query in local-state-query mini-protocol ouroboros-consensus#1067.

See full the list of PRs included in this release. ouroboros-network-0.18 was integrated with ouroboros-consensus (ouroboros-consensus#1223)

Tx-Submission​

We continued working on tx-submission monitoring its performance.

Ouroboros-Network - Mithril Design​

We had an internal discussion how to support the Mithril design. In near future we will be able to socialise the report we've been working on.

Code Refactoring​

We reorganised some of our substysems to use qualified imports with simplified names:

• ouroboros-network#4990 (connection-manager, inbound-governor)
• ouroboros-network#4997 (network-mux)

We also removed deprecated APIs in [ouroboros-network#4998]

High level summary​

Final changes for the next Hard Fork to protocol version 10.0:

• Ensure that it is still possible to unregister the reward account and withdraw the funds in the same transaction
• Fix a bug in recently introduced feature, which ensures DRep existence for all stake credential delegations.

More Conway testing and continued progress on conformance tests.

Low level summary​

Features​

• pull-4684 - Revert Mismatch-related changes of ShelleyPoolPredFailure serialization
• pull-4661 - Add GovRemovedVotes event
• pull-4697 - Minor fixups from internal audit
• pull-4709 - Fix drep delegation invariant preservation
• pull-4715 - Adjust semantics of ConwayWdrlNotDelegatedToDRep

Testing​

• pull-4683 - constrained-generators: Improve some error messages
• pull-4689 - Set maxTxSize relative to generated tx in Utxo conformance tests
• pull-4680 - constrained-generators: More tests for append and singleton
• pull-4665 - Remove the proposals workaround from UTXO conformance, add LEDGER conformance
• pull-4705 - Implement some of the tests in Alonzo.Imp.UtxowSpec.Valid
• pull-4707 - Add imp tests for drep delegation
• pull-4677 - Added example Tx specification

Infrastructure and releasing​

• pull-4681 - Update CHANGELOG files following release for 10.0
• pull-4686 - Bump up version in cardano-ledger-shelley changelog
• pull-4688 - Add nix develop to main README.md
• pull-4701 - Ensure repo is buildable on Windows
• pull-4656 - Align with Governance audit
• pull-4706 - Add changelog section for cardano-node-10.0 and 9.2.1
• pull-4710 - Cardano ledger conway 1.17.1.0
• pull-4716 - Release/cardano ledger conway 1.17.2.0

High level overview​

This week, the Mithril team released the new distribution 2442.0. This release offers stable support for decentralized signature orchestration in both the signer and aggregator, the Cardano transaction client library, CLI and WASM, and the Pythagoras Mithril era. It also includes bug fixes and performance improvements.

The team also continued implementing usage metrics with a Prometheus endpoint and a Grafana dashboard for the aggregator. Additionally, they completed preparing the Pythagoras Mithril era and refactoring the node logs to improve their readability.

Finally, they kept implementing optimizations in the CI and updated the decentralized message queue CIP pull request, which has been granted the CIP number CIP-0137.

Low level overview​

• Released the new distribution 2442.0
• Published a dev blog post about the Certification of Cardano stake distribution
• Completed the issue Enhance readability of node logs #1981
• Completed the issue Prepare new Pythagoras Mithril era #1946
• Completed the issue Expose Prometheus metrics for aggregator #1980
• Completed the issue Deprecate macOS 12 builders in CI #2016
• Completed the issue Fix Cardano transaction chunk importer #2021
• Completed the issue Deprecate macOS 12 builders in CI #2016
• Completed the issue Fix warning log when building OpenAPI UI in CI #2017
• Completed the issue Update workflow github actions to node 20 #2018
• Completed the issue release-preprod aggregator is unavailable #2036
• Worked on the issue Release 2442 distribution #1943
• Worked on the issue Create Grafana dashboard for aggregator #2001
• Worked on the issue Record aggregator metrics in event store #2023
• Worked on the issue Refactor ChainPoint conversion from pallas Point #2037
• Worked on the issue CIP for Mithril signature diffusion through Cardano network #1775

High level summary​

• Benchmarking: Started release benchmarks for Node 10.0.
• Development: Governance action workload - alternative tx submission method built, passes tests.
• Tracing: Preparing the bump to typed-protocols-0.3.

Low level overview​

Benchmarking​

We've started the benchmarking process for the freshly tagged, fully Chang 2 capable Node version 10.0 pre-release.

Development​

Calibrating a governance action / voting workload within our submission service tx-generator is more involved than anticipated.

As measurements for performance impact of voting are required very shortly, we have - in parallel - created a nix / bash based solution. That one uses cardano-cli for creating and submitting proposals and voting transactions, while the generator can run any other known workload simultaneously. Thus, we expect to get a clear performance delta between voting vs. no voting going on. This setup has already been deployed, and is passing testing - soon to be used for the first real-world voting benchmarks.

The implementation however is less flexible, much less parametrizable, and in its design tied to the very specific, fixed topology of the Nomad cluster. The workload definition inside tx-generator will thus continue, and eventually be used as the standard for benchmarks targeting voting / governance.

Tracing​

The new tracing system, more specifically, the components that forward metrics and traces to cardano-tracer, contain well-defined peers in the sense of the typed-protocols package. The upcoming bump to recently released version 0.3 contains breaking changes in the package API. We've begun necessary downstream adjustments in our packages, re-defining aforementioned peers using the new API.