Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

EOSIO.Contracts v1.9.1 Release Notes

Compare
Choose a tag to compare
@blockone-devops blockone-devops released this 03 Feb 15:55
· 98 commits to master since this release
f6578c4

The eosio.system and eosio.bios contracts contained in this release can only be deployed on an EOSIO blockchain after the activation of the WTMSIG_BLOCK_SIGNATURES consensus protocol upgrade.

System contract

A bug in the producer scheduling logic in v1.9.0 of the system contract has been fixed (#446). The bug may be triggered under certain circumstances when upgrading from system contract versions v1.8.x or earlier to v1.9.0. Observable side-effects of the bug, if triggered, including a pause in block producer payments, producer schedule changes, and the closing of name auction. Simply upgrading the system contract to the v1.9.1 version would resolve the issue and automatically resume those processes.

Other Changes

  • (#431) [1.9.x] Wait for CDT binary.
  • (#443) [1.9.x] Actions for community PRs.
  • (#436) docs: clean up @details for release/1.9.x

Dependencies

This release depends on eosio.cdt v1.7.x and (optionally) on eosio v2.0.x. To compile the contracts in this release, first install eosio.cdt v1.7.0. To also compile the unit tests, first build and install eosio v2.0.1. The eosio.bios and eosio.system contracts in particular also require that the WTMSIG_BLOCK_SIGNATURES consensus protocol upgrade (first introduced in eosio v2.0.0) has been activated on the EOSIO blockchain before they can be deployed. When starting a fresh blockchain, an older version of the eosio.bios contract (v1.7.x or v1.8.x) could be used to first activate the WTMSIG_BLOCK_SIGNATURES protocol feature.

Disclaimer: All repositories and other materials are 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 repositories and other materials, you accept and agree to the terms of the notice.