June 4, 2021
Status Updates (June, 2021) > June 4, 2021
This week, the team released Daedalus Mainnet 4.1.0, which enables configuration settings for decimals in native tokens with recommended values fetched from the Cardano token registry. This version also includes overall improvements, resolves some known issues, and enables Catalyst Fund4 voting registration.
This week, the team released an update for cardano-wallet to include support for decimals, and enable the multi-asset wallet migration endpoint.
They are currently working on the consolidation and streamlining of APIs for building transactions that will enable Alonzo/Plutus features, and have also started implementing changes needed for cardano-wallet to support v1.27 of the cardano-node.
The team have also completed a proof-of-concept part of the portfolio manager and the first phase of the multisig functionality implementation.
Finally, they implemented changes in cardano-graphql to support decimals and designed a proposal for the Plutus metadata server.
This week, the team worked on a P2P and non-P2P diffusion API, fixed some issues, and worked on server tests and scheduling within io-sim.
The team fixed the stateTVar signature, worked on simultaneous TCP connections opened by the handshake protocol, and rebased p2p-master branches.
Finally, they enhanced the connection shutdown feature using the connection manager and fixed issues found in PeerStateActions and systemd socket activation.
This week, the team prepared for the Alonzo Blue hard fork event, tested ERC20 multisig documentation, and performed Catalyst dry runs in preparation for Fund4.
Finally, they worked on Nixos sample configuration for the testnet stake pool on a single server.
This week, the team continued working on Alonzo benchmarking. They discovered the need for another trace in the block fetch client node, implemented it, completed block event recovery, and computed per-block propagation CDFs. The team then ran the initial calibration setup on AWS.
They continued redesigning the node logging infrastructure, reimplemented all tracers within the trace-dispatcher using the new framework, and started writing tests for the cardano-tracer. The team initiated an integration between trace-dispatcher and cardano-tracer and created a new tracing-master branch, which now carries the entire rewrite results for developers.
The team also improved logging in the Hydra node prototype, created an open-source repository for it, and examined prototype use cases designing its user journey.
Finally, work is ongoing within the transaction generator: the team continued working on the wallet abstraction and completed error handling for Marlowe and Plutus contracts.
This week, the Plutus team started investigating how to add API error handling to the chain index endpoints. They also switched the Plutus Playground simulations to higher lovelace values to accommodate the change in the higher fee calculation. Additionally, they added an equalsString and Eq instances to Plutus Core, made performance improvements to the JSON parsing, and applied a fix for a missing depth increment in LetFloat. Progress was also made on changing
plutus-use-cases and other projects from
POSIXTime and improvements to the Plutus Application Backend (PAB) test stability and simplified PAB package dependencies.
The Marlowe team implemented in-browser support for Marlowe Run and continued system QA testing and bug-fixing activities. They also prepared for the first Marlowe webinar, integrated ACTUS testing, and started working on ANN (Annuity) ACTUS contracts. Finally, work is ongoing on the Playground redesign.