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 and Call to All JavaScript Developers

    JSConf EU 2018 Recap

    Lightcurve, the consultancy behind Lisk, recently attended and sponsored major JavaScript conference JSConf EU 2018 in Berlin. Major companies, startups and influential figures were present, including giants like Google, Facebook and Microsoft.

    With six team members in attendance, a big booth and eye-catching banners, Lisk made a real splash at the event. Many of the visitors to our booth wanted to know what a blockchain company was doing at a JavaScript conference — we took such questions as opportunities to explain blockchain (many of the developers were unaware of the technology), why Lisk chose to use JavaScript, as well as how JavaScript enables us to make blockchain accessible for people just like them. We also told them about the Lisk Academy as a means to learn all about blockchain.

    The greatest part about the conference was the energy — to see just how engaged developers in the JavaScript community are, coming from all corners of the world to connect over JavaScript and discuss ideas and goals that will shape the future. We even had the chance to meet many influential people, including Redux creator Dan Abramov.

    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.

    Many presentations at the conference had a focus on ethics and how to effectively find solutions to errors, as errors and debugging are part of everyday work life for a programmer. There were also a number of deep dives; for example, GitHub software engineer Shelley Vohr held a talk about asynchronous programming, while web developer Marcy Sutton’s presentation focused on the promotion of accessibility - something that Lisk is all about. We also learned about the next JavaScript features that are expected to change the way we write code — Array.prototype.flatMap, pipeline operator, partial application and bind operator in a talk led by frontend developer William Martins.

    Charlie Gerard, a software developer at ThoughtWorks, gave a presentation and demonstration of brain-controlled JavaScript that was very fascinating — she has been developing an open source JavaScript framework for a brain sensor she has been working on that allows for the control of interfaces or robots with the use of facial expressions and mental commands. Tara Vancil, co-founder of Blue Link Labs, also gave a presentation on the peer-to-peer web — an experiment to re-imagine web publishing without servers. She even built and deployed a website on-stage with only the use of a browser and text editor. It was incredible to hear about the most up-to-date industry trends and happenings from the most influential minds in JavaScript.

    Calling All JavaScript Developers

    One of the biggest reasons we attended JSConf Eu 2018 was to scout talent — particularly, passionate JavaScript developers who want to help disrupt the world with blockchain. We met with at least dozens and dozens of individuals who are interested in applying to work at Lightcurve for Lisk. However, we’d like to take this opportunity to let our community know — and hopefully spread the word — that we are actively hiring developers. The positions currently open that are looking to be filled immediately are:

    • 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

    Version 1.0.0-beta.8

    Download:

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



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

    Next Steps

    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.

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

    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


Log in to reply
 

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