Status Update

DAEDALUS　

This week, the team assessed the new cardano-node v.1.33 functionality running compatibility tests and benchmarks. They are now preparing for the next Flight release, which will include the new cardano-wallet and cardano-node. Finally, the team continued working on the light wallet proof of concept and SDK integration.

ADRESTIA

This week, the team released new versions of cardano-wallet and cardano-launcher, both compatible with node v.1.33. They're currently working on updating cardano-rosetta and cardano-graphql to enable the same compatibility.

The team also prepared an update for offchain-metadata-tools to allow registering metadata for native assets with tickers longer than 5 symbols.

Finally, the team continued working on performance improvements and technical debt in cardano-wallet, and designing the cardano-js-sdk MVP.

NETWORKING

This week, the team continued working on P2P functionality, examining and resolving issues related to connection manager implementation. They worked on the keep-alive protocol’s restart issue and started investigating its peer state actions. Finally, the team continued testing the timeouts and worked on a feature that avoids peer ordering based on their IP number and port.

DEVOPS　

This week, the team improved Plutus Pioneers’ bootstrapping experience with Nix, which gets the Playground up using a single command locally.

CARDANO DECENTRALIZATION

This week, the team finalized ledger DB reorganization (required to run in-memory and hybrid databases) and are now in the process of its performance assessment.

Work is ongoing on scalability enhancements. The team finalised the preliminary implementation plan for block difussion pipelining using delayed validation.

The team commenced the parameter update proposal process to increase Plutus script memory units per transaction on the Cardano mainnet by 1.25M. This initial change will take effect at the boundary of epoch 317 on the 25th of January. This upgrade will provide increased resources for Plutus scripts and the DApps utilizing them. Once deployed, the teams will be monitoring carefully over at least one epoch (5 days) to determine the next increment.

The Hydra team estimated the costs of Hydra Plutus scripts, continued work on adding script validators to the Head protocol transactions, and are preparing a public Hydra implementation roadmap to be released soon. Finally, the team are now working on a new blog post about Hydra Heads and their role in the Hydra family of protocols.

GOGUEN

This week, the Plutus team released an updated version of the Plutus Application Backend (PAB). It includes multiple fixes and enhancements; in particular some refactorings of the PSGenerator, which aim to reduce the dependency load, a fix to minimum fee calculations, and they also updated documentation about the PAB deployment and wallet scenarios.

The Marlowe team upgraded the marlowe-cardano repository to the latest tagged plutus-apps, added drag-and-drop support for reordering templates, and removed the ‘Connect wallet’ feature from contacts. They also worked on the integration of Marlowe Run with the PAB and wallet to reliably create properly balanced transactions and made some improvements and additional tests for the marlowe-cli. Finally, they worked on new ACTUS contract types, scoped for next product releases, and are planning the Marlowe Pioneer program.