Lisk Announces Alpha SDK 2.1.0

Lisk Announces Alpha SDK 2.1.0

Lisk, a blockchain tool and community provider, has released the Alpha version of its SDK (version 2.0.0). The Alpha SDK allows developers to build blockchain applications that are compatible with the Lisk Protocol. The Alpha SDK is written entirely in JavaScript for ease of access for most developers. "Lisk Announces Alpha SDK 2.1.0"

Lisk Announces Alpha SDK 2.1.0

Lisk had previously forecasted this release with a stated set of goals: implement design pattern for protocol change, improve transaction processing efficiency, create transactions element, create transaction pool element, add node/dependency/management/configuration commands. With those objectives met, Lisk released v2.0.0.

While Lisk's JavaScript and sidechain development kit approach to blockchain attempts to minimize developers' required blockchain knowledge to get started, developers need to familiarize themselves with the Lisk framework, elements, and commander. With the 2.0.0 release, a few dependencies exist (i.e. NodeJS v10.15.3, PostgreSQL 10+, Redis 5+, and Python 2). Visit the SDK docs on GitHub to learn more.

Lisk has published a number of guides to help developers get started. The building blockchain applications guide describes how to create a blockchain application with the Lisk platform. In addition, Lisk's example applications give developers an idea of what can be built.

What is Alpha SDK?

The goal of the Lisk SDK (Software Development Kit) is to provide developers with a set of tools and libraries that will make the process of creation and customization of blockchain applications quick and easy.

The architecture of the Alpha SDK

The architecture of the Lisk SDK is designed in a way that can be extended to fit a wide variety of blockchain application use-cases. There have been a few minor changes made to the initial proposal:

The originally proposed system component, responsible for maintaining application state, was implemented as part of the application controller. This was done in order to eliminate the risk of having an inconsistent application state distributed across different modules within the application.

We introduced a new concept of public versus private actions. Public actions, like remote procedure calls, are allowed from other machines on the Lisk Network, but certain actions are restricted to the local machine only. This provided a greater level of security than what was originally proposed.

Post a Comment