Status Update

DAEDALUS　

This week, the team resumed working on the Electron upgrade, maintaining the application window size and its position after the Daedalus relaunch. They investigated issues related to the detailed earned rewards history feature, and finalized the implementation of a warning notification when making transactions with not enough funds to redeem rewards or move native tokens in the wallet.

ADRESTIA

This week, the team made good progress in Alonzo/Plutus-related changes.

Specifically, they released GraphQL v5.0, Rosetta v1.3.0, and Explorer-app v1.6.0. The team is also preparing to release a wallet update to enable compatibility with Alonzo Node 1.28, and they are working on streamlining cardano-wallet transaction APIs to enable Plutus Application Backend (PAB) integration.

Finally, they are working on several changes required for smart contracts (collateral, script witnesses, etc.)

NETWORKING

This week, the team worked on property tests and adjusted the ConnectionManager test, which resulted in the discovery and resolution of some issues.

The team also restructured the P2P to non-P2P switch for better clarity and easier maintenance of the data diffusion API. The data diffusion module now works in an abstract monad that allows building simulations in io-sim.

DEVOPS　

This week, the team updated the Explorer-app to v1.6.0 and continued preparing for Alonzo White v1.3.

CARDANO DECENTRALIZATION

This week, the team worked on Alonzo block time budgeting calibration benchmarking. They discussed and implemented the calibration data export format, extended the block propagation analysis to perform final data validation, and delivered the final 64kb block size results.

Work is ongoing on Alonzo Plutus payload benchmarking; the team integrated the script-based transaction generator into the workbench and continued implementing the initial Plutus capacity transaction generator.

Finally, the team completed work on the trace-dispatcher and cardano-tracer components’ features, and continued testing and updating documentation.

GOGUEN

This week, the Plutus team added rollback support, updated protocol parameters in the plutus-use-cases-scripts, and made more changes that allow running scripts during the Hydra process. They also provided more documentation for the Plutus Application Backend (PAB), and steps in the README for a Cabal update.

The Marlowe team worked on a new implementation of the Balance tab within the Marlowe Run client, worked on some adjustments to the ACTUS test framework, and made updates to the timezone and timeout features. These ensure that the displayed time is offset with the browser, and the contract timeout is applied correctly, rather than using the current slot at the moment of calculation.