Status Update

Weekly Development Report

CSL CORE

SCRAPE integration -Ready to be merged. At this point only minor tweaks need to be made.

Delegation/stake locking -Address type modification (having stake distribution as part of it) is merged. The team expects to have a working prototype by midweek and have everything merged by the end of the week.

Test stake locking Although great progress has been made, manual testing has been postponed.

Automated testing -The week was dedicated to making sure that testing reliability is high. Also, a lot of bug fixing, previously discovered by testing, has been accomplished. -Due to a lot of high priority issues, Work on testing invalid payloads (txs) has not yet began.

DAEDALUS

The work on theming support was finished and 3 themes were polished with small inconsistencies with the design specs fixed. In the scope of the theming support, all vector graphics were refactored to SVG format to support coloring of monochrome icons programmatically which enables support for a larger variety of themes.

TLS issue in communication with backend was fixed which was a major blocker for the continuation of testing and QA of the new backend code from the master branch.

UI for exporting wallets to a file was completed and will be integrated with the backend when the endpoint is ready in the next sprint.

Other than the abovementioned points, smaller issues were detected and fixed an test coverage was improved.

MIDDLEWARE

During this sprint, the team accomplished a lot of long overdue tasks, such as refactoring of the middleware code as well as finishing some important features such as transaction fees.

Unfortunately not much progress was made with issues such as testing tx creation logic or profiling wallet sync logic, due to critical core issues that took priority.

EXPLORER

This week the team has finally put the Timestamp reimplementation into review.

BENCHMARKING

Here are the latest developments from the Benchmarking team:

There were some hiccups with deploying the staging cluster with the new networking mechanism. The team worked with Devops to resolve them, and written proper documentation of how to set up a cluster with the new setup of core, relay, and edge nodes.

Unfortunately, with the changes, recovery mode (i.e., a node that has been offline for some time or otherwise unable to communicate with the rest of the network trying to catch up with the network) broke, due to a misunderstanding of how the implementation of recovery works. This has now been fixed.

DEVOPS

• setup new macOS/Linux slaves for CI and document it's setup
• plugin the new stack2nix CI and fix problems with macOS
• deployed staging using the new core/relay split
• shutdown TN 0.3

Current WIP:

• DNS round-robin for relays (Domen)
• 3 hosting accounts
• Ops
• automated benchmarks

MAJOR GOAL ASSESSMENTS

Testnet 5 release

The last two weeks have seen a bit of an increase in tickets, due to the issue with block syncing. A sum of 18 support tickets have been created.

The top most reported issues were:

-Issue with block sync: 10 tickets -Cannot connect: 3 tickets -Issue with redemption: 2 tickets -Cannot install: 1 ticket -Question about Daedalus: 1 ticket -Question about mainnet release: 1 ticket

Mainnet Release

We are currently in the process of planning a all-hands meeting, for a new timeline for launch. However, due the te delegation code freeze only happening by the end of this week, those dates might slightly fluctuate.