Skip to main content

Mithril Team Update

· 2 min read
Jean-Philippe Raynaud
Jean-Philippe Raynaud
Mithril Tech Lead

High level overview​

This week, the Mithril team completed benchmarks for the IVC SNARK recursive circuit and analyzed and optimized the testing strategy for the STM SNARK modules. They also worked on encoding the aggregate signature of the certificate message as bytes, which significantly reduces the size of the certificates.

The team also continued implementing the aggregator CLI commands and the runbook for on-chain configuration parameters, and began creating a local IPFS network for a proof-of-concept distribution of Cardano database artifacts.

Finally, they completed the repository transfer to the IntersectMBO organization. They also continued working on shipping the Mithril signer node binary in the Cardano node bundle, preparing the 2630 distribution release, upgrading to Cardano node v.11.1, updating the DMQ node to 0.7.0.0, and upgrading the documentation website to Docusaurus 3.10.2 and tailwind v4.

Low level overview​

Features​

  • Completed the issue Add benchmarks for the IVC SNARK recursive circuit #3412
  • Completed the issue Analyze and optimize the testing strategy of the STM SNARK modules #3405
  • Worked on the issue Use bytes encoding for aggregate signature in certificate message #3379
  • Worked on the issue Implement aggregator CLI commands for configuration parameters #3392
  • Worked on the issue Create a local IPFS network #3434

Protocol maintenance​

  • Completed the issue Transfer repository to IntersectMBO organization #3276
  • Worked on the issue Ship Mithril signer node binary in Cardano node bundle in GitHub #3011
  • Worked on the issue Release 2630 distribution #3271
  • Worked on the issue Upgrade to Cardano 11.1 #3346
  • Worked on the issue Update DMQ node to 0.7.0.0 #3358
  • Worked on the issue Create runbook for on-chain configuration parameters #3399
  • Worked on the issue Update documentation website to docusaurus stable version 3.10.2 #3413
  • Worked on the issue Update documentation website to tailwind v4 #3414