Hi Liskers,

The holidays are fast approaching — that doesn’t stop Lightcurve development teams from making headway across our suite of our products. We have released Lisk Core 1.3.1, Elements 2.0.0 and Hub 1.7.0. Check out the full rundown below.

Lisk Core

1.3.1 was released on December 5 in order to implement a security update from Node.js to v8.14.0 and SocketCluster to v14.3.3. Remaining node operators should upgrade if they haven’t already.

1.4.0’s development is finished, and the QA Phase has begun. This release fulfills the last objective from the current Lisk Network Roadmap phase, “Quality & Performance”, and moves the build system directly into Lisk Core. It also tackles a large chunk of the backlog and closes 44 issues.

1.5.0 will contain the first batch of changes from the next roadmap phase, “Architecture & Design.” Work on this phase has already begun, and the first pull request setting the fundamentals of the new Extensible Database Layer has been merged. It contains the basic structure of the database layer, and also contains a reference implementation of CRUD operations for the Account entity. This introduces new BaseEntity class which contains common methods available to entities that are extending it. The BaseEntity class also contains the blueprint of the methods that the subclass is required to implement hence acting as an interface. Another concept introduced by this pull request was Adapters which will allow to easily change the database solution if required.

For now, the initial work on the Extensible Database Layer will be done on a separate feature branch. It will be merged back to development after all of the new Database Entities will be implemented and securely replaced within the existing codebase.

Lisk Elements

2.0.0 was released on December 3. This release brings with it an upgrade to Node.js v8, bringing Elements in line with Core. It also includes the addition of Sodium Native support for faster performance for cryptography-related functionalities. Benchmarks on sodium-native vs. TweetNaCl can be found in our documentation.

2.1.0 is currently in development. As part of the “Improve transaction processing efficiency” roadmap objective, work on the transaction pool continued at a good pace, with a number of important issues being closed for this milestone.

Work on the “Introduce robust peer selection and banning mechanism” objective continued with all the main methods which will be exported to the peer-to-peer library being declared, along with all relevant TypeScriptdefinitions. The basic scaffolding for the peer-to-peer library’s test suite has been set up.

Lisk Commander

2.1.0’s major change, namely the migration of Lisk Commander to TypeScript, is expected to finish next week. Moreover, improvements have been made to the ‘transaction:get’ command, which includes pulling transactions by state unprocessed or unsigned and senderId. We have also created a new command to get all the voters for a delegate by typing ‘delegate:voters’. In addition, extra filtering functionality has been made to both of these commands.

Lisk Hub

1.7.0 was released on December 12. This release brings a number of updates to the overall look, noticeably the background has been changed to a lighter gray, with other elements adjusted to match. In addition, we have added a feedback button to the sidebar — you can now help steer the direction of Hub’s development directly from within the app!

Lisk Mobile

0.7.0 is currently awaiting approval in the App and Google stores and should be released shortly. This release brings with it a redesigned home page, a bookmark page, links to other accounts’ overviews when clicking on the address, UI improvements for smaller screens, and a progress bar on the send page.

This is the last LiskDevUpdate for 2018. We’ll be back on January 17 and can’t wait to share with you all the exciting developments 2019 will bring.

The Lisk Team