Friday, December 14, 2018

Development Update — November 1, 2018

Development Update — November 1, 2018

Hi Liskers,

As usual, it’s been a busy couple of weeks for Lightcurve Development teams. Among key achievements, we have the release of Lisk Core 1.1.1 to Mainnet, a new version of Hub 1.5.0 and Mobile 0.4.0. Check out the full rundown below.

Lisk Core

1.1.0 — With 1.1.0 released on Mainnet, node operators can now switch easily between networks without the need of rebuilding, as well as other improvements, such as an upgrade to Postgres 10, consistent usage of Bignumer.js. Full details of 1.1.0 are available in the previous blog.

1.1.1 — This patch was released to Mainnet in response to a security vulnerability identified by community

Development Update — November 1, 2018

Development Update — November 1, 2018

Hi Liskers,

As usual, it’s been a busy couple of weeks for Lightcurve Development teams. Among key achievements, we have the release of Lisk Core 1.1.1 to Mainnet, a new version of Hub 1.5.0 and Mobile 0.4.0. Check out the full rundown below.

Lisk Core

1.1.0 — With 1.1.0 released on Mainnet, node operators can now switch easily between networks without the need of rebuilding, as well as other improvements, such as an upgrade to Postgres 10, consistent usage of Bignumer.js. Full details of 1.1.0 are available in the previous blog.

1.1.1 — This patch was released to Mainnet in response to a security vulnerability identified by community

Community Spotlight: Core 1.0 Transaction Memo Field Projects So Far

Hey Liskers,

One of the key features of Lisk Core 1.0.0 is the addition of the transaction memo field. It allows the user to send custom notes along with any Lisk transaction they make. Aside from encouraging social interactions between LSK holders, in the future it will also have business use cases. For example, a sidechain project running an airdrop to promote an ICO, will also be able to send additional information, like their website address or terms of the promotion. In the meantime however, we are excited to see our community dive in and start building their own projects using

Community Spotlight: Core 1.0 Transaction Memo Field Projects So Far

Hey Liskers,

One of the key features of Lisk Core 1.0.0 is the addition of the transaction memo field. It allows the user to send custom notes along with any Lisk transaction they make. Aside from encouraging social interactions between LSK holders, in the future it will also have business use cases. For example, a sidechain project running an airdrop to promote an ICO, will also be able to send additional information, like their website address or terms of the promotion. In the meantime however, we are excited to see our community dive in and start building their own projects using

Development Update — October 18, 2018

Development Update — October 18, 2018

Hello Lisk Community,

It 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.

Lisk Core

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

Development Update — October 18, 2018

Development Update — October 18, 2018

Hello Lisk Community,

It 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.

Lisk Core

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

33FansLike
135FollowersFollow