Updated Details lisk



  • Lisk Hub 0.3.0 — Account Initialization, Lock ID and more

    We are happy to announce the release of Lisk Hub 0.3.0. This minor update brings to you a variety of new features, including account initialization, lock ID, copy address, home button, and a brand new new desktop icon.

    Account Initialization

    As described in one of our previous blog posts, every Lisk account should be initialized with an outgoing transaction, so that the public key of the account is cemented into the blockchain. The initialization can be done by any transaction — it can often be the case however that you don’t plan to do a transaction right after sending funds to a recently set-up account. In that case, the recommended and cheapest way is to send a small amount of LSK to the same account, which costs only the usual send transaction fee of 0.1 LSK.

    In the previous version of Lisk Hub, this could already be done by any user who is aware of this best practice detailed in past blog posts as well as the website help center. But from now on, all users to whom this extra security step applies are reminded right inside the Dashboard and Wallet sections of Lisk Hub. The UI provides a straightforward process to send the account initialization transaction as any ordinary one.

    Lock ID

    Ever since the initial release of Lisk Hub, we have received a lot of community feedback on the feature of account management within the application. Lisk Hub works with the concept of saved accounts that can be either locked or unlocked. Many non-blockchain applications work with a similar concept (e.g. Gmail), but with the difference that you need to enter the password to a saved account to see what is in it (e.g. emails). But with Lisk, all transactions are visible publicly on the blockchain, so knowing the address is enough to see what a particular account contains. This is very convenient if you want to check your account for incoming transactions, but for newcomers to blockchain technology, the practice can feel rather unsafe.

    In order to fix this, we have implemented a timeout of 10 minutes, after which the passphrase is removed from the app. The passphrase is saved only in the running app, so closing the tab or closing the desktop app removes the passphrase. But this was not obvious from the UI and until now, there was no way to remove the passphrase by some action in the app without closing it altogether. With Lisk Hub 0.3.0 you can now lock the account by clicking on “Lock ID” in the account switcher.

    This feature should improve the account management, but we don’t see it as the final state. We are conducting extensive user testing with the app as well as with prototypes of other account management solutions to improve our understanding of how users see the situation, as well as how best to build upon this aspect of the Lisk Hub.

    Other smaller tweaks

    In our push for the constant improvement of the Lisk Hub, we care about adding big features as well as making small improvements to the existing features, Below you will find a couple of these from this release.

    The first tweak comes handy when you need to copy the address of your account. From now on you can just click it in the upper right corner of the Hub window and it is copied for you. The address has the icon that we use next to any element with click-to-copy functionality.

    We have also made the Lisk icon clickable in the upper left corner of the Hub window. It is common practice that the logo links to the home page, and we did chose to implement the same feature. For logged-in users it means going to the Dashboard. Otherwise, it goes to the login page, which makes it easier to navigate between different aspects of the Hub when, for example, browsing the explorer section.

    Lastly, we have updated the icon of the desktop app. It used to be the gray Lisk logo that is in the upper left corner of the app. That one didn’t fit well next to icons of other desktop applications, so it got revamped to a blue circle with a white outline and white Lisk logo inside.

    User survey

    We also take this blog post as an opportunity to promote the Lisk Hub user survey. Please take a few minutes to answer some questions about your experience and expectations with Lisk Hub. Any answer can be instrumental in guiding further development of the product. You can access the survey here.

    For downloading the app and keeping an eye on the development of Lisk Hub in real time, please follow our GitHub page. To access the web version of the Lisk Hub, please follow our platform.

    About the Author:

    Vít Stanislav is a front-end developer for Lisk at Lightcurve and the project lead of Lisk Hub. Previously, he was developing web-based tools for Red Hat. He has plenty of additional front-end experience from developing online learning systems as a member of Adaptive Learning research group at Masaryk University, Brno, Czech Republic. He is committed to making Lisk the blockchain technology with the best user experience.



  • Lisk (LSK) Release Wallet Version 1.0.0-alpha.4

    v1.0.0-alpha.4Full Changelog

    Implemented enhancements:

    • Migrations takes too long after rebuild from snapshot #1799#1811
    • Update broadhash and height headers after block deletion #1803#1795
    • Failed to find common block with: xxx #1789#1786
    • NetworkHeight shows always zero #1778#1809
    • Database migrations must run in series but mutually exclusive to each other #1806#1798
    • Add integration tests coverage for synchronize and broadcast modes #1751#1725

    Merged pull requests:

    Download

    https://github.com/LiskHQ/lisk...



  • Lisk Release Wallet version 1.0.0-alpha

    Closed issues:

    • Update wamp-socket-cluster to newest Beta release #1820#1821 (MaciejBaj)

    Download

    https://github.com/LiskHQ/lisk...



  • Lisk Core 1.0.0 — Open Beta Released, Intensified Testing & Reddit AMA Announcement

    At Lisk, we put the quality of our products above all else. Given the ongoing excitement in our dedicated community, as well as the broader blockchain industry concerning this upcoming release, we are thrilled to announce that we have released the initial Lisk Core 1.0.0 Beta for testing, as scheduled.

    Introducing New Intensified Testing Stages

    At Lisk, we are dedicated to the development of a fully functional and tested final product. In order to achieve this, we have decided to divide our testing processes into two distinct phases for all major releases going forward, starting with Lisk Core 1.0.0. We have called them Betanet and Testnet.

    So what exactly is Betanet? We have introduced this additional stage of testing by creating an artificial replica of our network for any major product rollout — in this case it is Lisk Core 1.0.0. This network will have its own genesis block and will be secured by genesis delegates, with all the delegate nodes being maintained by our DevOps team to start with. After observing the activity of the Betanet for approximately a week, we will give an update on our plan to gradually introduce delegates into this newly created test ecosystem. This extra step in the deployment of Core 1.0.0, will help us safely put in practice and examine all of the variables of releasing Lisk Core 1.0.0 in a controlled environment of Betanet. By trying out the code there first, we are also avoiding any risk of negative effects on the decentralized, master Testnet which is an integral part of the Lisk ecosystem. Once this stage of beta testing is complete, we will be able to migrate Lisk Core 1.0.0 to the master Testnet. After the master Testnet is successfully running, we can release Lisk Core 1.0.0 on the Mainnet.

    How to Get Involved in Testing the Betanet

    While Lisk Core 1.0.0 is on the Betanet, our community members will be able to participate in testing of the network in a variety of ways. To begin with, they will be able to deploy and synchronise a node. They will also be able to interact with the new Application Programming Interface (API), as well as test Lisk Commander, Lisk Elements and Betanet Explorer with the new Lisk Core. Please note: During this pre-release phase (until Mainnet release), the products will be released on GitHub and NPM under their previous names (Lisky, Lisk JS). Lastly, they will be able to enjoy the new peer-to-peer (P2P) transport layer and verify the latest database migrations are working correctly. While Lisk Core is being evaluated in the essential quality assurance step of Betanet, delegates will not be able to send transactions, or participate in securing the network until further notice. We encourage our users to test the new network and provide critical feedback on the testing channel of Gitter.

    Announcing our Upcoming Reddit AMA

    In order to appropriately address any questions surrounding this particular release, the Lightcurve Dev Team will be hosting a Reddit AMA on the topic of Lisk Core 1.0.0. For the sake of providing as much development information as possible, the date of the AMA will be confirmed after Betanet testing has been completed — please subscribe to the Lisk subreddit where you will be able to receive further development updates, as well as more information about the upcoming Reddit AMA. We will provide more information on 1.0.0 releases of Lisk products, including the features of Core, Elements, Hub and Commander, in the coming weeks.

    This period marks an extremely exciting time in Lisk’s technological development. We are continuing to drive towards our objectives, ensuring that the tools we are building will meet the expectations of our entire community and that we remain dedicated to building a new, decentralized future together.

    The Lisk Foundation



  • Lisk (LSK) Release Wallet Version 0.9.13

    Merged pull requests:

    • Remove variable shadowing in transaction apply, applyUnconfirmed, undo, undoUnconfirmed - Closes #1726nazarhussain)
    • Add exceptions for mainnet (nazarhussaindiego-G)
    • Reject transactions with requesterPublicKey (diego-G)

    Closed issues:

    • Remove variable shadowing in transaction apply, applyUnconfirmed, undo, undoUnconfirmed #1726

    Download:

    https://github.com/LiskHQ/lisk...



  • Lisk (LSK) Release Wallet Version 1.0.0-beta.5

    Fixed bugs:

    • TypeError: Cannot read property 'nonce' of undefined #1856#1832

    Closed issues:

    • Cannot read property 'peers' of undefined crashing master process #1865#1862
    • Log current socket number while connecting Peer #1859#1858

    Merged pull requests:

    Download:

    https://github.com/LiskHQ/lisk...



  • Lisk Hub 0.4.0 — Tutorial, Second Passphrase Registration and more

    We are excited to announce release ofLisk Hub 0.4.0. This is another regular bi-weekly update with improvements to our web and desktop app. The main new features are:

    • Onboarding process with a tutorial
    • Second passphrase registration
    • Launch protocol in the desktop version

    Onboarding process

    Lisk Hub is now one of many applications that have a visual way of introducing all the UI elements to new users. The tutorial is launched automatically after you log into an account for the first time in Lisk Hub. You’re taken through all the menu items and account information. Some users prefer to be introduced to applications this way, while others like to click their own way through the app, therefore you have the option to skip the tutorial. We strongly believe that even if you choose to skip the tutorial, the UI should be intuitive and user-friendly.

    Second passphrase registration

    You can now register a second passphrase to your Lisk ID in Lisk Hub. Second passphrase is a 12-word mnemonic, similar to the first passphrase, and can be registered as an additional layer of authentication to your Lisk ID. If registered, it will be required to confirm any outgoing transaction.

    The feature in Lisk Hub is accessed from the gray carousel under “More” in the main menu. The registration is a multi-step process similar to creating a new account. The second passphrase is transaction stored on the blockchain, so there has to be a fee for it to prevent any malicious parties from bloating the blockchain. Currently the fee is 5 LSK, which is a lot given the current price of LSK. The fees will be adjusted in a future release of Lisk Core.

    Launch protocol in the desktop version

    Lisk launch protocol was first introduced in Lisk Nano 1.2.0 and is a scheme of links that allows you to easily access various sections within the application. There are already many community tools that use the launch protocol for the most useful use cases, pre-filling votes and sending transactions.

    The launch protocol for voting is a major improvement for the user experience. Without it, you would have to look up each delegate name when sharing a list of delegates for voting. With the protocol, there is a link that allows you to seamlessly share lists of delegates for voting using the link lisk://main/voting/vote. The link accepts two optional parameters: votes and unvotes, each with a list of comma-separated delegate names, e.g. lisk://main/voting/vote?votes=genesis_14,genesis_24,genesis_55&unvotes=genesis_29

    When transferring LSK tokens, you can create a link with two optional parameters:

    • The receiver’s address (e.g. 537318935439898807L)
    • The amount of LSK you want transferred (e.g. 100 LSK)

    The link will end up looking like this: lisk://main/transactions/send?recipient=537318935439898807L&amount=100.

    If you have installed Lisk Hub 0.4.0, the link opens and pre-fills the send dialog with the values.

    Other smaller tweaks

    The first of the smaller tweaks comes handy if you manage multiple accounts. You can now copy the address from any of them in the account switcher without the need to switch to that account.

    We have also made some improvements to the account lock timeout in the upper right corner. The wording “Address timeout 09:52” was confusing to some users, therefore we changed it to “ID lock in 09:52”, which better describes the fact that when the timeout runs out, the ID is locked and the passphrase will be required to perform any further transactions.

    In addition, we added an option to reset the timeout back to ten minutes once the time left is below five minutes. This option is useful if you need more time to perform a transaction.

    You can access the web version of Lisk Hub at https://lisk.io/hub/. For downloading the desktop app and keeping an eye on the development of Lisk Hub in real time, please follow Lisk Hub on GitHub.

    About the Author:

    Vít Stanislav is a frontend developer for Lisk at Lightcurve and the project lead of Lisk Hub. Previously, he was developing web-based tools for Red Hat. He has plenty of additional frontend experience from developing online learning systems as a member of Adaptive Learning research group at Masaryk University, Brno, Czech Republic. He is committed to making Lisk the blockchain technology with the best user experience.



  • Lisk (LSK) Release Wallet Version 1.0.0-beta.6

    Fixed bugs:

    • Never reuse sockets and always destroy socket instead of just disconnecting and always unbind all event handlers - Potential memory leak #1876#1847
    • Post mutisig tx via peers with invalid signatures takes down the node #1845

    Closed issues:

    Merged pull requests:

    Download:

    https://github.com/LiskHQ/lisk...



  • Lisk North America Tour 2018 Recap

    With a mission to expand Lisk’s global presence, we announced that we would be embarking on a Lisk North America tour in early spring. With the completion of the tour, I’m excited to share all of the details with you! This blog post will detail the cities I visited, the events, as well as the wonderful people and community members I met.

    First Stop — April 2, 2018: Meetup, San Antonio, Texas, US
    Second Stop — April 4–5, 2018: Conference and Meetup, Ottawa, Ontario, Canada
    Third Stop — April 9, 2018: Meetup, Seattle, Washington, US
    Meetup in San Antonio.

    San Antonio, TX

    The first city I visited on the Lisk North America tour was San Antonio. The city’s warm climate and people made this part of the trip very memorable. With a population of approximately 1.5 million, San Antonio is one of the fastest growing cities in the United States; San Antonio contains one of the fastest growing Lisk communities in the country as well.

    Group photo with San Antonio community members.

    The San Antonio Lisk meetup took place at Geekdom Event Centre in downtown San Antonio and was hosted by Lisk Ascend member Brandon, also known as Nimbus76, and Lisk USA, which is led by Edward, also known as StellarDynamic. The meetup opened with cyber security industry programmer Omar Quimbaya, who spoke very eloquently on the topic of blockchain scalability. Following his presentation, I provided a recap of the Lisk Relaunch and our newest products. I met many interesting people to list them all off here. However, one attendee that I had the pleasure of getting to meet was Javier, who runs TechQuarry, an IT services company in San Antonio. We discussed several topics, including the fact that he is in contact with many companies that have expressed interest in the Lisk platform.

    Later in the evening, several community members and I continued our interesting discussions over a delicious dinner on the city’s famous Riverwalk.

    To join Lisk San Antonio Meetups group, click here.

    On stage at the Forward JS: Ottawa Summit.

    Ottawa, Canada

    For those who haven’t been to Ottawa, Canada, it is a vibrant place with a perfect mix of historical old town and bright city lights. This stop on the tour was to attend the Forward JS: Ottawa Summit at the Adobe Systems corporate office. This event was one of the major highlights of the tour, as it gave me the chance to present Lisk in front of a crowd of nearly 200 JavaScript developers, which are such an integral part of Lisk’s ecosystem. I discussed the Lisk platform and how Lisk is bringing together blockchain and JavaScript. Other speakers at the conference were developers, engineers and scientists from companies such as Shopify, IBM, Else Labs Inc., Washington Post and Adobe. The presentation that really resonated with me came from Adobe Senior Software Scientist Simon MacDonald, on the potential of JavaScript. Throughout the conference, I was able to network with the brightest minds in the JavaScript industry, including the likes of Brian Farias Tavares, a software engineer with Else Labs, James Rauhut, a frontend and UX designer for IBM’s Design System, and many other valuable developers.

    Group photo with several community members at the Lisk meetup in Ottawa.

    Lisk’s first meetup in Canada, co-hosted by Bloqspace and LiskHQ, was held the day after the Forward JS Summit. I presented an overview of the Lisk ecosystem to the crowd over quintessential American snacks — nachos, chicken fingers and onion rings. I had the fortune of meeting an incredibly talented and dedicated developer by the name of Greg Sienkiewicz, who was able to speak very eloquently about the immense potential that Lisk will offer to developers looking to develop blockchain applications.

    Going forward, JavaScript developer and Lisk community member Adam Daw will organize Lisk meetups regularly in Ottawa. Following the continued success of Lisk meetups in Ottawa, I am confident that other cities across Canada will follow suit.

    To join the Lisk Ottawa Meetups group, click here.

    The crowd at the Lisk meetup in Seattle.

    Seattle, WA

    Seattle, Washington is energetic, young and also home to tech giant Amazon. It is a city for technological innovation and very, very good coffee. Lisk community members Paul and Yaman organized this meetup, the first meetup to-date in Seattle. The event garnered over 200 RSVPs within two weeks of its announcement, indicating the tremendous interest in Lisk in Seattle.

    The meetup was held at the Wells Fargo Center in downtown Seattle complete with chicken wraps and croissants. My presentation included an informative and detailed look into Lisk’s ecosystem and our major advantages in the blockchain space. The audience was very engaged and full of great questions. I really enjoyed the open discussion we had regarding potential use-cases for Lisk.

    Speaking to the Seattle community members about the benefits of blockchain.

    This event was Lisk’s biggest community-organized meetup ever hosted in North America. It was also incredible to see the number of Lisk Seattle meetup members soar following the meetup.

    To join the Lisk Seattle Meetups group, click here.

    In conclusion, I’m so grateful to have had the opportunity to attend all three meetups and conference in North America. I am also more confident than ever before in the communities’ ability to accomplish great things, having seen how passionate and knowledgeable they are. Everyone in attendance expressed their strong faith and belief in the Lisk project, its team and mission.

    I want to give a huge thank you to all of our Lisk community members around the world for their dedication to supporting a decentralized world and future. The team at Lightcurve is working very hard to make blockchain accessible to everyone. We see the expansion of our global presence as a primary way to achieve this.

    Although this is the conclusion of the Lisk North America tour for now, we will surely visit many more cities in the US. As always, we will keep you posted as soon as we solidify upcoming plans. As we previously announced, we will be attending the blockbuster blockchain and cryptocurrency conference Consensus 2018 in New York City in May.

    Best, Lisk Community,



  • Lisk (LSK) Release Wallet Version 1.0.0-beta.7

    Bump version 

    Download 

    https://github.com/LiskHQ/lisk...



  • Lisk (LSK) Release Wallet Version 0.9.14

    Merged pull requests:

    • Inconsistent behavior between syncing and snapshotting - Closes #1879nazarhussain)
    • Add code changes for handling inert transactions - Closes #1880SargeKhan)
    • Remove exceptions added in 0.9.13 for mainnet - Closes #19164miners)

    Closed issues:

    • Inconsistent behavior between syncing and snapshotting #1879#1880
    • Remove exceptions added in 0.9.13 for mainnet #1916

    Update At :https://github.com/LiskHQ/lisk...



  • Lisk Explorer 1.6.0 — New UI, new UX

    We are happy to announce the latest version of Explorer: Lisk Explorer 1.6.0. This release brings about the new UI theme that matches the new Lisk.io design that was first introduced at our Relaunch event in February. Also included are several stability patches, and most importantly, improved UX for mobile devices.

    Over the next few weeks, we’re going to be focused on minor fixes to polish up the new explorer.

    Desktop view of Explorer.

    About the new UI

    The new UI for desktop maintains the same functionality as before. The re-designed view matches our site.

    Our frontend team put a great deal of effort into making the application similar to the other apps in the Lisk ecosystem. General tools like top accounts, market watcher, network monitor and delegate monitor have also implemented the new design.

    Mobile view.

    New functionalities in mobile view

    This release makes the search feature accessible on a small smartphone screen. The magnifying glass icon lets us look for a certain transaction, block, account, delegate public key or block height.

    To make the view more mobile-friendly, we sacrificed the rank column and introduced an address shortener. Thanks to this, it is possible to see approximate one’s balance (decimal places are truncated) and percentage stake of the market cap.

    We optimized the spacing to better suit smaller screens. We improved sorting in the delegate and network monitor; the current sorting algorithm deals much better with the columns.

    Stability fixes

    The new release also includes many stability fixes. Lisk Hub uses the Explorer’s backend API for the chart displaying the value of Lisk. It’s important because all apps are co-dependent in the Lisk ecosystem.

    The backend is much more resistant to invalid responses from third party services such as cryptocurrency exchanges. We’re maintaining high coding standards therefore, in the following weeks, we are going to be focused on improving automated tests.

    The full changelog can be found here.

    -Michal and the Lisk Team



  • Upcoming Conferences + Lisk Meetups

    Mat, Michael, Jacob and Thomas at the Lisk London Meetup in April.

    The Lightcurve team is hard at work spreading the word of Lisk. As a slew of blockchain and cryptocurrency conferences around the world quickly approaches, we wanted to provide a breakdown of the ones where the Lightcurve team is going to be present.

    With conferences like Token 2049 in Hong Kong, Slush in Tokyo and Forward JS in Ottawa down, there are still many to go. Last week, Community Manager Mat Piaggi and Lisk Academy Lead Jacob Kowalewski traveled to Vilnius, Lithuania to attend the Crypto Capital World Summit on April 25–26. Hosted at the Vilnius Grand Resort, a sprawling hotel complex half an hour outside of Vilnius, the conference offered a speaker lineup consisting of Tim Draper, Monetha founder Justas Pikelis and Lisk’s own Jacob Kowalewski.

    To suit the nature of the projects in attendance, namely budding ICOs, Jacob’s keynote was titled “Marketing an ICO to Facilitate the Adoption of Blockchain Technology”. The subjects covered included the problem with ICOs today, the solution to these problems and how the candid and supportive nature in which Lisk conducted it’s 2016 ICO has contributed to Lisk’s core values of education, as well as enablement. The unanimous feedback was that Lisk presented one of the strongest keynotes at the conference. On the second day, Jacob also participated in a panel discussing ICO marketing with these young projects and explained that ICOs should become more altruistic in how they educate and facilitate adoption and build their community, rather than solely focus on raising funds.

    Jacob and Mat formed several key relationships over the span of two days, including a number of projects planning to develop on the Lisk network. Overall, the conference was a great success with each attendee now acutely aware of Lisk’s vision.

    Upcoming Conferences

    On May 4-5, blockchain conference Chainges will be taking place in Amsterdam. Cryptographer Iker Alustiza will be a featured panelist in a vibrant panel discussion focused on blockchain platforms. He will participate alongside Interim President at NEM, Kristof Van de Reck, and Ilya Smagin, Smart Contract Lead Developer for Waves. They will cover several topics, including decentralized applications for mainstream use, and whether or not tokenization is necessary to make dapps functional and popular.

    Shortly thereafter, we will be attending and sponsoring Consensus 2018, a blockbuster blockchain technology summit in New York City. This will be host CoinDesk’s fourth year running the conference and will feature over 250 speakers and over 4,000 attendees from the leading industry startups, investors, financial institutions, enterprise tech leaders, and academic and policy groups who are building the foundations of the blockchain and digital currency economy. Given that Consensus will be occurring during Blockchain Week in New York, there will be dozens of meetups and events taking place every evening.

    Subsequently, members of the team will attend Token Summit in New York City on May 16-17. The conference will focus on the economics, regulation and best practices surrounding blockchain-based tokens, protocols and crypto-assets. Attendees include projects from the blockchain and cryptocurrency space as well as venture capital firms.

    At the same time, from May 16–18, the WeAreDevelopers World Congress will be taking place in Vienna. WeAreDevelopers will bring together 8,000 tech enthusiasts with an incredible speaker line-up including the likes of Steve Wozniak and Andreas M. Antonopoulos. We hope to increase our involvement in developer-focused conferences like this one. We also plan to begin sponsoring similar events in the future.

    Following WeAreDevelopers, members of our Design team and Human Resources will be attending major design conference OFFF Barcelona 2018 to hear and see the most creative and talented minds today in the design world, as well as to attract additional talent to add to our team.

    Max Kordek, CEO and co-founder of Lisk, will be speaking at the Distribute 2018 conference on the campus of Bucerius Law School in Hamburg on June 28. The overall goal of the conference is to learn how to best take advantage of blockchain technology.

    We see tremendous value in attending conferences as it allows us to stay attuned to overall developments in the blockchain industry, network with other projects and learn more about what they are doing. But most importantly, it allows us to talk about and showcase Lisk to people who previously may not have heard of Lisk or to those who might know a little bit about Lisk, but not quite grasp the impact that we want to make.

    Upcoming Lisk Meetups

    The Lisk New Orleans community will be hosting its fifth Lisk meetup in New Orleans on May 30. The main topic of discussion will be the Lisk ecosystem, with the support of Lisk USA and Edward Trosclair.

    On June 7, Lisk Mentor Matthew and Lisk USA will host Miami’s third Lisk meetup. The focus of the meetup will be on blockchain governance, the Lisk platform, and the Lisk DPoS system.

    Make sure to visit the events page on our website for the latest information on which events and conferences we will be attending, as well as where you can check out Lisk meetups.



  • Lisk Community Update — April 2018

    Hello everyone!

    As always, April was a very busy month on all fronts — development, marketing and operations. To complement this blog post, we’ve included the Lisk Vlog #2, which provides a visual recap of all the happenings at LiskHQ in April.

    The Community Update for April will cover the following:

    • Company Update
    • Development Update
    • Marketing Update
    • Community Update
    • Next Steps

    Company Update

    • Consistent with our strategy to double in size this year, the Lightcurve team is continuing to grow month after month. In April, two new members joined the team: Abel Boldu as our latest DevOps Engineer and Gabriela D’Alo as Human Resources Generalist. We’re very excited to have them on board.

    Development Update

    In April, Darpal Rating ranked Lisk as one of the top blockchain projects in terms of GitHub activity for March. Our development team continued to work incredibly hard throughout the month of April. We recently announced that we have decided to cease hosting the online versions of Lisk Hub and Lisk Nano as we have come to the conclusion that the web version cannot guarantee the additional levels of security that the desktop version of Lisk Hub offers. If you haven’t already, please download and use the desktop version. And if you’re interested in learning more about decision, please read our comprehensive blog post on the topic.

    • Lisk Core 1.0.0 Beta was released for testing last month. As we described in major detail in our corresponding blog post, we decided to divide our testing processes in two distinct phases for all major releases going forward, starting with Lisk Core 1.0.0 — Betanet and Testnet.
    • Lisk Explorer 1.6.0 was released last month, and included new UI and UX elements that correspond with the new Lisk.io design. To learn more about the release, please read our recent blog post. Prior to this release, we also released Lisk Explorer 1.5.0, which fixed bugs and closed issues; you can read the full changelog here.
    • We released Lisk Core 0.9.14 and closed issues such as inconsistent behavior between syncing and snapshotting and added code changes for handling inert transactions. You can find the changelog on GitHub. We also released Lisk Core 0.9.13 earlier in the month which addressed variable shadowing and added json schema validation for transaction.signatures property among much more. You can read the full corresponding release notes here.
    • Lisk Hub 0.5.0 was released, which brought the following changes: delegate registration, new version release notes in the desktop app and simplified URL scheme. You can read much more about the release with its corresponding blog post. In the same month, we also released Lisk Hub 0.4.0, which added new features such as an onboarding tutorial, second passphrase registration and launch protocol in the desktop version. Read more about this release on the Lisk Blog.

    Marketing Update

    • The Lisk Blog published 10 articles in April, including an interview with Lisk Community Member Aleksey aka Alepop, a feature on ADAMANT Messenger, as well as Jan’s comprehensive post about the Lisk North America Tour.
    • Last month, Community Manager Mat Piaggi and Lisk Academy Lead Jacob Kowalewski traveled to Vilnius, Lithuania to attend the Crypto Capital World Summit on April 25–26. Jacob presented on the topic of ICOs on Day 1 and participated in a panel on Day 2. Jacob and Mat formed key relationships at this conference, include those with projects planning to develop on the Lisk network.
    • In April, we received 49 media mentions and 8 media placements, including Nasdaq, and ICO Crowd Magazine.
    • There were a number of great interviews that took place over the month:

    Lindsay Buescher was interviewed by Crypto Potato

    Julian Alterini was interviewed by Crypto Briefing

    Max Kordek was interviewed by Ivan On Tech

    Max Kordek was interviewed by BTC-Echo

    Jan Liz Fonts was interviewed by Ryan Berkness and Dale Brose

    Will Clark was interviewed by International Business Times

    Thomas Schouten provided commentary to ValueWalk

    Andries Bellemans provided commentary to Bankless Times

    In addition, Michael and Jacob were interviewed in London for an upcoming documentary, Beyond Bitcoin.

    Community Update

    • On April 18, Lisk held its inaugural London Meetup. With over 150 attendees, the meetup was a great success. Presenters included members of the Lightcurve team as well as Shane V. Kehoe of SVK Crypto, a prominent London-based cryptocurrency investment fund.
    • We opened up applications for community members in Japan and China to translate the Lisk Academy into their respective languages. We had a number of quality candidates and will continue to consider people who are willing to contribute. If you would like to find out more, please email [email protected]
    • Finally, we want to give a special shout out to the dedicated Lisk community members who reviewed our Core Betanet: cc001, slamper, gr33ndrag0n, punkrock, arca_music, carbonara, StellarDynamic, Karek and biolypl.

    Next Steps

    We are still actively hiring talented individuals to join our team. We have recently added a new opening for the position of Community Manager. Please check out AngelList for more details about Lightcurve’s open positions.

    These next few months are going to be incredibly busy for Lightcurve. In a recent blog post, we highlighted all of the blockchain and cryptocurrency conferences around the world that team members will be traveling to in order to spread the word of Lisk.

    We hope to possibly see some of you in person at any of the events we will be attending this month! As always, thank you for your continued support and dedication to our vision to make blockchain accessible.

    -The Lisk Team



  • Lisk Hub 0.6.0 — Improved transaction details, Amount in EUR/USD, and more

    We are happy to announce the release of Lisk Hub 0.6.0. This release of our desktop app brings the following changes:

    • Improved transaction detail page
    • See amount value in EUR/USD when sending LSK
    • Vote launch protocol landing page
    • Other small tweaks

    Improved transaction detail page

    We made some updates on the transaction detail page. The transaction type (e.g. delegate vote) is now the title of the page to help users immediately distinguish what kind of transaction they’re looking at. However, the biggest change has been made under the “Delegate vote” transaction detail. From now on, it displays all the votes that were added or removed in this transaction.

    See amount value in EUR/USD when sending LSK

    We added the conversion of LSK into EUR/USD in the transfer module to provide a quick way for users to make sure the LSK amount filled in is the right amount to be sent.

    Vote launch protocol landing page

    The vote launch protocol screen is new. From now on, the landing page informs users of which delegates were selected from the launch protocol, whether some delegate names couldn’t be resolved, or if they have already been voted for.

    Other small tweaks

    We also worked on the moving shapes in the “Create” step of the registration process. Moving your mouse now not only makes the shapes move towards the center to form your new Lisk ID avatar, but they also change colors while moving. The update is purely visual and is meant to give the user a hint that the final colors of your Lisk ID avatar depend on how you move your mouse.

    Finally, we decreased the height of the price chart on the main dashboard page to give more space to the “Latest activity” module under the chart.

    Download the desktop app and keep an eye on the development of Lisk Hub in real-time by following Lisk Hub on GitHub.

    About the Author:

    Vít Stanislav is a frontend developer for Lisk at Lightcurve and the project lead of Lisk Hub. Previously, he was developing web-based tools for Red Hat. He has plenty of additional frontend experience from developing online learning systems as a member of Adaptive Learning research group at Masaryk University, Brno, Czech Republic. He is committed to making Lisk the blockchain technology with the best user experience.



  • Lisk (LSK) Release Wallet Version 1.0.0-beta.7.4

    Download:

    https://github.com/LiskHQ/lisk...



  • Development Update — Lisk Core 1.0 Beta Testing

    Hello Lisk Community!

    In an ongoing effort to update you on our development progress, we’ve written a comprehensive blog post to address the status of Lisk Core 1.0 and Beta Testing.

    With this blog post and other development-related posts, we aim to deliver in-depth updates in a way that you can understand what it is we’ve accomplished in the past weeks no matter what your technical background is. We want to promote transparency regarding our development to help you understand our decision-making, the reasons behind potential delays and finally to offer a clear overview of the next steps.

    Lisk Ranked #3 by the CCID

    Before we begin, we have great news to share related to our development. Lisk has been recognized as the top 3 ranked public blockchain project by the CCID: China’s Ministry of Industry & Transformation Technology!

    Lisk Ranked #3 in CCID Blockchain Rating.

    It has been a little over one month since the public deployment of the Lisk Core 1.0 Beta Network, and within this time, 80+ Lisk Core issues have been closed accompanied by 309 commits made towards the advancement of Lisk Core 1.0 and the codebase.

    From the 80+ issues closed, six were recognized to be difficult to the point where they were labeled as ‘hard’ issues. A ‘hard’ label means that a vast amount of resources, time, and effort from our team is needed to resolve such complications.

    Lisk Core 1.0 issues closed from 09/04–14/05.

    Memory Leaks in the Core Application/Postgres

    Within the last month, we spent most of our time and resources working to resolve the primary ‘hard’ issue identified as — ‘Memory leaks in the core application/postgres’, issue #1882. This particular complication (#1882) was discovered during the beta testing process, which stemmed from the network sockets not being properly destroyed in the stage of communication. This was in part due to network-wide duplicate entries of peers objects.

    Breakthroughs that brought us closer to solving the issue led to even more code changes needing to be made, allowing us to continue on and eventually find the main source of the problem. For this reason, issue #1882 was persistent and remained open for the length of time that it did.

    Issue #1882’s Expected Behavior vs. Actual Behavior.

    A Major Breakthrough in Development

    We are thrilled to report that four days ago, the Memory Leak issue was finally fixed and completely closed. As a result, we’ve successfully progressed over this 3-week hurdle, allowing us to make further code advancements and headway in the development of Lisk Core 1.0.

    Next Step: Fix Issue #2025

    At the moment, our team’s focus has entirely shifted to a new, ‘medium’ labeled issue that was uncovered during the time that was taken to fix issue #1882. This ‘medium’ labeled issue, #2025, relates to our network peers not properly staying in one accord or in alignment when it comes to network broadhash and forging new blocks. They tend to, instead of forging the correct block and sharing these details amongst other peers, look to forge the next block without verifying if it has been forged by someone else, leading to a recurring fork in the network. With the discovery of this issue, our team is proactively working to solve it day in and out to successfully get this closed in what is expected to be a short turnaround time.

    Lisk Team Contributors for Core 1.0 Development.

    After #2025 Is Fixed

    When issue #2025 is resolved, an in-depth testing and enhancement of the fix will take place, after which we expect to be in a position where Lisk Core 1.0 will be in the final stages of development. The remaining minor issues would then be left as tasks to complete before the final Beta is released.

    Releasing Lisk Core 1.0 to Testnet and Mainnet

    Shortly after, we will prepare the transition of Lisk Core 1.0 to Testnet where the very final testing of the newly fixed and added code will take place. The highlight here is that the length of time that Lisk Core 1.0 spends on Testnet is anticipated to be much shorter and quicker than Betanet, placing us in position, with great and immense achievement, to have a successful Lisk Core 1.0 migration to Mainnet.

    In short, this is a detailed explanation to say that we are very close to completion of Lisk Core Beta Testing. We also want to share the major achievements made by our development team. At this stage in development, the outlook is promising due to the vast amount of time that’s been put into proper testing of the Lisk codebase.

    Lisk Core Testnet Announcement

    We will in due time publicly announce the details of the migration from Lisk Core 0.9.14 to Lisk Core 1.0.0 on Testnet. This announcement will include the necessary information for a seamless migration to the newly improved Lisk codebase such as a set block-height for when the migration will take place and further documentation to assist our network peers and delegates.

    One More Thing…

    It needs to be made crystal clear that at any point in time, a major issue may arise which would delay the trajectory of our anticipated timeframe. However, with our team having made great progress as of late, this detailed update and optimism is warranted.

    What is Lisk Core 1.0?

    I would like to give a final reminder of what Core 1.0 is: Core 1.0 is Lisk’s biggest development and release to date, including over 4,560 commits and 500+ code changes/enhancements in one single deployment.

    • A completely new design and new API
    • A new P2P transfer layer
    • New layer for communication with the database
    • Code migration to es6
    • Full atomic block writes
    • Security fixes and improvements
    • Block processing enhancements
    • Improved code standards
    • Addition to the 64 byte data field for type 0 transactions

    Another step that will be taken on the communications side moving forward will be to continue providing regular development updates. For real-time progression of what was discussed above, I highly recommend following our Lisk Core GitHub Repository.

    Have a great week, Liskers!

    -Jan

    About the Author:

    Jan Liz-Fonts is a community manager for Lisk at Lightcurve GmbH. Known for being the first to learn about innovative ideas that would change the world, Jan has always found a way to contribute to and support startups that he believes in. Jan first learned about Bitcoin and blockchain technology in 2010 when he was only 13 years old. He moved from Minnesota to join the Lisk project and tea



  • Lisk (LSK) Release Wallet Version 0.9.16

    Change Log

    0.9.16 (2018-06-05)

    Full Changelog

    Closed issues:

    • Error from modules.round.tick is ignored
    • Last block is set before block is saved to
    • Incorrect usage of promises in Chain.prototype.saveBlock

    Merged pull requests:

    Download:

    https://github.com/LiskHQ/lisk...



  • lisk - Further Details Regarding June 2 Network Interruption

    Recent blocks added to the Lisk blockchain.

    On Saturday, June 2, the Lisk network experienced a temporary halt. Despite the fact that the issue was identified and resolved within several hours, we believe the situation warrants a more thorough explanation of precisely what happened to the Lisk network.

    Lisk Core uses PostgreSQL, a relational database. Blocks are stored as rows in a `blocks` table. This table has a foreign key constraint requiring that each block contain the ID of the previous block — the constraint here being that the previous block must already exist in the database. Insert operations which do not conform to the constraint will fail and not be saved. Similar to that, transactions are stored as rows in a `transactions` table, with the different parameters of a transaction, like a timestamp, sender, recipient, and amount, being saved in columns.

    In the early hours of last Saturday morning, an anonymous individual broadcasted a transaction to the Lisk network with a timestamp of -3704634000, which comes out to be 1898–12–31 13:00:00 CEST. This requires a manually created and signed transaction, which is how we know it was intentional. The timestamp column in the `transactions` table will only accept a 32-bit integer value (a value between -2,147,483,648 and 2,147,483,647) — the timestamp used exceeded this range. Therefore, the transaction can be described as malformed and malicious; this resulted in the transaction not being inserted into the database. When a block is saved to the database, the block and its corresponding transactions are written as one atomic database operation; if a transaction-insert operation failed, the entire block-insert operation will fail as well. Thus, the whole block with the malformed transaction did not get inserted into the database. All subsequent attempts at block-insertions referenced the block ID of this nonexistent block and failed to insert due to the previous block foreign key constraint. This, in turn, halted all transaction and block-insertions into the database. That is the described security measure we reported on Saturday.

    Here are the exact errors:

    ```
    ERROR: integer out of range STATEMENT: INSERT INTO “trs”(“id”,”blockId”,”type”,”timestamp”,”senderPublicKey”,”requesterPublicKey”,”senderId”,”recipientId”,”amount”,”fee”,”signature”,”signSignature”,”signatures”) VALUES (‘181175095785369468’,’5488578331239914243',0,-3704634000,’\x6dd24c92d91c0082f5be68f7350d87b7cdf105267543f1f61d3043a5c2d8a00b’,null,’3402562013208542942L’,’3402562013208542942L’,1,10000000,’\xcde9a3459b1f5590a9b6f32a5d9c2e85596be9d01ded14fa9d9c5f276a37e2562e40f459c727599323e1ee84435a63316b3a3a50fb3b5d687dc7ea1f1ad9e001',null,null) ERROR: insert or update on table “blocks” violates foreign key constraint “blocks_previousBlock_fkey” DETAIL: Key (previousBlock)=(5488578331239914243) is not present in table “blocks”. STATEMENT: INSERT INTO “blocks”(“id”,”version”,”timestamp”,”height”,”previousBlock”,”numberOfTransactions”,”totalAmount”,”totalFee”,”reward”,”payloadLength”,”payloadHash”,”generatorPublicKey”,”blockSignature”) VALUES (‘13977984917448353211’,0,63803270,6144655,’5488578331239914243',0,0,0,400000000,0,’\xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855',’\x6cb825715058d2e821aa4af75fbd0da52181910d9fda90fabe73cd533eeb6acb’,’\x0b534abcbe640cef4df6a579bbffe00eb62401b9090e6d7f1ef72e4dafaa31bdb8594b85007f7d8ed79d4166835334ca2adb0830a175d6ac39263fe5fcf8950f’) ERROR: insert or update on table “blocks” violates foreign key constraint “blocks_previousBlock_fkey”
    ```

    Upon closer inspection following our Saturday afternoon announcement, we discovered that Lisk Core did not fully catch the error. The chain continued to move forward with mostly empty blocks only stored in memory and not written to the database. Therefore, we can rest assured that no user funds were at risk assuming that our users rely on the immutable blockchain state and not the memory state.

    Saturday, June 2, 2018 Lisk Core 0.9.15 Release

    When it became apparent that we needed a Lisk Core 0.9.15 release to prevent such a transaction from being accepted again, we immediately contacted exchanges and asked them to temporarily halt withdrawals and deposits, although LSK funds were safe the entire time. A pull request with the fix (https://github.com/LiskHQ/lisk/pull/2087) was made by Simon Warta, one of our community members, which we accepted after a careful peer review. The new release of version 0.9.15 of Lisk Core, which included the fix, was tagged, built and then rolled out to our testnet.

    Shortly afterwards, the new release was also applied to our mainnet. To ensure a smooth upgrade of the whole network, we had to do this as a hard fork. We deployed the new release first to one of our mainnet seed nodes, temporarily setting the minVersion parameter in the configuration to an earlier version (0.9.14), so that it could communicate with the rest of the network and sync up to the last fully valid block without the malicious transaction.

    Afterwards, we set the minVersion parameter on the seed node back to the latest version (0.9.15). Then, we deployed the new release to the rest of our seed nodes with the minVersion parameter set on the latest version (0.9.15), and let them fully sync up from the one seed node already fully in sync. Normally we don’t carry out this syncing process; but in normal upgrades, databases of our network nodes are in a valid state. However, they were not in this case, therefore we had to execute the steps described above. This slowed down the deployment process.

    On late Saturday afternoon, Lisk Core 0.9.15 was officially released to the public and delegates immediately upgraded their nodes to the latest version. By the early evening, activity on the network and exchanges returned to normal.

    June 5, 2018 Lisk Core 0.9.16 Release

    As explained above, Lisk Core 0.9.15 only fixed the timestamp problem, however, it didn’t fix the root cause of the problem, which was that Lisk Core didn’t correctly catch the error that occurred. In an effort to prevent similar situations from arising in the future, we have released Lisk Core 0.9.16 today.

    The fixes of the new release are:

    • to handle errors properly and crash the application if an error is returned from the database during blocks/transactions-inserts (when one of the database queries fails).
    • to set `lastBlock` into node memory only after the block is successfully written to the database.
    • to handle errors properly and crash the application when the round tick fails (the round tick tracks the progress of each round, mainly the weight of votes for particular delegates, blocks’ rewards and transactions’ fee splits).

    Looking Forward

    We’re proud of the Lisk network’s safety and security, and the people who facilitate this. The developers at Lightcurve’s office were incredibly quick to respond to the issue; several of them came into the office on Saturday morning and worked quickly and efficiently to resolve the issue. All the while, the Lightcurve Marketing team immediately established channels of communication, particularly on Lisk.chat and Reddit, to address the situation to our community.

    We’d also like to take this opportunity to give a huge thanks to the Lisk delegates. They were integral in helping us get the network back to normal. We’d especially like to give a big shoutout to Simon Warta, Carbonara and Nerigal!

    And finally, we want to thank our community for their patience, feedback and ongoing support.

    -The Lisk Team



  • Lisk Hub 0.8.0 — New Settings Page and Sign Message

    It is our pleasure to announce the new and improved version of our Lisk desktop app — Lisk Hub 0.8.0. This release includes the following enhancements:

    • New settings page
    • Sign message via launch protocol

    New settings page

    Regarding settings, I believe that we need to limit complexity and provide reasonable defaults of Lisk Hub features to lower the entry barrier for users who are new to blockchain. However, we also have more experienced users who might have different needs.

    Lisk Hub used to have a neat settings module in the menu. It worked fine with the few settings we currently have, even though it appeared to be somewhat difficult to navigate for some users. Some of the new features of Lisk Hub will also require more settings. For this reason, we created a dedicated settings page much better suited for scaling up the amount of settings in the upcoming releases.

    Sign message via launch protocol

    We believe that signing a message is quite an advanced feature of blockchain projects, which won’t be needed by most mainstream users we hope to attract. Since the time we communicated this to our community, we received a lot of feedback about why the feature is necessary in Lisk Hub.

    In other cases with a rare feature like this, the solution could be found in a single-purpose tool built by someone from the community. But in this particular case, it is problematic because signing a message requires the secret passphrase of the user and we wouldn’t advise anyone to enter their passphrase into a random tool. Therefore, we need to have this feature available in Hub, though at the same time making sure it won’t get in the way of a novice user who has no idea what its purpose is.

    We came to the conclusion that signing a message, in the vast majority of cases, is something that the user is asked to do by a third party. To support that use case, we decided to make signing messages possible via the Lisk launch protocol. This means that anyone can create a special link and share it with the recipient. When the recipient clicks on the link, it opens Lisk Hub on the “Sign message” page with a pre-filled message. The link can contain the message in standard URL encoding, e.g. lisk://sign-message?message=Here%20is%20the%20message. To keep Lisk Hub UI clean, there is no way to access the page from the UI without the link.

    Download the desktop app and keep an eye on the development in real-time by following Lisk Hub on GitHub.

    About the Author:

    Vít Stanislav is a frontend developer for Lisk at Lightcurve and the project lead of Lisk Hub. Previously, he was developing web-based tools for Red Hat. He has plenty of additional frontend experience from developing online learning systems as a member of Adaptive Learning research group at Masaryk University, Brno, Czech Republic. He is committed to making Lisk the blockchain technology with the best user experience.


Log in to reply
 

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.