Status Update

May 28, 2021

Status Updates (May, 2021) > May 28, 2021


This week, the team continued adding the Catalyst voting registration feature to Ledger hardware wallets, improving UI/UX for the native asset display, implementing earned rewards history option, and, finally, removing legacy MC4, Shelley Testnet, Incentivized Testnet, and Jormungandr code.

The team also began integrating token decimal places into metadata.


This week, the team released an update for the offchain-metadata-tool to include decimals, and also worked on an upcoming update for cardano-wallet to also include decimals, and an endpoint for multi-asset wallet migration.

The team is currently working on the consolidation and streamlining of APIs for building transactions that will enable Alonzo/Plutus features.

Finally, work is still ongoing on the portfolio manager and multisig features, and the team is also busy investigating & resolving some performance issues.


This week, the team continued working on the P2P governor functionality, discovering and diagnosing PeerStateActions race conditions, fixing asynchronous transition delays, and upgrading DNS resolution to io-sim-classes.

They also worked on the handshake protocol to handle simultaneous open connections and tested FirstToFinish and LastToFinish synchronizations using an Alternative type class. Finally, the team fixed the deadlock issue in the Win32-network test.

P2P testnet updates

This week, the team completed the second milestone of the P2P deployment, delivering an engineering testnet, which allows for automatic peer selection in the network. During this stage, the team tested and implemented different user configurations, established interoperability between legacy and P2P nodes, and produced a video that reflects automated peer selection.

The team had a call with SPOs, where they explained P2P project goals, P2P system design, and the concept of hot, cold, and warm peers. They also introduced the goals of the third milestone in P2P deployment (semi-public testnet), explaining that there will be a switch in the node to enable selection of either the new P2P mode or the existing (non-P2P) one. During the semi-public testnet delivery, the team will be inviting a small group of SPOs to help test system functionality.


This week, the team tested Alonzo properties and provided Bitte support for non-AWS clusters. They also worked on Nixos configuration for the testnet with running stake pools, and improved relay and db-sync properties on a single server with isolated Nixos containers, which provides full monitoring and central logging.


This week, the team continued Alonzo benchmarking activities completing node configurations, extending traces with the necessary hashes, and improving the locli log analysis tool to enable re-capture of new traces. This week also marks the launch of the first Alonzo testnet - Alonzo Blue, which is the early alpha network that provides core Alonzo-node networking capabilities. The team is now in the process of inviting an early group of supporters to test its functionality. Over the next few months, the program will expand to include more users as the team integrates new testnet functionality and features on the way to mainnet deployment.

The team continued working on the wallet abstraction property within the transaction generator, also rebasing Alonzo-related API changes into master. They made progress implementing tracers based on the new framework and completed file-based log writer, journald backend and Prometheus exporter activities for the cardano-tracer.

Work is ongoing on the Plutus application backend (PAB), including logging output improvements and issue resolutions. The team extended the mock wallet implementation to validate transactions locally prior to their submission, and investigated how to run the PAB in-browser. They also changed the time type in TxInfo from Slot to PosixTime, made some improvements to the Game example on plutus-starter, and supported the decimal metadata field in offchain-metadata-tools and the cardano-wallet.

The team made progress on the multi-stake-keys scheme for the portfolio manager, ran final testing of the wallet migration (send all assets feature), and implemented more API endpoints for shared wallets. They worked on new transactions signing API within the PAB, removed some blocks to integrate with Marlowe Run, and fixed some errors within Marlowe Plutus contracts.

Finally, the team is now working on the refactoring of Actus contract generation and Playground redesign.


This week, the Plutus team worked on the Plutus application backend (PAB) and improved the efficiency of the crowdfunding contract. They also fixed a JSON decoding error when using the ContractModel, so that state machine property tests that use multiple contract instances per wallet will run as designed. Additionally, they kicked off a redesign of the Playground home page.

The Marlowe team implemented in-browser support for Marlowe Run, finished work on the new Marlowe website, and included a registration link for the upcoming series of webinars. They also continued work on promotional materials and documentation, and finally, they fixed a build optimization issue in the Marlowe Playground and completed a small refactoring to the simulator.