October 30, 2020
Status Updates (October, 2020) > October 30, 2020
Last week, the team released Daedalus mainnet version 2.4.0. This release adds a new stake pool table view for easier pool comparison, and improves the delegation experience by featuring a saturation indicator for stake pools that shows how close a pool is to getting saturated. The release also includes tooltips for all stake pool attributes to ensure a better understanding of the key metrics, and adds a potential rewards estimation based on the amount of stake intended for delegation. The team are now preparing for the upcoming Daedalus Flight release, which will include Trezor hardware wallet support.
Last week, the node team provided the required type definitions, so Adrestia can now begin working to support multi-assets in the wallet.
Also, the team prepared for the latest Rosetta release, moved into the final stages of implementing multisig accounts, and worked on delegation support for hardware wallets.
Last week, the team continued working on the connection manager integration with the node, worked out the development building procedure on Windows, and fixed some issues within the cardano-node, iohk-monitoring, and ouroboros-network.
The team fixed ongoing issues in the handshake protocol and implemented cardano-ping applications, which are beneficial for DevOps activities. They progressed with the cardano-CLI API works by implementing typed wrappers, which expose a consistent view for the typed interface of ouroboros-consensus.
Finally, the team cooperated with the benchmarking team and the researchers from the Athens University of Economics and Business (AUEB) and Leuven University regarding the node connectivity policies and Delta-Q framework.
Last week, the team incorporated the hardware wallet support for Trezor and Ledger devices within all platforms in Daedalus installers, and resolved some relay db-sync issues occurring after the relay long-term running. They assisted the benchmarking team with large-scale deployment for performance analysis, and provided an initial packet.net support for cardano-ops to make the deployment heterogeneous across different providers. The team enabled wireguard tunnels to replace security groups for monitoring server communication with stake pool, BFT, and relay nodes.
The team also continued integrating the Catalyst mobile application with the CI for iOS and Android, made Bitte improvements to allow persistent storage for jobs - which is required for Catalyst deployment (jormungandr voting cluster) - and enhanced labeling for the logs and metrics.
Last week, the team worked on K=1000 benchmarking and reworked resource statistics reporting in the node, which allows for high-frequency and low-log-volume collection of the most relevant metrics. They completed an initial pre-production K=1000 run on Amazon Web Services (AWS), evaluated the preliminary results, and identified the metrics. The team then reworked the log analysis according to the new metrics.
The team collaborated with DevOps to deploy a large-scale packet.net benchmarking, implemented the generator for large, region-aware, toroidal benchmarking and also addressed some technical debt.
This was a busy week; more work has been done to integrate new eras with Shelley and implement changes within the consensus. The team parameterized eras over the script type, made the trace generators more efficient, and added a serialization for the Shelley genesis so the node can support a new query. Finally, they upgraded the cardano-node to GHC version 8.10.2 and continued working on the technical report.
Last week, the Plutus team spent time running Agda code in plutus-metatheory and added a Yubikey setup guide to the deployment README file. Also, they fixed some terraform warnings about string interpolation and started exploratory work on the ledger script interface.