has been a busy couple of weeks for Lightcurve development teams. Among
key achievements we have the release of Lisk Core 1.1.0 to Testnet and a
new version of Lisk Hub, while crucial development has continued across
our full suite of products. Find a full rundown of what each team has
been working on below.
1.1.0 — Yesterday
we released 1.1.0 to Testnet. This release intentionally introduced a
hard fork to limit versions that are to be accepted. Full information
can be found about why we did this here.
To quickly summarise, this was caused by the following problem: release
versions containing suffixes (like ‘rc’ or ‘beta’) which were
identified as incompatible by v1.0.0-rc.* Testnet nodes. More
importantly, this hard fork will only be introduced for this release on
Testnet. Mainnet will not be effected for the 1.1.0 release as there are
no such suffixes.
With 1.1.0, the following features will be introduced:
ability to switch between networks without the need to build releases
separately for individuals ones i.e. Betanet, Testnet and Mainnet. For
us, this will mean improved test processes. This is because we will be
testing against the same builds, which will reduce the chance of
inconsistencies occurring between networks. People running from source
can also use single codebase to run multiple networks without switching
branches. Read more here, or find more details in our readme and documentation.An upgrade to Postgres 10 will introduce improved performance and increased security.Implementing consistent use of BigNumber for handling large numbers across the project.Replaced libsodium with sodium-native to use updated and secure cryptographic implementation together with improved performance.Improved performance of various HTTP API endpoints.A full list of all the issues tackled as part of v1.1.0 can be found here.
1.2.0 — Lisk Core
1.2.0 is currently in the QA phase. Once 1.1.0 is released to Mainnet,
we will be able to announce when the release to Testnet will occur.
1.2.0 will include the following changes:
An update Node.js to 8.12.0, allowing more recent features of Node.Use of DNS names instead of IPs for seed nodes.Updated HTTP API to allow filtering and sorting transactions by height.Support of many new environment variables for configuration.Many more fixes and improvements.
1.3.0 — Development
on 1.3.0 has finished, and once 1.2.0 has been released to Testnet, we
will begin the QA process. In this version, we will allow the optional
benchmarking of nodes with NewRelic. Using NewRelic will allow Node
operators greater insight in the the performance of various layers of
the application e.g. the SQL queries. For more detailed reasoning behind
this feature, please see here.
1.4.0 — We
have already begun work on 1.4.0. This development phase will stay open
for longer than 2 weeks, and will remain open for non-critical bugs
discovered as part of 1.2.0/1.3.0 releases.
1.1.0 — We continue work on 1.1, finalizing child package names on NPM, as well as pushing on with 2.0.0.
As mentioned in previous blogs, 1.1 will cover a move to a mono-repo
structure, allowing individual subpackages to be downloaded. 2.0 entails
migrating all packages to typescript, which will allow type checking,
and therefore removes the occurrence of type errors.
2.0.0 — We have released Lisk Commander 2.0 Beta. To see the full changelog for this visit here.
With this release, we have added the signature create command and the
option to create multiple accounts. Before 2.0 release candidate, we
will also add transaction validation from Elements 1.1.
1.4.0 — We
have released version 1.4 of Hub, which included a number of bug fixes,
code refactors and test improvements. A full version of the changelog
can be found here.
1.5.0 — QA,
and the associated bug fixes, continue on 1.5. This version of Hub will
allow users to bookmark Lisk accounts for future transactions. More
information on this feature can be found here.
0.4.0 — We have been working on a number of new features for Lisk Mobile, including:
Implementing biometric authentication, to allow users to login with their fingerprint or face.Added pull-to-refresh feature, making it easier for users to refresh and view the latest information.A redesign of the login page and transaction detail page.Added ‘backup your passphrase at anytime’ option to the settings page.
for keeping up with the latest developments here at Lightcurve. We look
forward to sharing with you what the next two weeks will bring in early