Skip to main content

· 2 min read
Sebastian Nagel

High-level summary​

This week, the Hydra team worked on several fronts, including fixing state machine continuity on-chain, discussing voting project solutions, exploring adding Hydra support to kupo, and improving API navigation with a sidebar. The team also updated dependencies and fixed issues in their test suites. Moving forward, the team plans to hold the next monthly review meeting, address a user issue, prepare for the 0.10.0 release, and work on a dirt road fix for the rollbacks issue with proper test coverage.

What did the team achieve this week​

  • Fixed scripts to enforce state machine continuity on-chain #777.
  • Took part in a twitter space on “Scaling Cardano”.
  • Joined a CBIA meeting to discuss Cardano network protocols & how to specify them.
  • Discussed potential solutions of ensuring vote uniqueness in the voting project.
  • Updated dependencies to match cardano-node master to prepare for upcoming releases and hard-forks
  • Explored adding Hydra support to kupo, a lightweight Cardano chain indexer - some more work required.
  • Improved navigation of the API Reference with a sidebar, see unstable API version.
  • Fixed two things in our test suites (random port conflicts and an arithmetic underflow in smoke test)

What are the goals of next week​

  • Monthly review meeting (join via Discord or AddEvent) & report
  • Dirt road fix for rollbacks #784 properly covered by a test.
  • Groom and ideally address user issue #823.
  • Put the spec into the repo #693 and prepare release 0.10.0.

· One min read
Jared Corduan

High level summary​

We continued to make progress on CIP-1694 and the conway ledger era. In particular, the conway era now supports Plutus V3. Finally, we made small improvements to the ledger API and now host our Haskell code documentation (haddocks) on github pages.

Low level summary​

Conway ledger era​

Haddocks hosted on github pages​

Small improvements to the API​

Technical Debt​

  • [pull-3367] Fix cost model json instances.
  • [pull-3371] UMap cleanup.
  • [pull-3373] Upgrade to ghc 9.2.7 and cabal 3.10.1.
  • [pull-3375] Sadly, we had to revert the TICKF optimizations. There was a regression we do not yet understand.
  • [pull-3377] Fix cabal warnings.
  • [pull-3383] Fix multi-asset test.

· 2 min read
Jean-Philippe Raynaud

High level overview​

The Mithril team released a new 2315.0 distribution that implements the first part of the migration of the aggregator stores along with minor improvements and bug fixes. They finished the migration of the aggregator stores to a relational design by completing the adaptation and migration of the signed entity, signer and single signature stores. They also created a new tick service that provides beacons to other services of the aggregator. Additionally, they started implementing the new new certifier service of the aggregator that is in charge of producing certificates for multi-signatures.

Finally, they completed the design and definition of the interfaces that must be implemented to provide certification for a new type of data in a Mithril network.

Low level overview​

  • Released the new distribution 2315.0
  • Completed the epic that implements a relational store in the aggregator #779:
    • Completed the migration/adaptation of the signed_entity table #816
    • Completed the creation of the signer table #814
    • Completed the migration/adaptation of the single_signature table #829
  • Worked on the epic that designs and implement generic signing/verification of entity services #780:
    • Completed the definition of the interface of the generic entity service for signing #847
    • Worked on the implementation of the Certifier service in the aggregator #850
    • Completed the extension of the SignedEntityType type #848
    • Completed the implementation of the Tick service in the aggregator #849
    • Worked on implementing the signable builder for the Mithril Stake Distribution #851

· One min read
Jordan Millar

2023-04-20 - 2023-05-04

High level summary​

  • Various fixes and improvements

docs​

CI & project maintenance​

Developer experience​

cardano-cli​

cardano-api​

cardano-node​

cardano-testnet​

· One min read
Damian Nadales

High level summary​

This week the consensus team continued working on the improved DB lock mechanism for UTxO-HD, and modifications to the mempool benchmarks that this prototype requires.

On the Genesis front we validated that the fragment size calculation in BlockFetch is a major performance sink for ChainSync Jumping. By removing it we will get performance that is acceptably close to that of the baseline. We also started investigating a performance fix that does not alter the existing baseline behavior too much. In addition we reviewed our Genesis attack vector calculations.

On the support front we released Consensus 0.4, and we are working on improving our release process, to support the Cardano-wide efforts in this area. We also performed an analysis on the number of file descriptors that consensus use. This information can be used by the node operators to check if the number of file descriptors they want to support are enough.