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

EOSIO Contracts v1.2.0 Release Notes
Compare
Choose a tag to compare
@arhag arhag released this 02 Aug 01:35
· 925 commits to master since this release
v1.2.0
7f1aae0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

System contract

The setramrate action will now first update the RAM supply based on the old rate prior to changing the RAM growth rate to the new rate specified in the action. Other improvements were also made to the implementation of setramrate so that the instantaneous RAM supply never temporarily lags behind (because of missed block production slots) what it should be at the time of buying or selling RAM.

Due to initial over-conservative estimates of the amount of RAM overhead costs per account, 1400 extra bytes RAM was identified to be safe to return to each account. However, because the amount of bytes charged for the fixed overhead of creating account is part of the protocol, it would require a consensus-breaking change to reduce the charged amount.

Instead, this system contract upgrade effectively achieves the same results by gifting all accounts a free 1400 extra bytes to their RAM quota. All new accounts will have the additional 1400 bytes of RAM from the very beginning, which effectively drops the minimum RAM requirements to create a new account by 1400 bytes. For existing accounts, the same RAM quota increase of 1400 bytes will be reflected on their account the first time that they sell ram, buy ram, or delegate/undelegate CPU/network bandwidth.

Dependencies

This release depends on EOSIO.WasmSDK v1.1.x and a version of EOSIO no older than v1.1.2. To compile the contracts in this release, first build and install EOSIO.WasmSDK v1.1.0 and EOSIO v1.1.3.

Assets 2
Loading