Status Update

October 23, 2020

Status Updates (October, 2020) > October 23, 2020


Last week, the team prepared for the release of Daedalus mainnet 2.4.0. It includes improvements such as re-enabled stake pool saturation details, table view on the “stake pools” display, potential rewards details within the “stake pool” tooltip, and updated ranking display based on non-myopic member rewards.

The team have reached the final stages of Trezor hardware wallets integration, which is now in testing and review phase. Finally, they are working on adding support for Ledger devices.


Last week, the Adrestia team's efforts were focused on hardware wallet support, Catalyst, and multi-assets.

They added delegation support for hardware wallet, started work on extending Cardano-rosetta for delegations, and completed flexible SMASH server selection.

It was a busy week for Adrestia, as they also accomplished nightly benchmarks of server in the context of multi-account done, and have almost completed a configurable time-to-live for transaction and automatic re-scheduling of failed transactions. The team has also made good progress on the creation of script addresses via the API and soft derivation via the API.

Finally, the team completed work on signing arbitrary data with stake key for Catalyst, and are now working on pre-testing valid SMASH server URL.


Last week, the team worked with mini-protocols for nodes communication, focusing on refactoring the handshake negotiation. They also continued integrating the connection-manager with a node, and improving the cardano-API.

The team have presented simulation results to the Athens University of Economics and Business (AUEB) for various simple policies regarding the choice of upstream peers by the node. This will allow AUEB to design their simulation about the inclusion of cold, warm, and hot peers.


Last week, the team worked on the scripts for Project Catalyst to generate vote registrations from a stake key in cardano-CLI, and scripts to query db-sync to fetch these registrations. They also ran initial testing of the voting workflow for Fund2 and worked on iOS and Android voting applications.

The team improved Bitte deployment tooling to allow running multiple unrelated node clusters on the same nomad cluster, and deployed Catalyst jormungandr cluster for the Fund2 voting. Finally, they provided Nix assistance with Glasgow Haskell Compiler (GHC) 8.10 update for the node and implemented Daedalus hardware wallet support for Trezor devices.


Last week, the team worked on the technical report for the consensus layer functionality. More work has been done on the integration of new eras with the consensus, which requires additional changes in the ledger for finalization. The team is now testing Shelley hard-forking, implementing some refactoring to simplify this process, and also rewriting ThreadNet tests.

In terms of multi-asset functionality, the team merged multiple property tests and worked on their generalization. They rearranged era parametrization to fix an issue with the consensus integration and deployed a framework for transaction generalization, which allows new era transactions to use the timelock scripts. Finally, the team worked on the parameters to enhance stake pool ranking, and prepared a pull request that will synchronize documentation (delegation design, formal specification, and ranking specification) with non-myopic calculations.


Last week, the Plutus team made some initial changes to the metadata batch query structure in the smart contract backend (SCB). They also updated a number of scripts that are involved in validations that occur during the plutus-use-cases tests, together with some benchmarks for timing the validation process. Additionally, they updated the batch query endpoint convention from GET requests to use POST requests to improve usability.

The Marlowe team concentrated on updates to Blockly regarding the use of account numbers. They also made changes to the Option contract example in the Marlowe Playground to make it more realistic. The technical writing team worked on new explainer materials for Marlowe, which will be published soon.