Status Update

Weekly Development Report

DAEDALUS

Wallet

Last week, the team finished the integration of Cardano wallet V1 API endpoints and proceeded with the post-integration cleanup of the legacy V0 API code. The introduction of the V1 API opened up the opportunity for improvements of the Cardano node connection status handling, so the team decided to completely refactor this part of the code. The code is now much more robust and should eliminate most of the "Connecting to network” issues. As a part of this refactoring, the team introduced a new "Network Status" screen which in real-time presents all the connection-related information and is very useful when it comes to understanding what is going on with the connection.

The team completed the implementation of IPC driven Cardano-node / Daedalus communication and the code is in the final testing and review phase.

As a part of the regular maintenance tasks, the team did another quarterly review of design and features implementation together with the Daedalus main designer. The review resulted in a list of around twenty minor issues which were all addressed and resolved.

App Platform

The team designed application registry interface and implemented a local registry for use in development and testing. The entry contains installation details, including download information and service permission requirements.

Application uninstallation feature was implemented.

New, container-based isolation infrastructure has been designed and implemented which significantly simplifies the design of the application platform and makes it more flexible and secure.

WALLET BACKEND

The team concentrated on front end optimization and bug fixing.

A developer worked on a task pertaining to reunifying all Wallet Layer exceptions into the pre-existing WalletError sum type as well as manually testing that the wallet layer is returning WalletError correctly via the API. Additionally, the developers removed all remaining V1 wrappers of Kernel errors, and removed all Exception instances of Kernel errors (to prevent kernel errors from being thrown directly).

Furthermore, the team worked on database migration.

Team members, continued work on hardening restoration and catch up against a variety of race conditions and related failure modes. This combines the work on wallet restoration and “backfilling” / wallet catch up. They expect one or two more days of effort at this point.

NETWORKING

On the task of Communication Protocol Design, the engineers have proposed solutions to the problem of transmitting duplicate data when running independent chain consumer protocols in both directions between two given peers. The team is in the middle of implementing this proposal after which they will engage in analyzing the outcome.

DEVOPS

There is no update this week.

CARDANO DECENTRALIZATION

The team is in the middle of re-calibrating our scope for Shelley and understanding what that means from an implementation perspective. So far they have defined and documented what the work packages are for development. They are in the process of collaborating with a number of internal departments to ascertain what other features need to be added and what the dependencies are, as this will determine what gets implemented first and what can be done in parallel.

ANNOUNCEMENTS

IOHK is currently looking for talented people to work with us as a OpenSource Manager, Performance Management Specialist, Web Tester, Director of Product Management, Rust Software Engineer, Haskell Trainer, Technical Writer, Senior Haskell Developer - Prototyping as well as several others. Please see the IOHK Careers page for more details.