Added logic to prevent LRT pipelines from self triggering
On February 3, 2020 we released eosio.contracts v1.9.1. With this update, a number of bugfixes and changes were introduced.
We identified and patched a bug in the producer scheduling logic in v1.9.0 of the system contract that, when triggered, include a pause in payments to block producers, block producer changes, and the closing of name auction. A simple update to v1.9.1 resolves this issue.
Introduced logic to retry downloading the CDT binary, updated built/test commands to support the new logic, and improved logging output
Cleaned details in annotations to be compatible with mdjavadoc generator
It is important to note that, In this update, the eosio.system and eosio.bios contracts contained within can only be deployed on an EOSIO blockchain following the activation of the WTMSIG_BLOCK_SIGNATURES consensus upgrade. If starting a fresh blockchain, older versions of the eosio.bios contract (v1.7.x or v1.8.x) may be used to activate this protocol feature.
Another February 7, 2020 release is the EOS JS v21.0.0 release candidate. This release candidate focuses on enhancing the elliptic library, introduces new commands as well as the use of minified files for production environments, and other changes.
Introduced helper functions to perform actions that sign, verify, and recovery key signatures
Deprecated table_key parameter and replaced with index_position
Added yarn build-web command that creates both debug and minified files in dist_web
Introduced recommendation to use minified files as opposed to debug files in production environments to reduce load times on end user
Merged pull request #649 from EOSIO/develop-version-bump to lock versions
Added functions from eosjs-ecc to PrivateKey/PublicKey/Signature classes to handle format conversions and call elliptical functions
Removed the Travis CI configuration pending future updates
Introduced zero padding to r and s signatures so they will generate signatures with the proper amount of bytes
Removed certain warnings and related documentation
Added IMPORTANT.md and changed related section in the README.md document
Adjusted minified and debug files created by yarn build-web to follow new minified file convention
Removed usages of the now deprecated table_key command
Updated documentation to properly reference the new doc version
In addition, on February 7, 2020 we updated the repository for Elemental Battles, an educational tutorial and card game, to eosio-card-game-repo v1.1.10.
Tropical Stay App v1.1.0
We continue to explore innovative approaches to improve account security on EOSIO. On January 18, 2020, we released Tropical Stay App to v1.1.0. The Tropical Stay Example Application provides a guideline for developers on how to integrate multi factor authentication powered by WebAuthn with EOSIO web applications. WebAuthn allows applications to authenticate user credentials by way of hardware devices. This most recent version of Tropical Stay provides examples on how to set up a hardware authenticator, such as aYubiKey or an iOS device with TouchID or FaceID, with WebAuthn to validate account signatures.
We are committed to the ongoing improvement of EOSIO software, tools, and resources. If you would like to offer feedback and work more closely with our team to improve EOSIO for developers, you can send our developer relations team an email at [email protected].
To keep up-to-date with future announcements, you can also subscribe to our mailing list on the EOSIO website. We are excited to be regularly improving the usability of the software for EOSIO developers as we continue to lay a foundation for the mass adoption of blockchain technology.
. . .
Important Note: All material is provided subject to this important notice and you must familiarize yourself with its terms. The notice contains important information, limitations and restrictions relating to our software, publications, trademarks, third-party resources and forward-looking statements. By accessing any of our material, you accept and agree to the terms of the notice.
Send us a link to your project, for consideration in our voting slate. No confidential submissions will be accepted and, depending on how many submissions we receive, we can’t guarantee when or if we’ll get to review each submission.