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

EOSIO Contracts v1.1.0 Release Notes
Compare
Choose a tag to compare
@wanderingbort wanderingbort released this 11 Jul 22:43
· 960 commits to master since this release
v1.1.0
e8e687a
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.

Token contract

In case that action transfer needs to create new database row for storing user's balance, the contract bills storage of the row to the user which balance belongs to, if the user's authorization was provided

New action retire introduced, it removes tokens from circulation

New action close introduced, it removes balance for given account and token from the database and frees storage. action transfer no longer removes balance from database even if it reaches zero

System contract

Action sellram provides authorization of caller to eosio.token contract action transfer when transferring system tokens from eosio.ram account in order to avoid billing RAM to eosio.ram account

Action buyram provides authorization of eosio.ram' account to eosio.token contract action transferwhen transferring system tokens from caller to eosio.ram in order to bill RAM to eosio.ram account

Add action setramrate. It allows producers to set the rate at which RAM supply (in bytes) increases per block. Amount of new RAM is calculated and added to the supply every time someone buys/sells RAM. RAM is then priced based on the new supply.

Another change to the system contract is removing multiplying/dividing by 1000 in bancor algorithm connector weights used in calculating RAM price. It can be proved that RAM price remains invariant under this change. However, rounding errors are reduced.

EOSIO.WasmSDK

This repo requires the new eosio.wasmsdk to build the contracts.

Assets 2
Loading