Skip to content
This repository has been archived by the owner on Oct 4, 2019. It is now read-only.

v0.18.0

Compare
Choose a tag to compare
@afalaleev afalaleev released this 15 Jun 15:43
· 589 commits to master since this release
26c081f

GOLOS·CORE Equality HF·18 Release Notes

This page contains general information about a new BlockChain version from Golos·Core,
based on new realised features and named as HF·18. Golos·Core recommends all witnesses,
seed nodes and anyone else who uses the witness plug-in have to update to HF·18.

Release date is schedule for 20 June 2018 12:00:00 MSK

Reindexing

HF·18 requires reindexing from all previous versions, except v0.18.0RC3

Updating from previous version

See build instruction

New HardFork operations and opportunities


1. VESTS Delegation

1.1. Delegation operation

This operation is used to delegate for a time a part of VESTS to another account as if that account owned this VESTS and could dispose it. The delegated VESTS can be back to lender after a time. The active key is required to perform this action.

1.2. Update delegation operation

This operation is used to update the VESTS amount. The active key is required to perform this action.

1.3. Delete delegation operation

This operation is used when the lender changes her/his decision and wants to withdraw back the delegated VEST. As soon as the operation starts the VEST will immediately be withdrawn in full and be back to lender after a time. The active key is required to perform this action.

1.4. Account create with delegation operation

This operation is used to create a new account while this time the creator can also delegate a part of her/his VESTS to the new account. The creator has to use the active key and pay the creation fee are required to perform this action.

2. Preventing various abuse kinds of the VEST delegation operation

This feature has been implemented in order to prevent various fraud operations (or abuses) related with transfering delegated VESTS from account to account, as well as cashing VESTS into Golos.

3. Modified method for determining the cryptocurrencies ratio

This feature has been implemented in order to provide more accurate pricing policy for Golos and GBG on the stock exchange. The meaning is while determining the cryptocurrencies ratio, only actual values are used in database.

4. Ability for users to edit their profile by using the posting key

This feature allows a user to edit the profile fields by using the posting key.

5. Proposed transaction

5.1. Create proposed transaction operation

This operation allows a user to propose a transaction on the blockchain which consists of multiple operations and requires approval of multiple accounts in order to execute. Each operation from the transaction requires an approve of the author whom the operation is intended. The active key is required to perform this action.

5.2. Update proposed transaction operation

This operation allows the author, as well as other participant of the transaction, to change their own decisions and update the signatures before the expiration time. The key type which is required to perform this action, depends on an operation in the proposed transaction.

5.3. Delete proposed transaction operation

This operation is used to stop performing the proposed transaction if it takes no sense in continuation. The proposed transaction may be deleted by either author or any participant. The active key is required to perform this action.

6. Ability for users to update their posts or comments regardless of when they were published

This feature allows the users to update their posts or comments regardless of when they were published and keep their in up to date.

7. Expansion operation of the parameters list which values are set by delegates voting

This operation is used to support a more extensive parameters list which values are determined by Golos delegates voting. The active key is required to perform this action.

8. Increasing system performance due to placing frequently and rarely used database fields in separate objects

The meaning of this fix is to place frequently and rarely used fields into separate objects. This provides loading into shared memory only the object with frequently used fields, not all of fields. It takes much less time for processing the blocks and allows to increase system performance, while voting.

9. Improving API protocol performance by reallocating some methods between plug-ins to use them more effectively

9.1. Removed unused fields from some methods

The fix allowed to move the methods between plugins in order to release some unused fields from the methods and then delete them. This allowed also to reduce the load on used memory.

9.2. Index operations for blocks and accounts are placed in separate plug-ins

This fix allows the user to form a request for obtaining information about operations of the transactions (or blocks) without receiving unnecessary history of accounts. This allows also to decrease the server and memory loads and increase system performance.

10. Using tags to create requests for obtaining the necessary information

Methods that process tags as well as methods that provide access to root elements are placed in separate plug-ins. This reallocation allows the user to pull out just a needed part of the content while searching.

11. Getting shared memory status

This fix allows a user to form a request to the blockchain for getting memory status.

12. Ability to paginate private messages and send them out to user's screen

This feature allows a user to pull out her/his private messages from whole list of outgoing (or incoming) messages and paginate them while viewing.

13. Improving storage subsystem of chain blocks

This fix provides simultaneous access to read data from the file where is located a chain of packaged in a certain order signed blocks. Blocking access to the file is possible during the write operation only.