Status Update

DAEDALUS

The Daedalus team worked on 2.2.0-FC1 and upcoming 2.2.0 wallet releases. They made some staking and delegation improvements, integrated hard wallets, fixed acceptance tests, and finally, made Cardano Explorer adjustments.

ADRESTIA

Last week the Adrestia team worked on wallet improvements for our partner exchanges. Also, the team is working on a new release that will resolve some outstanding technical debt incurred following the Shelley sprint.

This week the Adrestia team has continued working on the Cardano implementation of the Rosetta framework. This included setting up nodes, validating the chain, and constructing transactions. The important first stage has been passed, and the next step will be to move the cardano-rosetta repo to public for testing on the Coinbase side. Internal tests did not show any issues, but cardano-rosetta is still undergoing rigorous testing to prepare it for custody integration. Working closely with the Coinbase team, we’ll next be extending the Rosetta framework to include stake delegation capability.

NETWORKING

Last week the team continued work on the integration of the peer-to-peer governor with the cardano-node and a connection manager to handle bi-directional communications.

DEVOPS

Last week the team fixed bugs and made improvements to cardano-ops code and DevOps network tools. They also worked on Bitte, a new DevOps toolset. Bitte facilitates the deployment, management, and performance testing of large, scalable, and distributed workloads and services in the cloud. The team also released 1.19.0 version of the node and Daedalus FC.

CARDANO DECENTRALIZATION

Last week the team improved property tests to reflect more epochs and worked on a pool ranking documentation covering the ledger testing details.

GOGUEN

Last week the Plutus team made an update to the control continuation environment (CEK) machine to ensure that thread environments are routed through the machine. They also refactored a built-in application in the CEK machine itself, which makes the structure of the machine clearer and corresponds more closely to its specification. Also, the team spent time simplifying contracts and fixing issues with Websockets.

The Marlowe team were busy adding web-ghc integration to the Playground infrastructure and resolving some Marlowe frontend compiler warning errors.