Updated Details lisk
Lisk (LSK) Release Version 0.9.10
Merged pull requests:
- Move cb to last argument for blocks/chain/applyBlock
- 0.9.10 - Multisig transactions from the same account bug resolution
- Decreased amount of LSK transferred to multi account
- Rewind fork 5-3 fix
- Bug resolution for multisignature registration transaction
- Duplicated delegates fix with silent validation failure
Lisk (LSK) Release explorer Version 1.3.1
- Remove obsolete and unstable Api tests #314#316
- Remove obsolete and unstable Api tests #314#316
- Add analytic meta tag #308#309
- Run eslint in Jenkins build pipeline #311#320
Merged pull requests:
- Skip obsolete tests - Closes #314 #315reyraa)
- Fix some minor regressions - Closes #316 #317reyraa)
- Add custom meta tag - Closes #308 #313reyraa)
- Add eslint no-exclusive-tests rule - Closes #309 #310reyraa)
- Add eslint step to Jenkinsfile - Closes #311 #312reyraa)
- Search performance improvement - Closes #320 #321reyraa)
Lisk (LSK) Release Nano Wallet Version 1.2.1
- Cannot "Vote(+1/-1)" with "My votes (101)" #932#928
- Searching for a delegate in the voting system "unchecks" all delegates #916#914
- Show passphrase icon intersects with the passsphrase #913#912
- Vote limit error toast is triggered incorrectly #911#910
- Launch protocol doesn't work on Linux #909#907
Merged pull requests:
- Fix vote count computation for vote button disable - Closes #932 #933slaweet)
- Fix launch protocol on Linux - Closes #909 #931slaweet)
- Fix error message in about dialog - Closes #907 #923slaweet)
- Retain votes after cleaned search box - Closes #916 #922reyraa)
- Fix transaction and port bug on custom node - Closes #910 #921ginacontrino)
- Custom node translation doesn't update - Closes #914 #920yasharAyari)
- Show passphrase icon intersects with the passsphrase - Closes #913 #919yasharAyari)
- Make commands for building packages from scratch on each platform - Closes #912 #918slaweet)
- Fix incorrectly triggered error toast in voting - Closes #911 #915ginacontrino)
Lisk - Announcing Updated Ambassador Program and Local Meetup Initiative
We have been receiving a lot of interest from community members around the world wanting to host Lisk Meetups locally. The community has become increasingly active over the last few months. We’ve also seen more community members take initiative and host Lisk-focused meetups in the US, Europe, Asia and Australia that have drawn many attendees. We feel fortunate that so many people have taken great interest in Lisk.
Back in March of 2016, Lisk launched a Country Ambassador initiative that nominated ambitious community members who were interested in representing Lisk. The goal of the initiative was to strengthen the bond between the Lisk core team and local communities across the world. In addition, we had in mind to create a grassroots effort in spreading awareness of Lisk to those interested in the idea of decentralized applications and custom blockchains.
The Lisk Ambassador initiative will continue, but with some major changes:
- Due to the increase of community member involvement and requests to be an ambassador, we have decided to open up the Lisk Ambassador Program to anyone who is committed to hosting local meetups.
- This means that there will no longer be dedicated Lisk Country Ambassadors since there will be an opportunity to be more than one Ambassador per country.
- It also means that the private Lisk Country Ambassador channel in Lisk.chat will be replaced by a public Lisk Ambassador channel. This is in line with our goal to make Lisk an open source grassroots effort.
- No, this doesn’t mean that if you were formerly a Lisk Country Ambassador that we don’t acknowledge your efforts. :)
- The focus of the Lisk Ambassador program will be to host local meetups with incentives for hosting successful meetups.
How does Lisk support Ambassadors in their efforts?
There are many incentives for becoming a Lisk Ambassador who hosts local meetups.
- You will not only become a part of the greater Lisk family, but it will also give you a chance to become a leader in your local Blockchain community.
- Lisk will promote your event on social media channels as well as the newsletter.
- On a case by case basis, we also offer funding to help cover costs.
- Lisk can also introduce you to other Lisk community members in your area if you do not know who they are already.
- If it is possible, we will try to have a Lisk team member attend the event in person or via Skype.
- In the near future, there will be a Lisk Ambassador Kit available to purchase that will include Lisk merchandise, presentation slides, online marketing materials and more.
- We will also soon have a dedicated community manager who will become the point of contact for all Lisk enthusiasts that are planning to organize local meetups.
Why are we making changes?
The changes outlined above will enable the Lisk Ambassador program to be more inclusive and scalable. We would like to give more Lisk enthusiasts the opportunity to become more active, whether it be on social media channels or as hosts of Lisk meetups in their community. We would like to call these individuals Lisk Ambassadors. This is not the same as a Country Ambassador — anyone dedicated to hosting occasional Lisk meetups can now become a Lisk Ambassador.
Thank you to our past and present Ambassadors for paving the way!
- Luiz Chen, China
- Daniel Vassilev, Australia
- Samuel Heinrichs, Brazil
- John Cortesi, France
- Daniel B., Germany
- Petros Anagnostou, Greece
- Lisk Italian Group
- Nick F., Netherlands
- JM N. Erestain, Philippines
- Joel Fernández, Puerto Rico
- Stefan Neagu, Romania
- Denis Smirnov, Russia
- Kostyantyn Ahafontsev, Ukraine
- Shariq Hashmi, UAE
- Edward Trosclair, USA
Introducing Lisk Meetup Guidelines
In order to make it easy for anyone to host a successful Lisk meetup, we have put together a set of guidelines. By following Lisk’s meetup guidelines, you are directly involved in helping maintain high-quality standards for all Lisk meetups globally. It is important to follow the steps we’ve outlined because you, as a host, are expected to uphold the Lisk brand image.
In our comprehensive guidelines, we provide step-by-step instructions on how to create your local Lisk Meetup. We also provide tips on how to get your meetup sponsored, what to prepare before the day of the meetup, guidelines to follow during a meetup, as well as steps to take after the meetup. A sign-in sheet template that can be printed out for your meetup is also included.
As we’ve stated in previous blog posts, many improvements are yet to come. For example, we will be releasing an official Lisk Ambassador Kit for purchase with merchandise, presentation slides and marketing materials. It will be released around the time of our rebrand.
Please download the Lisk Meetup Guidelines via Google Docs.
Lisk (LSK) Release explorer Version 1.3.2
- Explorer fails to find the publicKey randomly #337#333
- Improve version sorting in networkMonitor #335#330
Merged pull requests:
- Fix an issue with PublicKey
regexin search Api - Closes #337 #338reyraa)
- Improvements in custom sort function - Closes #335 #336reyraa)
- Fix best height - Closes #333 #334reyraa)
- Add Coincheck and Iconomi to known addresses - Closes #330 #331reyraa)
Lisk Explorer 1.4.0 — Enhanced UX/UI, Improved Performance, Bug Fixes, and Website Analytics
We’re happy to announce the release of Lisk Explorer 1.4.0 after the recent patches of 1.3.1 and 1.3.2. In the last two patch releases, we’ve introduced multiple enhancements in our client-side AngularJS based application and on our server side Node.js application. With the introduction of 1.4.0, we have made several UX/UI improvements.
UX/UI Enhancements — Peers Statistics, Network Status and Search Box
We appreciate that it wasn’t easy enough to grasp the meaning of the numbers in peers statistics, so we did all we could to remedy this. We tried different designs and eventually came up with a more informative and consistent approach to illustrate the number and percentage of peers running different height on different operating systems and Lisk Core versions.
In addition, we discovered that the network status is a frequently checked element that warranted a dedicated space on the homepage. As a result, we added a section right below the header to make the network status prominent.
The last change that you will notice in this release is the design of the search box. We’ve implemented a more consistent and appealing design to improve your search experience..
We enhanced our code quality by removing many unnecessary API calls or iteration over our data lists. With these changes made, we’ve achieved a notable improvement in the load time of our pages and components. We still have a long road to go in this aspect of the Explorer, but the aim is to create the fastest Explorer in the blockchain world, with an unrivalled user experience, and we are rapidly getting there.
We updated our code base to ES6 standards and have eliminated many outdated libraries previously used to provide some methods which are presently available in ES6. We performed this migration in order to be able to upgrade to new libraries like React which are currently utilized in Lisk Nano. In these two patch releases we’ve essentially fixed almost all the bugs we spotted or that were reported by our eagle-eyed community.
Introduction of Standards
Eslint ensures our code is easily read for any developer in our community.
Last but not least, we’ve introduced a change which may seem to be somewhat minor, but it makes it considerably easier for webmasters to deploy Explorer on their servers, with their custom Analytic service name and client ID to keep track of statistics of their users.
Analytic services like Google Analytics provide facilities for anonymous statistics of their users, such as the number of visits in every page for a random time period.
About the Author: Ali Haghighatkhah is frontend developer at lightcurve with a hand in painting and writing. In his spare time, Ali enjoys developing mobile games and at work he is the project lead on Lisk Explorer. Here are a few of the honorably mentioned websites that he’s developed:
Coyote - 12points.fr - Awwwards Nominee
12points is the biggest survey regarding the driving licence of the French people.www.awwwards.com
Red Bull Kumite - Awwwards Nominee
The biggest VS Fighting champions will be present. With a unique goal : decide who will be the best. Who will win the…www.awwwards.com
Nocibe #LoveMessage - Awwwards Nominee
Trick your boyfriend for Valentine's day with a subliminal message. Choose a crazy video, add your custom message…www.awwwards.com
Email: [email protected]
- Dapp deposit/withdrawal types are wrong #353
- Switch static code analysis from jshint to eslint #105#259
- Perform automatic eslint fixings #260#262
- Apply code changes and enhancements required to meet eslint rules for utils #265#266
- Apply code changes and enhancements required to meet eslint rules for benchmarks #268#271
- Apply code changes and enhancements required to meet eslint rules for api sockets #273#275
- Apply code changes and enhancements required to meet eslint rules for src #276#279
- Refactor repeated codes in Api #281#300
- Make redis database number configurable #324#341
- Run eslint on all the source files including configs #343#345
- Data provided in network monitor page is confusing #347#349
- Create Pull request template #351
Merged pull requests:
- Optimise images - Close #275 #264albinekcom)
- Make redis database number configurable - Close #324 #325fchavant)
- changes to enable concurrent runs - Close #300 #329Nazgolze)
- Add Changelly to known addresses - Closes #341 #342reyraa)
- Cleanup grunt file - #345 #346reyraa)
- Run Eslint on all the source files - Closes #343 #344reyraa)
- Use a more informative design for peers statistics - Closes #347 #348reyraa)
- Improve network statistics readability - Closes #349 #350reyraa)
- Create Pull request template - Closes #351 #352reyraa)
- Fix transaction types - Closes #353 #354reyraa)
- Replace jshint with eslint - Closes #259 #258reyraa)
- Perform automatic eslint fixings - Closes #260 #261reyraa)
- Eslint fixings in libs directory - Closes #262 #263reyraa)
- Eslint fixings in utils directory- Closes #265 #267reyraa)
- Eslint fixings in benchmarks directory - Closes #268 #269reyraa)
- Eslint fixings in Api directory - Closes #266 #270reyraa)
- Eslint fixings in src/components directory - Closes #271 #272reyraa)
- Eslint fixings in src directory - Closes #276 #278reyraa)
- Eslint fixings in all remaining files directory - Closes #279 #280reyraa)
- Refactor repeated codes in Api - Closes #281 #282reyraa)
Lisk (LSK) Pre - Release Nano Wallet Version 1.3.0-rc.1
- Add support for message encryption and decryption #536#573
- Notify users when there is new version available #196
- Account switching to a custom node account doesn't work #995#986
- Signed Message Invalid when Created from Saved Nano Account (Not Already Logged In) #981#980
- Make react app compatible for all browsers #968#957
- Encrypt/decrypt message menu items are broken #948#946
- Lisk Nano throw an error if config.json is corrupted #942#935
- Add dev-app-update.yml file #996#989
- Add German translations for strings added in 1.3.0 #983#978
- Review and refactor e2e tests #973#961
- Build recovery slack notifications don’t work #944#939
- Move networks.js to src/constants #926#925
- Upgrade to React 16 #902#900
- Add eslint no-exclusive-tests rule #893#892
- Make e2e tests more stable #878#859
- Setup David for dependency management #844#843
- Setup i18n-scanner to run in webpack #831#751
- Check alert dialog text e2e step doesn't work #734#733
- Don't unit test component methods directly #703#620
Merged pull requests:
- Add app update file - Closes #996 #998ginacontrino)
- Fix account switching with custom node - Closes #995 #997slaweet)
- Add German translations for strings added in 1.3.0 - Closes #983 #994ginacontrino)
- Add eslint no-exclusive-tests rule - Closes #893 #993slaweet)
- Fix i18n of second passphrase registration authenticate step #992slaweet)
- Long Passphrase bug fix - Closes #986 #988joerodrig)
- Authenticate the user before setting second passphrase - Closes #980 #985reyraa)
- Update message signature with passphrase input value - Closes #981 #984slaweet)
- Do not show delegate registration form for a delegate - Closes #946 #982joerodrig)
- Pilot integration tests - Closes #733 #977yasharAyari)
- Use core port number > 4000 to prevent side effects #976fchavant)
- Review e2e tests - Closes #973 #974slaweet)
- Write unit tests for electron code - Closes #900 #970ginacontrino)
- Remove outdated labels from Jenkinsfile #969slaweet)
- Allow to save and manage multiple accounts in local storage - Closes #573 #966slaweet)
- Cleanup eslint paths #965slaweet)
- Set meta viewport to fix size on mobile devices #964slaweet)
- Use variable for job name instead of hardcoded string in Jenkinsfile - Closes #961 #962fchavant)
- Setup testnet tests - Closes #925 #960ginacontrino)
- Setup David for dependency management - Closes #844 #959yasharAyari)
- Fix broken "save account" e2e scenario - Closes #957 #958slaweet)
- Add hard-source-webpack-plugin #956slaweet)
- Create CODE_OF_CONDUCT.md #955slaweet)
- Remove direct calls to methods of components in unit tests - Closes #703 #954reyraa)
- Fix styles of encrypt/decrypt menu items - Closes #948 #952slaweet)
- Refactor i18n - Closes #892 #951ginacontrino)
- Fix recovery notification - Closes #944 #950fchavant)
- Convert i18n-scanner command into a webpack plugin - Closes #831 #949slaweet)
- Add gitter badge to README.md #947slaweet)
- Move networks.js to src/constants - Closes #926 #945yasharAyari)
- Fix exception throwing - Close 942 #943alepop)
- Unskip tests and solve TODOs - Closes #751 #941ginacontrino)
- Create pull request template - Closes #939 #940slaweet)
- Upgrade to react 16 - Closes #902 #938yasharAyari)
- Add DevTools Keyboard Shortcut #937V1shvesh)
- Fix randomly failing delegate test - Closes #859 #934ginacontrino)
- Make e2e tests more stable - Closes #878 #890slaweet)
- Use Websocket to get new transactions - Closes #843 #889ginacontrino)
- Setup auto update - Closes #196 #765slaweet)