Updated Details lisk
Development Update — Lisk Core 1.0 Beta Testing
Hello Lisk Community,
As stated in our previous development update blog post, keeping you up-to-date about our development progress is very important to us. Today, we have another update regarding the current state of Lisk Core 1.0.0 Betanet testing and the release of Version 1.0.0 Beta 8.
Our developers are working incredibly hard day in and day out. This morning, we had 11 issues remaining on this version, but now, there are only six. Out of these, issue #2080 has, so far, proven to be the most challenging to solve. The Lightcurve development team is currently running a number of tests that are investigating the most efficient way to decrease the number of missed or deleted blocks. The aforementioned issue #2080 needs to be addressed before migrating the Core code to Testnet and Mainnet as the issue would become more visible as the network grows, likely contributing to potential scalability issues. At the forefront of our development goals is a secure, stable and scalable network.
The backport issue relating to release 0.9.15, #2097, has been addressed and successfully merged. Following the network interruption on June 2, we were prompted to fix issue #2098, which was completed earlier today.
We started the day with open issues #1988, #2101, #2102 and #2010, but have since closed them all. #2022 has been open for some time, as tests are currently failing at the integration level. When the issue was tested in a 10 node environment, many blocks were skipped due to a lack of broadhash consensus while tests were running in ‘sync-only mode’ (a mode in which all nodes have broadcast disabled). Following this, the sync process tests were simplified and executed on two nodes — one node that is forging and another node that is being synced based on the forging node. This issue has now been closed.
Based on the feedback from delegates regarding improvements to our technical documentation, Lightcurve developers are contributing to issue #2004, which aims to provide high quality guidelines.
As Jan mentioned in the previous Lisk Core Betanet update, while rigorous testing of the network through Betanet, any issue can arise and have an impact on the timeframes we currently have set. Not only is this the nature of software development, but especially true in the creation of cutting edge and scalable blockchain technology. Having said that, the team is ready for anything and working harder than ever.
The preparations for transitioning to Core 1.0.0 Testnet have already begun. With large scale code quality and migration tests planned, we’re ready to make this transition as seamless as possible.
Core 1.0 is Lisk’s biggest development and release to date. Given its level of importance, we need to pay close attention to every detail. To see our progress in real-time, please follow our Lisk Core GitHub Repository.
We’re on the road to an exciting milestone for Lisk and in that vein, have decided to create a video unpacking all elements of Core 1.0.0 and what it means for the future of our network. Our Motion Designer Julian has already kicked off the preparations and will start shooting next week. However, we will continue to update our dedicated community on the status of Betanet on our social media and community channels.
Thank you again for your continued support!
-The Lisk Team
JSConf EU 2018 Recap
As one would expect from a developer conference, it was very focused on education and knowledge-sharing. In fact, about 15% of the attendees at the conference attended through a scholarship program. There was even a Community Lounge, which served as a spotlight for incredible community initiatives, including lightning talks, VR installments, as well as meet and greets with presenters.
- Frontend Developer s— We are seeking talented frontend developers with a wide variety of skills to help develop and maintain our blockchain applications platform. As a frontend developer, you will be responsible for developing our client user interface using modern practices, maintaining our website, and optimizing a fast, simple and enjoyable experience across the Lisk platform. Learn more about this position and apply here.
- Backend Developers — We’re looking for experienced backend developers with a passion for delivering high assurance code, who have a strong background in building complex mission critical database-powered distributed applications. As backend developer, your primary role would be to help develop and maintain the Lisk Core and Lisk SDK product lines. Learn more about this position and apply here.
- Backend QA Engineer — We’re looking for a backend QA engineer with advanced knowledge of Node.js and PostgreSQL, who can help the Lisk project achieve the very highest standards in code quality, performance and security. Learn more about this position and apply here.
- DevOps Engineer — We’re looking for a DevOps engineer who can assist the Lisk project in configuring and orchestrating its entire development infrastructure. Learn more about this position and apply here.
- Cryptographers — We’re looking for cryptographers with expertise in applied mathematics and blockchain technology, who can help the Lisk project achieve a cryptographically secure and mathematically scalable protocol/solution. Learn more about this position and apply here.
In addition, we’re still hiring for we’re also looking to fill roles in our design, marketing and operations teams. To learn more, please take a look at AngelList.
We will attend many more conferences over the next few months, so be sure to check out our upcoming conference recaps to hear all about them!
-The Lisk Team
Lisk (LSK) Release Wallet v1.0.0-beta.8
Development Update — Lisk Core 1.0 Beta Testing
Hello Lisk Community,
Since last week’s development update, we have continued to make strong progress with beta testing Lisk Core 1.0.0. The Lisk Core team completed all remaining issues on beta.8 earlier this week and released the latest update on Tuesday. A short release summary can be viewed below:
- Issue #2080: This issue was solved through extensive testing to ensure the correct propagation of blocks and peers data over the network, guaranteeing proper consensus and resulting in a decreased number of missed and deleted blocks.
- Issue #2046: We added config.json migration script from version 0.9.x to ensure the update will be a simple process for those who are running nodes.
- Issue #1956 and #1988 were in relation to changes to the API. Issue #1956 was solved to make the use of the node/status/forging endpoint easier, while issue #1988 removed the rank parameter in delegates endpoint.
- Issue #2010 was fixed to make blacklisting IPs of peers connecting to our node via the P2P layer possible.
Since Lisk’s inception, a large part of our community has been involved in the development of the project. This has been particularly evident throughout the beta testing of Lisk Core 1.0.0. The #network channel on Lisk.Chat has been the meeting point for technical discussions; we also receive high quality feedback in this channel. Following the release of Beta.8, community member Simon Warta (Prolina) identified two issues:
- Issue #2126: The rewards for blocks and transactions in the first round (first 101 blocks) had been applied twice to account balances when creating snapshots. On Betanet, it resulted with inconsistent data for a few genesis delegates. Testnet and Mainnet are unaffected. We have published new valid snapshots for Betanet which can be viewed here.
- Issue #2123: With the approval from the community, we removed the extra 0.1 LSK transaction fee for an extra data field — the new functionality introduced by 1.0.0 version. There are five transactions with extra data fields already sent on Betanet — 1.0.0-beta.9 adds them to the exceptions list.
Prior to releasing beta.9, we refactored the entire snapshotting logic to close a number of issues related to snapshot creation together with corresponding tests. As a result, issues #1949, #1927, #1869, #1868 and #1933 #1963 have been resolved, enabling valid snapshots to be taken on betanet.
Once Lisk Core 1.0.0 beta.9 is released at 10:00 CET on Friday, we will kickstart our final round of QA where the team will focus on the following:
- 0.9.16 -> 1.0.0 Mainnet and Testnet data migration, synchronization and snapshot creation.
- 0.9.16 -> 1.0.0 Network migration which will take into account many variants: updating the version manually, using dedicated script for automatic migration, delays in migration etc.
- Large public betanet testing with 500 nodes to test scalability of the network. During this large-scale test, multiple transactions will be broadcasted to confirm that the network behaves as expected when put under stress. The commencement of this process will be announced on Lisk.Chat.
- Test every feature that 1.0.0 introduces.
- We expect the QA process to be finalized by the end of next week. Upon completion, we will announce the expected date of arrival for Testnet.
We will communicate all of these updates and any potential changes via the #announcements and #network channel on Lisk.Chat. Please contact @maciek (Lisk Core Lead), @JuanG (DevOps) or @Mat (Community Manager) if you have any inquiries.
Thank you again for your great feedback and support!
-The Lisk Team
Future in Focus: Sapiens Project
Disclaimer: The Lisk Foundation in no way endorses projects that are interviewed for the series.
This week, the Future in Focus series is getting an inside look into how blockchain technology can revolutionize current certification systems. We’re featuring Italy-based Sapiens Project, a blockchain-based notary system. With Sapiens Project, people will own and have full control over their certificates and records in a format that enables easy sharing. We had the chance to speak with co-founder Matteo Ferrari to learn a bit more about the project.
Jennifer: Please tell me a little more about the history of Sapiens Project and your relationship to blockchain technology. Why did the founders decide that the world needs Sapiens Project?
Matteo: I’m Matteo, a software engineer passionate about new technologies. I became aware of Bitcoin and blockchain technology in early 2011, but like many others, I was initially skeptical. However, at the end of 2011, I had a revelation about the potential of blockchain technology. Since then, I have appreciated, studied, and spread the word about the technology. I’m mainly a C++ developer, so I’ve deeply studied the Bitcoin codebase. Today, I use all my free time to study Bitcoin, the blockchain revolution and work on my projects on Lisk.
Sapiens Project is an ambitious idea that dates back to May 2016, when I decided to channel my passion for Bitcoin and blockchain into creating something to solve practical issues that are present today. People deserve to own and have full control over their certificates and records in a format that enables easily sharing. For this use-case, the blockchain can act as a secure and trustless notary system. Sapiens Platform will support schools, universities and companies, to share their resources and services with a decentralized, cost-effective and secure solution. Users can build a career with collecting badges and certificates. These are the core values behind Sapiens Project.
J: What issues does the academic and certification system market currently face?
M: The current certification system relies on paper and a centralized database, making it an insecure and not instantly verifiable system. It’s like an auto-certification process where the counterpart needs to trust what they receive — or alternatively, make many phone calls or use a mail-in order to verify the authenticity of the certifications. Consequently, these are issues that everyone with a curriculum vitae will face. This all had me thinking about creating a solution using a blockchain-based protocol — at that moment, Sapiens Project was born.
J: What problems will Sapiens Project solve?
M: Digitized academic credentials enable accessibility, shareability, verifiability and traceability of achievements and professional certifications. Anyone with access to the Internet can build his own academic credentials and/or verify others’ careers. Sapiens Platform will provide the tools to issue and verify academic records, professional certifications, achievements, licenses and more. All of these aspects are embedded in a secure shell provided by blockchain technology. Sapiens Platform will also provide a service to create an online marketplace of courses and a Reputation Platform; imagine a LinkedIn-like service where all the certifications are issued and verifiable through Sapiens Platform.
J: Who do you have plans to collaborate and work with to achieve these goals of creating a better world?
M: Sapiens Project will be a community-driven project with rewards for every contribution with Sapiens Tokens (XSP). This will help attract new developers and involve them in the project. Contributions will bring value to the project, and, consequently, value to tokens. It’s a self-powered machine. The underlying Sapiens Token (XSP) will fuel the Sapiens platform. Collaborations with universities will be also important. Collaborations could help bring to life real world use cases, attract new developers and educate students about this new revolutionary technology.
J: Where do you envision Sapiens Project will be in five years?
M: I hope that five years from now, Sapiens Project will be a successful project driven by the community, serving as the main entry point for professionals and employers to eliminate the barriers that currently exist in the certification world.
J: How do you anticipate blockchain technology will change the world? What is its potential?
M: Distributed and trustless systems are powerful tools that will allow for a change in the current power equilibrium in every realm. In existence of centralized systems for thousands of years have led to monopolies of high power concentration. We are here to change this — and that is why, for me, this is a real revolution; a revolution driven by an infallible and unstoppable technology.
Lisk Hub 0.9.0 — Updated Main Menu, Transaction Detail Page Tweaks and More
We are happy to announce the release of Lisk Hub 0.9.0, our desktop application for Windows, MacOS, and Linux. This version brings the following improvements:
- View of votes from non-delegate accounts
- Updated main menu
- Transaction detail page tweaks
- Other UI and UX tweaks
Viewing votes from non-delegate accounts
Lisk Hub 0.9.0 adds a new feature to the account page. Previously, the account page had allowed users to view votes and voters only from delegate accounts. We have added an “Account Info” tab which lists all the delegates that the account voted for — you can easily view the votes from any account regardless of whether or not the account is a delegate account.
Updated main menu
We have updated the main menu icons to take less space, so that the menu fits into most screens with various sizes. We also removed the “More” option, which previously yielded a sidebar with all of the items. In the case of a laptop with really small resolution, the menu will be scrollable for now. We plan to look into how to better optimize the UI on smaller resolution laptops.
Transaction detail page tweaks
This release also contains several UX improvements as we’re always striving to improve the user experience of using Lisk Hub.
A small tweak was made to the way a transaction amount is displayed on the transaction detail page. Previously, a transaction would be displayed with a + or a — based on which account the user came from. But because it could be confusing to some users as to why the amount of the same transaction was sometimes displayed with a + and sometimes with a -, we changed the transaction detail page to display only the number.
We also updated the transaction detail in the Wallet section to behave as a separate page. At first sight, it may look the same, but it has more intuitive behavior in some cases. For example, when previewing a transaction’s details in the Wallet and clicking the Wallet menu item, it goes back to the default view of the Wallet listing all transactions, whereas in the past, it stayed in the transaction detail because it was still considered the same page.
Other UI and UX tweaks
Since Version 0.6.0, we’ve had the FIAT currency converted in the send module to allow users to see the value of LSK they are sending in EUR or USD. We’ve now added the EUR/USD switcher to the settings so that once the user selects one of them, it will always stick to the preferred FIAT currency.
We also added icons to the vote launch protocol landing page to make it even quicker and easier to spot the delegates to be voted or unvoted.
We are aware that there are other UX issues that require a bigger overhaul of some parts of the application. More UX improvements are coming, including a solution to a frequently asked question of how to log out.
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 Core 1.0 Testnet Announcement
Hello Lisk Community,
As expected, we have continued to make strong progress with beta testing Lisk Core 1.0.0. Over the last week, we were mainly focused on testing and documentation. We also finished the last QA round for Core 1.0.0, which focused specifically on checking the migration process from version 0.9.16 to version 1.0.0 and integration with testnet and mainnet data.
We adjusted our Lisk Scripts repository to ensure compatibility with Core 1.0.0 and the capability to fully support the migration process. As a result, issue #2099 was closed. A migration from version 0.9.16 to version 1.0.0 was tested using various scenarios, taking all the edge cases into account. These scenarios including testing migration under various circumstances simulating the real network environment.
During these tests, we spotted minor issues affecting migration scripts:
- Issue #2132: Set proper websocket port during migration
- Issue #92: Clear database table `peers` after migration to avoid conflict between 0.9.x `port` and 1.0.0 `wsPort` fields (peers will be discovered from seed nodes)
- Issue #2141 — Enforce minimum length of five characters for encryption password in config migration script
Completed Large-Scale Public Betanet Test with ~500 Nodes
We also performed and finished a large-scale public betanet test with almost 500 nodes. This past weekend, we executed multiple acceptance and stress tests against betanet, and everything went as planned. The network operated without any interruptions and all transactions were accepted.
Snapshotting and synchronization from scratch tests on nodes running version 1.0.0 with testnet and mainnet databases were also completed. Everything went smoothly while database data remained consistent.
Fully Functional 1.0.0 Node with a Testnet Network Blockchain
You might be wondering how exactly those tests were executed. To begin, we grabbed the latest testnet snapshot that was created using version 0.9.16 and then, we loaded it into the database. After that, we connected the 1.0.0 node directly to that database. When a new version node starts up for the first time, database migration is executed and several database tables are modified, with one even recreated. The result is a fully functional 1.0.0 node with a testnet network blockchain. We copied that database and created a snapshot using version 1.0.0 — this took several days. When the process was finally complete, we carefully compared all of the database tables that we got after snapshotting with the copy. Similar with syncing from scratch tests, but after migration we connected a second node (that was running locally) to the first one and let it sync. Following this, we again compared their databases. We executed the same process with the data from the mainnet blockchain.
The Testnet Release Candidate is Almost Ready
Branch 1.0.0-rc.0 and its corresponding milestone were created, containing the last efforts that need to be made before the actual testnet migration:
- Issue #2145: When migration height is picked, we will need to put it as milestone for rejecting type 6 and 7 transactions. Those transactions are temporarily suspended and will not be accepted with version 1.0.0.
- Issue #2134: Review of README.md file. We need to ensure that the file is up-to-date with all of the 1.0.0-related changes, such as having proper test examples, updated dependencies, etc.
The Next New Minor Release 1.1.0 is Open!
Among our goals is to restore the consistency in shipping new releases while remaining disciplined in assigning new issues with equal workload among the different code areas. In this way, we will be able to deliver following releases consistently. All of the open issues in Lisk Core backlog were revisited, those deemed solved or irrelevant have been closed. Minor releases will be created from the most significant ones that are still open. Release 1.1.0 will mainly focus on updates, minor bug fixes as well as minor code and performance improvements which will move the product closer to desired state.
Announcing Lisk Core 1.0.0 Release to Public Testnet at Block Height 5,594,490
We’re excited to announce we are releasing Lisk Core 1.0.0 to our public testnet network when we reach block height 5,594,490 — the date and time is estimated to be 12:00 CET on Thursday, June 28 with the current network growth speed.
Updated Documentation and Migration Guide Coming June 25
Ahead of the testnet release on Thursday, we will be putting out the comprehensive Lisk Documentation and Migration Guide on Monday, June 25, to ensure that everyone will stay up-to-date on our products and have a smooth migration experience with Lisk Core 1.0.0.
Reminder of Upcoming Reddit AMA
In an effort to address any questions surrounding the release of testnet, the Lightcurve Development Team will be hosting a Reddit AMA on the topic of Lisk Core 1.0.0. Next week, we will announce the date of the long-awaited AMA.
As always, thank you to the community for the continued support!
-The Lisk Team
Introducing the Lisk Documentation and Migration Guide
The Lisk team has been working diligently on our biggest accomplishment to date — Lisk Core 1.0. We’re nearly at the finish line. However, ahead of the release of Lisk Core 1.0 to testnet on Thursday, June 28, we’d like to share the updated Lisk Documentation and Migration Guide to ensure that everyone is able to migrate and be aware of the changes and updates in our products.
The Lisk Documentation and Migration Guide contains a series of comprehensive documentation for the Lisk Protocol, Lisk Core, Lisk Elements, Lisk Commander, Lisk Hub and Lisk Explorer, to help you begin working with Lisk as quickly as possible. In this blog post, we will break down the various sections of the documentation and guides to help with the on-boarding of the latest versions of our products and teach you the basics, as well as more complicated aspects, of the network.
In this section, we provide an overview of the Lisk Protocol. Here you can learn all about the fundamentals of Lisk. We thoroughly explain the ins and outs of the Lisk Consensus Algorithm, how Lisk secures its network, such as the use of cryptographic hashing to secure all aspects of the system, how the blocks in our ecosystem function, how transactions work and available features related to transactions, and finally, how peer-to-peer communication serves as a vital function within the network. This form of communication allows for the facilitation of network consensus, block propagation and transaction propagation.
Lisk Core is the application that implements the Lisk Protocol. It is necessary in order to run a node — in turn, enabling participation in the network. We will initially release Core 1.0 Testnet to perform actions in testing mode before reaching the real network. New versions and fixes of Lisk Core are tested here before they are released to Mainnet. Mainnet serves as the real Lisk ecosystem, where users are able to transfer money from one account to another, register accounts as delegates or vote for other delegates.
The Lisk Core section of the documentation details how to prepare a system for the installation of Lisk Core, the prerequisites that are needed, how to install it and upgrade it in the future. We’ve also included a comprehensive guide to troubleshooting in case any issues come up. And finally, this section also contains a Lisk Core User Guide for managing and configuring Lisk Core nodes. If you are a new user, we recommend you start with the general configuration. If you wish to run a delegate or public node, extra configuration will be necessary.
There are a significant number of changes that come with Lisk Core 1.0. During the course of Lisk Core development, we have introduced some changes in the configuration which are not backwards compatible and are strictly related to the version you are running. The Lisk Core Migration section describes each of those changes in detail.
We have completely changed and improved the Lisk API, which you can read about in great detail under the Lisk Core API User Guide with a helpful comparison chart for all endpoints — previous and new ones.
This section includes a step-by-step guide on how to set up Lisk Elements, which prerequisites are needed to install it, and installing instructions. You can also learn how to upgrade the installation, and finally, how to properly use Lisk Elements with the Lisk Elements User Guide. There are also comprehensive subsections about the Lisk Elements’ API Client, Constants, Cryptography, Passphrase, and Transactions.
Lisk Commander serves as a low entry point and the most convenient tool for developers who are looking for an efficient way of coding with a command line interface (CLI). With Lisk Commander, it is easier and quicker to plug new commands into the CLI than building a Graphical User Interface (GUI) around every command. This will facilitate delegates, node operators, contributors to the Lisk codebase, developers using Lisk’s infrastructure (and anyone else who’s interested) to make use of Lisk’s functionality from the command line with ease. Lisk Commander allows you to communicate with a remote or local node and carry out Lisk-related functionality using an interactive or non-interactive command line tool. Going forward, we’ll be adding more commands to provide a comprehensive suite for all your Lisk-related needs.
This section explains how to set up Lisk Commander, which prerequisites are needed to install it, and installing instructions. You can also learn how to upgrade the installation, and finally, how to properly use and configure Lisk Commander with the Lisk Commander User Guide. We have also dedicated subsections to Lisk Commander’s Sensitive Inputs and Commands.
Lisk Hub is an all-in-one solution to manage your Lisk ID, access and send LSK tokens, sign messages, and vote for delegates. It combines functionality from the former wallet and blockchain explorer. In the future, Lisk Hub will feature a DEX (decentralized exchange), sidechain registration and the ability to launch your own ICO.
You can download Lisk Hub in this section. After downloading Lisk Hub to your device, you will be able to participate in the Lisk network. The app will automatically notify you when latest versions are available. But in case you may have dismissed upgrades, you can check upgrade availabilities by going to “Help” and “Check for updates” in your menu bar.
Lisk Explorer is a tool for visualizing and presenting the information and activity surrounding the Lisk Blockchain. It can be used to gather information about particular blocks and transactions, and general information about the whole network and delegates’ status. Components like Network Monitor and Delegate Monitor show the status of the whole ecosystem in real-time.
This section includes detailed steps on how to set up Lisk Explorer, which prerequisites are needed to install it, and installing instructions. You can also learn how to properly use Lisk Explorer with the Lisk Explorer User Guide with its various tools and API.
We hope you find the Lisk Documentation and Migration Guide helpful! Your feedback is very important to us — please let us know if you have any thoughts or contributions for the guide.
Follow us on our social media and chat channels for the latest developments. Thank you again to our community for the continuous support!
-The Lisk Team
Lisk (LSK) Release Wallet Version 1.0.0-rc.1
Lisk - Tech Open Air 2018 Recap
Last week, Berlin hosted one of Europe’s largest technology conferences with over 20,000 attendees — Tech Open Air 2018. For the first time ever, this year’s conference placed a major focus on blockchain with a dedicated day and stage to the technology. At Tech Open Air 2017, there was only a handful of blockchain-related talks that were very general and barely scratched the surface. Lisk both sponsored and attended the event this year, which was held at Funkhaus, an enormous historical venue on the riverbanks of the Spree.
The conference was casual, in line with an authentic Berlin experience. It was buzzing with all types of companies present, including the likes of Google, SoundCloud, Axel Springer, Polaroid, Klarna and many more. The place was so crowded; it took people over an hour to claim their entry tickets.
Lisk had a huge presence with two large booths, inside and outside. Several team members represented each booth. The team inside focused on sharing Lisk’s story with attendees. All attendees had the chance to win up to 10 LSK after taking the blockchain quiz we created. Our outside booth was primarily focused on scouting potential talent for Lightcurve. We received many applications from enthusiastic candidates.
Lisk was also featured on stage with Marketing Manager Thomas delivering a twenty-minute presentation on the Innovation Stage in the middle of the conference floor about Lisk’s ecosystem, vision and strategy. He also explained how blockchain marketing differs from traditional startup marketing. The presentation was very well-received by the audience.
People from nearly all backgrounds attended the conference, but we were particularly interested in meeting blockchain pioneers and members of the startup scene in Berlin. Crowds of people stopped by the Lisk booths, including people from the likes of SAP, Siemens, Daimler, and those working with independent banks that are interested in innovation and implementing blockchain technology into their businesses. We ran out of businesses are a record rate! We were asked many questions about Lisk — both general as well as technical.
And of course, there were many journalists at Tech Open Air. Lisk received a great deal of media interest; several members of the team were interviewed both during and after the conference. We even had several journalists come by our Berlin office following the conclusion of the conference for office tours.
Even though the team was busy spreading the word of Lisk and networking, we tried our best to attend presentations.
There were talks about how banks and crypto exchanges could work together to create safer trading environments for users, the use of blockchain technology in the automobile industry, and many, many others. We were incredibly grateful to share the room with such bright individuals who will make a true impact in the world.
We’re looking forward to attending similarly great conferences this summer! Several members of the team are currently at the Blockchain Expo in Amsterdam, where Cryptographer Iker sat on a panel titled “How Can Developers Make the Most of the Blockchain Opportunity?” Thomas gave a presentation titled “Lisk: Enabling Blockchain Creators.” Up next this month is Distribute 2018 in Hamburg, CEO and cofounder Max will be speaking. We are also hosting the Lisk tour in Poland, where several team members will hold three meetups — Krakow on July 3, Wroclaw on July 4, and Warsaw on July 5. We’re looking forward to connecting with our Polish community!
Although we are still looking for developers to join our Development Team, we’ve opened many new positions on our Marketing Team.
We are currently accepting applications for:
- Community Manager (Germany market) — We are looking for a Community Manager to join our team who can help us grow and nurture Lisk’s presence and engagement across several online and offline channels in Germany and abroad. You will be responsible for managing all community communications, orchestrating events and customer support. Therefore, we are looking for candidates who have exceptional communication skills in German and English, in-depth experience with community engagement and equally important, knowledge about Blockchain technology.
- Community Manager (Dutch market) — We are looking for a Community Manager to join our team who can help us grow and nurture Lisk’s presence and engagement across several online and offline channels in the Netherlands and abroad. You will be responsible for managing all community communications, orchestrating events and customer support. Therefore, we are looking for candidates who have exceptional communication skills in Dutch and English, in-depth experience with community engagement and equally important, knowledge about Blockchain technology.
- Community Manager (UK market) — We are looking for a Community Manager to join our team who can help us grow and nurture Lisk’s presence and engagement across several online and offline channels in the United Kingdom and abroad. You will be responsible for managing all community communications, orchestrating events and customer support. Therefore, we are looking for candidates who have exceptional communication skills in English, in-depth experience with community engagement and equally important, knowledge about Blockchain technology.
- Tech Evangelist — Lisk is seeking a well-rounded and experienced Tech Evangelist to join our rapidly growing team. We are searching for somebody with a passion for blockchain technology, basic understanding of the Lisk project and community, as well as proven experience in getting key stakeholders excited about complex technological ideas.
- Junior Performance Marketing Manager — As a Junior Performance Marketing Manager at Lisk, you will be responsible for managing paid marketing campaigns across a variety of online channels such as Adwords (Google, YouTube) and Facebook. We are looking for someone who can effectively oversee the paid marketing budget and analyze data to maximize quality traffic to Lisk.io.
- Senior Copywriter — Blockchain can be intimidating, technically complex and comes with unique UX challenges. That’s why we’re seeking a Senior Copywriter to help us simplify and effectively articulate copy across all digital touchpoints. For this to be realistic, we expect the successful candidate to have experience copywriting for a tech startup across website and mobile interfaces.
To learn more, please take a look at AngelList.
We look forward to keeping you posted on the upcoming meetups and conferences we attend!
-The Lisk Team
Lisk Hub updateVersion 0.10.0
- Remove the explorer page and menu item #896#831
- Autosuggest should update input placeholder - Delegate Search #745#900
- Add "recent searches" to search autosuggest #895#745) #865#745) #834#830
- Support usage of custom node #463#745 #929#976
- Autosuggest should not colide with main content in signin - Delegate Search #745#958
- Recent searches show addresses when delegate names were searched #950#949
- Rank 101 is labeled standby, should be active #948#947
- Autosuggest should redirect properly when not using suggested results - Delegate search #745#946
- Triggering a request with autosuggest makes account visuals and info not visible - Delegate Search#745#928
- Add follow account functionality to account page #907#906
- Delegate search with autosuggest should be covered by unit/integration/e2e tests - Delegate Search (#745#835
- Use jenkins shared library #923#905
- Implement edit and delete mode of followed accounts #904#903
- Create redux logic for followed accounts #902#890
- Styling of Sign message #880#879
- Refactor API requests from middlewares to actions #770#976 #977slaweet)
- Onboarding overlay should not allow to click on UI - Closes 957 #963faival)
- Don't hide explorer elements while loading - Closes #928#961 (faival#958 #960faival)
- Use search value for saving into recent searches - Closes #950#959 (faival#947 #954michaeltomasik)
- Redirect to valid entity results page when no autosuggestion result used - Closes #946#953 (faival#948 #952michaeltomasik)
- Change text in Delegate Details page - Closes #949#951 (michaeltomasik#935 (ginacontrino#906 #933ginacontrino)
- Add followed accounts to account profile page - Closes #907#930 (ginacontrino#896 #919faival)
- Implement editing and deleting followed account - Closes #904#925 (ginacontrino#923 #924abelboldu)
- Verify that passphrase used belongs to active account - Cooses #921#922 (michaeltomasik#903 #890#905 #918ginacontrino)
- Add redux logic for followed accounts - Closes #902#912 (ginacontrino#895 #910faival)
- Styling of sign message - Closes #880#909 (michaeltomasik#879 #908michaeltomasik)
- Update autosuggest input placeholder with suggested results - Closes #900#901 (faival#830 #887michaeltomasik)
- Limit linux builds to x86_64 #885abelboldu)
- Refactor api calls in middlewares - Closes #770#882 (ginacontrino#834, #835#865 #878faival)vi
Development Update — Road to Core 1.0 Mainnet
Hello Lisk Community!
We’re getting closer and closer to the release of Lisk Core 1.0.0 to Mainnet! We want to assure the community that we are working diligently while also taking the appropriate time and measures to ensure that the release is of the highest quality.
The steps include making sure that all of our products — Lisk Elements, Lisk Explorer, Lisk Commander and Lisk Hub — are compatible with Lisk Core 1.0.0. The first compatible release candidate of Lisk Elements, 1.0.0-rc.0, is planned for release today. Regarding Lisk Commander, the current release candidate, 1.0.0-rc.0, is already compatible. The latest version of Lisk Explorer — 2.1.2 — was released today. For Lisk Elements and Lisk Commander, the next minor versions are already under development. Although we already have established communication channels with most major exchanges, we are continuing to reach others who we are not currently in touch with yet. Streamlined communication is the key to ensuring the migration is able to occur without issues; we will offer them any necessary assistance with this process.
Continuous updates & improvements to Documentation
In preparation for the release of Lisk Core 1.0.0 to Mainnet, we’re still constantly working to improve our documentation. We recently added a section about troubleshooting to provide solutions for the most common issues that can occur during the migration process, installation process and node management.
In the most recent version of the Troubleshooting Guide, you can learn what to do in the following cases:
- Installation script fails during binary installation because the PostgreSQL server is already installed
- npm install command fails because of an error related to the build process of sodium dependency
- Nothing is shown in the console after starting the Lisk Core application
- Delegate not found error message when trying to enable forging on the node
As stated in last week’s development update, Quality Assurance for Core 1.1.0 is moving as planned. This phase is expected to be completed by next week.
With Lisk Core boasting the largest development team at Lightcurve, we’re able to fully focus on the completion of 1.0.0 as well working on the releases that will follow; 1.1.0 and 1.2.0.
Further changes in the Core 1.2.0 version include:
Issue #1647: There was an inconsistency in our database schema as we’d used different data types among different tables for storing round numbers. After careful deliberation, we decided that sticking to the integer data type is sufficient.
Issue #750: We discovered an inconsistency related to the usage of this variable and passing scope when performing verification for different transaction types. We simplified the code by removing the usage of this and adjusting corresponding function calls to no longer pass the scope variable.
Issue #2125: We have a few different test types as part of our automated test suite. One of the test types involves integration testing. Integration tests spin up a small network of ten peers on a single machine to perform a series of tests focusing on stable communication between the peers, data integrity within the different nodes, proper transaction and blocks broadcasting. They also include tests for some features such as peers blacklisting, behavior of the nodes when they are run behind a firewall and a few others. We’ve experienced issues related to the stability of those tests for some time and because of that, we have decided to review them in order to figure out the actual cause of this behavior. As a result, we refactored those tests to ensure they can scale further. We’ve also identified a few test cases that need to be fixed and for this, we will open separate issues.
1. Complete and perform QA on Lisk Core 1.0.0 2nd Release Candidate
Given that Mainnet is far more important than Testnet, our biggest focus right now is to complete and then perform QA on the second release candidate of Core 1.0.0, which we are working on for release to Testnet.
2. Include new security features in Lisk Core 1.0.0
We decided to include a few additional features in the Lisk Core 1.0.0 release to avert possible security risks related to the migration process. Issues are already open in GitHub for the corresponding 1.0.0-rc.2 milestone, however, we will describe them in detail in next week’s development update.
3. Update your tools to be compatible with 1.0.0 new REST API.
This release will be the final release before the actual Mainnet migration. Despite all of the steps that need to be taken prior to this event, it will take significantly less time to release Lisk Core 1.0.0 to Mainnet than it did to release Lisk Core 1.0.0 to Testnet. Users will still have a little more time to update their tools to be compatible with 1.0.0 new REST API.
4. Continue working on open issues for Lisk Core 1.2.0
We will continue to work on the open issues for version 1.2.0, which we will discuss in further detail in next week’s Weekly Update. And finally, please be sure to check the Lisk Documentation and Guidelines from time to time for continuous updates and improvements.
As always, please stay up-to-date via the #announcements and #network channels on Lisk.Chat and please contact maciek (Lisk Core Lead), JuanG (DevOps) or Mat (Community Manager) if you have any inquiries.
Thank you again for the continued support!
-The Lisk Team
Lisk explorer Update v2.1.3-rc.0
Lisk Hub Pre Release Version 1.0.0-rc.1
- Add support for reference field in transactions #813
- Settings menu item disabled when not logged in and delegates section enabled #1036#1030
- UI under the onboarding overlay reacts to clicking #957#956
- Activity: Delegate statistics: Number of blocks undefined #1034#1033
- Pending transaction appears/disappears/reappears after a while - Core 1.0.0 Migration #1029#1024
- Locking an account should have e2e tests - Core 1.0.0 Migration #1022#1019
- Send: reference field not showing on confirmation screen #1018#995
- Fix saved accounts after 1.0 API migration #991#975
- Voting feature should pass e2e - Voting - 1.0.0 Migration #812#969
- Register second passphrase feature should pass e2e- 1.0.0 Migration #812#968
- Send feature should pass e2e - 1.0.0 Migration #967#942
- API independent features should pass all e2e related tests - Core 1.0.0 Migration #941#812 #940#812 #939#937
Merged pull requests:
- Fix transaction amount on pending non-send transactions - Close #1033#1045 (slaweet#1030 #1043michaeltomasik)
- Fix main menu to have always enabled Settings item - Closes #1036#1041 (slaweet#1034 #1039slaweet)
- Fix pending transaction disappearing/reappearing - Closes #1029#1038 (faival#1033 #1037slaweet)
- Fix remove passphrase when locking an account - Closes #1022#1031 #1027faival)
- Show reference field on confirmation screen - Closes #1018#1026 (michaeltomasik#1024 #1025faival)
- Enable signMessage e2e tests - Closes #1019#1021 (faival#967 #1020faival)
- Register delegate should pass e2e tests migration 1.0.0 - Closes #940#1017 (faival#995 #1016faival)
- Login related unit tests should be reenabled - Closes #975#994 (yasharAyari#991 #993slaweet)
- Api independent features should pass all e2e - Closes #941#989 (yasharAyari#942 #988slaweet)
- Add reference field - Closes #813#986 (michaeltomasik#969 #974faival)
- Fix second passphrase migration 1.0.0 - Closes #968#973 (michaeltomasik#939 #971faival)
- Migrate Login to work with lisk-elements 1.0 - Closes #937#966 (faival#956 #962michaeltomasik)
- Send features, show single Transactions migration to 1.0.0 - Closes #967#970 (michaeltomasik)