[ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers

[bioly]

Second signature registration is planned for 1.0.0 release - https://github.com/LiskHQ/lisk-nano/projects/4

When approximately the next signature campaign is planned?

Since there are many projects coming up i would even like to join a signature campaign but how to find out whether it is a good one as i have seen many scam coins ,but if lisk is planning for a signature campaign i would definitely wish to join.

I made a little mistake and you missunderstood me, I meant that with 1.0.0 Lisk Nano there will be feuture to create second passphrase from Lisk Nano instead Web wallet (full node). I don't have any info about siganture campaign

[titibach]

Second signature registration is planned for 1.0.0 release - https://github.com/LiskHQ/lisk-nano/projects/4

When approximately the next signature campaign is planned?

Since there are many projects coming up i would even like to join a signature campaign but how to find out whether it is a good one as i have seen many scam coins ,but if lisk is planning for a signature campaign i would definitely wish to join.

thats if the accept your low rank.
i too am interested in joining any potential lisk signature campaign.
stack me some more lisk while i post on the forum like i usually woudl anyway.
win win.

[prix]

But it's shame that the Lisk don't have full-featured light client after a year of development.
We have a big amount of delegates but can't use their nodes as secure backend for light client.

https://github.com/LiskHQ/lisk-nano/projects/4

Good. Waiting for the release on https://lisk.io/download.

[kingcrimson]

Any Old Nut here from 2014?
can you explain about Crypti , why it got failed and How the successor of Crypti (LISK) is different from its parent?

thread to answer: https://bitcointalk.org/index.php?topic=1864791

Lisk was pretty much a second ICO and re-branding. I believe everyone in Crypti got to trade-in their coins for Lisk.

[HelioHash]

Vote for new Lisk pool
LISKLAB
100% profit sharing
for next few weeks

https://twitter.com/LiskLab

*node going online as soon as we receive enough votes

[nyanhtet]

Any Old Nut here from 2014?
can you explain about Crypti , why it got failed and How the successor of Crypti (LISK) is different from its parent?

thread to answer: https://bitcointalk.org/index.php?topic=1864791

You can find answers here: https://blog.lisk.io/what-is-lisk-and-what-it-isnt-e7b6b6188211

[Poly#Crypto]

To all testnet participants:


Lisk v0.8.0c — Release Candidate (Testnet)


Lisk has released v0.8.0c for testnet which is identical to the version coming out on mainnet.
This version includes a minor fix to one of the dapps endpoints and a fix for transactions API regarding maxAmount.
Please update your nodes.

Download Server: https://downloads.lisk.io/lisk/test/0.8.0c/
Lisk Documentation: https://github.com/LiskHQ/lisk-wiki/wiki/Binary-Upgrade

Simple way:

Code:

rm -f installLisk.sh
wget https://downloads.lisk.io/lisk/test/installLisk.sh
bash installLisk.sh upgrade -r test

Join http://lisk.chat  to participate in the testing.

[Jumanji7]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

[nyanhtet]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

Sure. 

[Jumanji7]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

Sure. 

My website passphrase works on both wallets, but my nano passphrase works only on nano wallet and not on the webwallet. any thoughts? 

[nyanhtet]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

Sure. 

My website passphrase works on both wallets, but my nano passphrase works only on nano wallet and not on the webwallet. any thoughts? 

May be wrong typo. Try with Ctrl+V or paste.

[Poly#Crypto]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

The passphrase is not dependent on the type of wallet but belongs to the account. This means if you have created an account via the webwallet and you want to have access to the same account via the Nano Client later, then you need exactly this passphrase. And vice versa...

[Jumanji7]

In Lisk Nano desktop wallet where can I find wallet.dat file?

There is no wallet.dat file, your backup is always the passphrase (and second passphrase if you set)

Is the desktop nano wallet safe? Has there ever been reported problems with it?

Second passphrase can be set in webwallet not in desktop client right?

Yes.No.
Yes.

Can we use the same passphrase in the desktop nano wallet and the webwallet?

The passphrase is not dependent on the type of wallet but belongs to the account. This means if you have created an account via the webwallet and you want to have access to the same account via the Nano Client later, then you need exactly this passphrase. And vice versa...

ok thank you guys. I`ll try again.

[Jumanji7]

besides eth, is there any other competitor of lisk?

[Chevas Regal]

besides eth, is there any other competitor of lisk?

Lisk haven't any competitor of its kind it is just re-branding of a previous coin that had a pre-sale and delivered nothing while Ethereum has Vitalik Buterin, a large team of well-known, community-engaged, crazy talented developers, and a large community of developers working on the core code (everything is open-source), Dapps, and third-party wallets, etc.

^^from: http://ethereum.stackexchange.com/questions/2104/how-does-lisk-differ-from-ethereum

Just hold on! market is so tight today. Interest lack from both side either it isbuy or sell. if lisk wants support and trade volume then either it must either show 0.1$ green bar or a 0.12 red bar..

Code:

Last Price :0.00022015 24hr Change: -0.33% 24hr High: 0.00022572 24hr Low: 0.00021000

[Bigcabrito]

Lisk 0.8.0 has been released, bringing more performance improvements and bug fixes. For this release, we’ve put even more work into database optimization, refining the API layer and resolving some difficult bugs. Following are more details on the changes, enjoy!

The Little Things
As with each successive release it is our pleasure to report a number of bugs that have been squashed. These bugs range from the minor misnamed and deprecated endpoint for the dApps API, to the application listening before it is ready and finally the rare but major nullification of the configuration file. These are just a small list of bugs that were resolved, we know that this list will shrink with successive releases.

Performance
We have also improved the performance of some heavily used database tables, particularly, `trs_list` view has been refactored and now provides much better performance, completely ironing out inefficiencies which cropped up in prior releases. Additionally, a `round_fees` table has been introduced to collect transaction fees awarded to delegates for each round. The new memory table brings performance improvements and much greater data flexibility for historical lookups on fee allocations.
In previous releases, it took up to 120 seconds of not receiving a block from the network to begin pulling fresh blocks from a peer. Now, nodes synchronize blocks after 20 seconds of not receiving new blocks, meaning that lagging peers catch up more often and much faster than before.

Modularity
While efforts toward scalability are ongoing, 0.8.0 brings a much needed step in the right direction. Under 0.8.0 all existing API’s have been extracted into their own modules so that future developments to the Lisk API are far easier to implement.
The binary builds also received some modularity/scalability improvements. We have moved away from Forever as the process manager and replaced it with PM2. PM2 offers much greater flexibility and control of the node process with some performance monitoring features and the required modularity to easily support multiple Lisk processes.

Lisk UI
A large number of bug fixes have been applied to the user-interface component of the Lisk client. The fixes include improved responsiveness on mobile devices, better feedback when placing votes, a more accurate sync progress indicator, the proper removal of user data on logout, and a performance fix related to the display of forging statistics. All of these fixes should help provide a better experience for users awaiting the planned Lisk Nano 1.0.0 release, that will eventually replace Lisk UI as the main user-interface for Lisk.

GPLv3
One final thing of note for these releases is that we are moving from The MIT License to the GPLv3 license. While this has no direct impact on the code itself, it is important to properly license our code in a way that the Lisk Foundation receives recognition on its open-sourced products. Code prior to this release will remain MIT licensed but going forward from Lisk 0.8.0 all new code will fall under GPLv3. If you wish to know more about the differences between the GPL and MIT licenses, please read the article: GPL vs. MIT: Which License to Use.

Summary
Lisk 0.8.0 yields significant performance gains through faster syncing, more efficient use of the database, and greater stability through the resolution of some bugs, continuing to improve upon the solid foundation established by previous releases. This release, along with the planned minor release of 0.9.0, lays the basis for our first major release, Lisk v1.0.0. A complete list of changes can be seen in the release log on GitHub. If you have any questions, feel free to reach out to us.

Original Blog Post

[iimpact]

Lisk haven't any competitor of its kind it is just re-branding of a previous coin that had a pre-sale and delivered nothing while Ethereum has Vitalik Buterin, a large team of well-known, community-engaged, crazy talented developers, and a large community of developers working on the core code (everything is open-source), Dapps, and third-party wallets, etc.

^^from: http://ethereum.stackexchange.com/questions/2104/how-does-lisk-differ-from-ethereum

Also don't miss the reply from Max on that one, it's a massacre I would say Good one Max!

[iimpact]

Lisk 0.8.0 has been released, bringing more performance improvements and bug fixes. For this release, we’ve put even more work into database optimization, refining the API layer and resolving some difficult bugs. Following are more details on the changes, enjoy!

The Little Things
As with each successive release it is our pleasure to report a number of bugs that have been squashed. These bugs range from the minor misnamed and deprecated endpoint for the dApps API, to the application listening before it is ready and finally the rare but major nullification of the configuration file. These are just a small list of bugs that were resolved, we know that this list will shrink with successive releases.

Performance
We have also improved the performance of some heavily used database tables, particularly, `trs_list` view has been refactored and now provides much better performance, completely ironing out inefficiencies which cropped up in prior releases. Additionally, a `round_fees` table has been introduced to collect transaction fees awarded to delegates for each round. The new memory table brings performance improvements and much greater data flexibility for historical lookups on fee allocations.
In previous releases, it took up to 120 seconds of not receiving a block from the network to begin pulling fresh blocks from a peer. Now, nodes synchronize blocks after 20 seconds of not receiving new blocks, meaning that lagging peers catch up more often and much faster than before.

Modularity
While efforts toward scalability are ongoing, 0.8.0 brings a much needed step in the right direction. Under 0.8.0 all existing API’s have been extracted into their own modules so that future developments to the Lisk API are far easier to implement.
The binary builds also received some modularity/scalability improvements. We have moved away from Forever as the process manager and replaced it with PM2. PM2 offers much greater flexibility and control of the node process with some performance monitoring features and the required modularity to easily support multiple Lisk processes.

Lisk UI
A large number of bug fixes have been applied to the user-interface component of the Lisk client. The fixes include improved responsiveness on mobile devices, better feedback when placing votes, a more accurate sync progress indicator, the proper removal of user data on logout, and a performance fix related to the display of forging statistics. All of these fixes should help provide a better experience for users awaiting the planned Lisk Nano 1.0.0 release, that will eventually replace Lisk UI as the main user-interface for Lisk.

GPLv3
One final thing of note for these releases is that we are moving from The MIT License to the GPLv3 license. While this has no direct impact on the code itself, it is important to properly license our code in a way that the Lisk Foundation receives recognition on its open-sourced products. Code prior to this release will remain MIT licensed but going forward from Lisk 0.8.0 all new code will fall under GPLv3. If you wish to know more about the differences between the GPL and MIT licenses, please read the article: GPL vs. MIT: Which License to Use.

Summary
Lisk 0.8.0 yields significant performance gains through faster syncing, more efficient use of the database, and greater stability through the resolution of some bugs, continuing to improve upon the solid foundation established by previous releases. This release, along with the planned minor release of 0.9.0, lays the basis for our first major release, Lisk v1.0.0. A complete list of changes can be seen in the release log on GitHub. If you have any questions, feel free to reach out to us.

Original Blog Post

Congrats to the devs, great work guys!

[NorthPixel]

Lisk 0.8.0 has been released, bringing more performance improvements and bug fixes. For this release, we’ve put even more work into database optimization, refining the API layer and resolving some difficult bugs. Following are more details on the changes, enjoy!

The Little Things
As with each successive release it is our pleasure to report a number of bugs that have been squashed. These bugs range from the minor misnamed and deprecated endpoint for the dApps API, to the application listening before it is ready and finally the rare but major nullification of the configuration file. These are just a small list of bugs that were resolved, we know that this list will shrink with successive releases.

Performance
We have also improved the performance of some heavily used database tables, particularly, `trs_list` view has been refactored and now provides much better performance, completely ironing out inefficiencies which cropped up in prior releases. Additionally, a `round_fees` table has been introduced to collect transaction fees awarded to delegates for each round. The new memory table brings performance improvements and much greater data flexibility for historical lookups on fee allocations.
In previous releases, it took up to 120 seconds of not receiving a block from the network to begin pulling fresh blocks from a peer. Now, nodes synchronize blocks after 20 seconds of not receiving new blocks, meaning that lagging peers catch up more often and much faster than before.

Modularity
While efforts toward scalability are ongoing, 0.8.0 brings a much needed step in the right direction. Under 0.8.0 all existing API’s have been extracted into their own modules so that future developments to the Lisk API are far easier to implement.
The binary builds also received some modularity/scalability improvements. We have moved away from Forever as the process manager and replaced it with PM2. PM2 offers much greater flexibility and control of the node process with some performance monitoring features and the required modularity to easily support multiple Lisk processes.

Lisk UI
A large number of bug fixes have been applied to the user-interface component of the Lisk client. The fixes include improved responsiveness on mobile devices, better feedback when placing votes, a more accurate sync progress indicator, the proper removal of user data on logout, and a performance fix related to the display of forging statistics. All of these fixes should help provide a better experience for users awaiting the planned Lisk Nano 1.0.0 release, that will eventually replace Lisk UI as the main user-interface for Lisk.

GPLv3
One final thing of note for these releases is that we are moving from The MIT License to the GPLv3 license. While this has no direct impact on the code itself, it is important to properly license our code in a way that the Lisk Foundation receives recognition on its open-sourced products. Code prior to this release will remain MIT licensed but going forward from Lisk 0.8.0 all new code will fall under GPLv3. If you wish to know more about the differences between the GPL and MIT licenses, please read the article: GPL vs. MIT: Which License to Use.

Summary
Lisk 0.8.0 yields significant performance gains through faster syncing, more efficient use of the database, and greater stability through the resolution of some bugs, continuing to improve upon the solid foundation established by previous releases. This release, along with the planned minor release of 0.9.0, lays the basis for our first major release, Lisk v1.0.0. A complete list of changes can be seen in the release log on GitHub. If you have any questions, feel free to reach out to us.

Original Blog Post

For some reason, this news has no reaction in the market. Although here basically there is nothing new, only the elimination of some bugs.

[LiskHQ]

For some reason, this news has no reaction in the market. Although here basically there is nothing new, only the elimination of some bugs.

We mentioned the release in advance, so it was probably priced in. However, there are quite a few nice changes in this release.