This blog post is designed to provide a brief overview of the next steps for the Lisk Platform and UI teams. To achieve the continual ongoing development of the Lisk products the key steps are taken in chronological order and are as follows: Research, Requirement Gathering and Planning, Implementation, and finally the Quality Assurance.
Our efforts in the continued Lisk development are currently two-fold. Firstly to successfully launch the Lisk Testnet v3 followed by the Lisk Mainnet v3, as well as simultaneously begin the immediate implementation of the Lisk interoperability solution.
The last stepping stone towards a successful Lisk Testnet v3 launch is Lisk Desktop v2.0.0-rc.0, currently scheduled for July. All other required products (Lisk Service v0.3.0, Lisk SDK v5.0.0, Lisk Core v3.0.0, and Lisk Migrator v1.0.0-rc.0), were already successfully released. With that we are looking at the Lisk Testnet v3 launch this summer, closely followed by the Lisk Mainnet v3 launch this fall. Naturally, these are estimations and may be subject to some changes in the course of development.
Taking all of that into consideration, we are now directing our main resources towards focusing on the implementation of the Lisk interoperability solution, likely to occur in Lisk SDK v6.0.0.
Next Steps for the Lisk Platform Team
The Lisk platform team is responsible for our backend products, namely Lisk Core and Lisk SDK. With the release of Lisk SDK v5.0.0 and the consequent readiness of Lisk Core v3.0.0-rc.0, all the platform requirements for the Lisk Testnet v3 launch have been completed, therefore the full focus is now on implementing the Lisk interoperability solution.
To start the process we will begin with the implementation of the first five supporting LIPs listed below:
- Add BLS signatures.
- Add sparse Merkle trees.
- Use message tags and network identifiers for signatures.
- Add weighted Lisk-BFT consensus.
- Add a Proof-of-Authority validator selection mechanism.
The knowledge sharing and developer peer reviews of these LIPs have been completed, and we are now beginning the planning process. Furthermore, to prepare the Lisk SDK for the Lisk interoperability solution it is necessary to improve it further in other aspects as well. To know which aspects, we have already started competitor analyses with the following objectives:
- Compare libp2p with lisk-p2p.
- Compare state store implementation and framework hooks.
- Compare block forging modularization.
Next Steps for the Lisk UI Team
The Lisk UI team is responsible for our frontend focused products which consist of Lisk Desktop, Lisk Mobile, and Lisk Service. With the release of Lisk Service v0.3.0, the only requirement outstanding for the Lisk Testnet v3 launch is the release of Lisk Desktop v2.0.0-rc.0. This is where the full focus is now being applied, and it is scheduled within the next few weeks.
While Lisk Desktop is in the release candidate (RC) stage and the Lisk Testnet v3 is launched, the main focus will then be on fixing various bugs and visual defects, in order to provide a quality product for the Lisk Mainnet v3 launch.
After the Lisk Mainnet v3 is launched, the next steps for the Lisk UI team will be on completing the already planned objectives for Lisk Desktop to complete full compatibility with all new Lisk Mainnet v3 features as listed below:
- Adapt hardware wallet integration for Trezor and Ledger.
- Add proof of misbehavior transaction support.
- Add delegate failsafe banning mechanism support
- Add multi-signature transaction pool support.
- Add multi-signature transaction notifications.
- Implement account history export.
As well as to update Lisk Mobile to support the latest API for the Lisk Mainnet v3.
Finally, to summarize here, we are getting very close to meeting all requirements for both the Testnet and Mainnet launch to happen, therefore the spotlight is now on implementing our Lisk interoperability solution.