EOSIO.Contracts v1.9.0-rc2 Release Notes
Pre-releaseThis is a RELEASE CANDIDATE for version 1.9.0. The latest STABLE release is v1.8.1.
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
When someone outbids an existing account name, the system contract generates a deferred transaction containing the eosio::bidrefund
action to return the funds of the account that was outbid. In prior releases of the system contract, this action was authorized by the active
permission of the eosio
which meant the CPU/NET costs of the entire deferred transaction was billed to the eosio
account. As of this release, the authorizer of the eosio::bidrefund
action is the active
permission of the account that was outbid (#383).
Other changes
- (#354) Change pronoun in buyrex Ricardian summary - v1.9.x
- (#360) [1.9.x] Test metrics fix
- (#356) Add eosio.contracts documentation content to release/1.9.x
- (#373) [1.9.x] Fix for forked PRs.
- (#379) [1.9.x] CI/CD: switch from gke to eks
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-rc1. To also compile the unit tests, first build and install eosio v2.0.0-rc2. The eosio.bios and eosio.system contracts in particular also require that the WTMSIG_BLOCK_SIGNATURES
consensus protocol upgrade has been activated on the EOSIO blockchain before they can be deployed.
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.