One of the central topics at our recent Lisk.js 2021 event was the publication of the Lisk interoperability solution. Since we announced that all the research up to blockchain interoperability was completed one year ago, the main focus of the team has been on the Lisk interoperability phase of the roadmap. We take great pride in the fact that we have proposed a scalable and decentralized interoperability solution for the Lisk ecosystem.
To easily comprehend the entire interoperability solution, we organized it around 8 roadmap objectives. Each roadmap objective defines one key aspect of our interoperability solution that is addressed by one or more LIPs. For these LIPs, we distinguish between interoperability core LIPs and supporting LIPs. Some of these are already present in our Research forum and the remainder will be published in the next few weeks.
The goal of this roadmap objective is to introduce the data structures and the transactions necessary to exchange messages between chains participating in the Lisk interoperability.
This objective aims to define the lifecycle of a sidechain, starting from its connection to the Lisk ecosystem, realized by its registration on the mainchain, up to its potential termination including the recovery mechanisms from terminated chains.
The goal of this roadmap objective is to introduce a new state model and the concept of state root in the Lisk protocol.
The goal of this roadmap objective is to introduce the data structures and transactions to be used to handle tokens in the Lisk ecosystem.
Lisk-BFT is the new consensus protocol introduced as part of Lisk Core 3.0. It defines a protocol for validators to finalize blocks using two rounds of voting on blocks. In order to support the new Proof-of-Authority mechanism and cross-chain certification for interoperability, the Lisk-BFT protocol requires some modifications that are encompassed by this roadmap objective.
The block header schema was touched in several other LIPs, including the LIP State model and state root or the LIP Introduce a certificate generation mechanism. This roadmap objective aims to cover all changes to the block header schema in one place, which is achieved by the LIP New block header schema.
Currently, the SDK offers DPoS as the only validator selection mechanism by default for new blockchains. This objective aims to provide alternative mechanisms for future sidechains so that they can adapt for a wider range of use cases and applications.
This roadmap objective has two main goals. The first one is to enable compact aggregate multisignatures. Without them, the certificates contained in a cross-chain update transaction would be significantly larger. The second one is to remove any security risk of signature re-purposing and signature replays that may occur once new data structures are signed within the Lisk ecosystem.
If you watched Lisk.js 2021, then you are surely aware that the Research team’s work is far from over. With the publication of the entire amount of interoperability and supporting LIPs, the team will first focus on an improvement phase for the interoperability solution. During this phase, we will work on topics such as reducing the time for finality in the consensus mechanism or providing a sound incentivization for the role of the relayer in the interoperability solution. We will also collaborate with our colleagues in UI to ensure that the accessibility for end-users to the Lisk ecosystem is as seamless and secure as possible. In general terms, with the completion of this phase, the Lisk ecosystem will reach a higher level of future-proofness.
Looking further ahead, one of the key features to be added to the Lisk ecosystem is the capability to interoperate with other existing ecosystems. This will be the goal of the blockchain interoperability phase crystallized in the concept of Lisk bridges. Once this roadmap objective is completed, the Lisk ecosystem will not only be a solid autonomous blockchain application platform but also a universally interoperable blockchain solution.In the meantime, we encourage the entire Lisk community, and particularly those with a technical focus, to discover every detail of our interoperability solution in the Research forum and give feedback about it.
For more details click here.