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

v0.19.1
Compare
Choose a tag to compare
@afalaleev afalaleev released this 28 Dec 11:15
· 92 commits to master since this release
v0.19.1
a88d70e
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.

GOLOS·CORE

The new SoftFork 0.19.1 version

***Golos·Core announces the release of the next SoftFork 0.19.1 version, which eliminated the shortcomings identified in the blockchain after releasing HF 19.0. ***

Identified and corrected deficiencies

Fixed bug in the results of calling API functions of family get_discussion_by_* (the issue #1005)

In the results obtained when calling API functions of the family get_discussions_by_ *, fields of predicted payments contained null values, for example:

“pending_author_payout_value”: “0.000 GBG”,
“pending_author_payout_gbg_value”: “0.000 GBG”,
…
“pending_payout_value”: “0.000 GBG”,
“total_pending_payout_value”: “0.000 GBG”,

The values of predicted payments on website golos.io also displayed null.

In SF 0.19.1, the plugins social_network, tags and follow were modified to fix the logic for calculating the predicted payments. This implementation has provided a correct display of field values of the get_discussions_by_ * functions.

Added the «reputation» field to result of calling API functions of the family get_discussion_by_* (the issue #1006)

The reputation field author_reputation was missing in results of the API functions of the get_discussion_by_ * family, due to which information about authors was incomplete.

In SF 0.19.1, changes were implemented in the api-library to ensure correct result.

Fixed an error that occurred when deleting obsolete data (the issue #1007)

When performing an operation in the social_network plugin to remove obsolete data, an error occurred, which broke down the replay process of chain with issuing messages like this one:

th_0  social_network.cpp:522 on_block
926859ms th_0 database.cpp:1325 notify_applied_block ] Caught exception in plugin: 1020200 missing_object: Missing object
Missing comment with id "25"
    {"type":"comment","id":25}
    th_0  database.cpp:660 get_comment
    {}

The cause of the error was an attempt to access an object that had already been deleted. This disrupted synchronization of a node with network. The bug is fixed in SF 0.19.1.

Improved control of transaction serialization result (the issue #823)

Sometimes the user needs to verify that a transaction is correctly serialized into a binary data stream (for example, when a node does not accept user-signed transactions) to get a hash amount..

The existing way to validate the serialization of a transaction is based on calling database_api :: get_transaction_hex. Disadvantage of this method is that the get_transaction_hex function also adds the signatures field to overall serialization result, which makes it difficult to verify the result. To verify correctness of the transaction hash amount and obtain transaction signature from it, a user needs to add the chain_id byte array to the result.

In SF 0.19.1, at the request of users, the transaction signature has been removed from result of the database_apt::get_transaction_hex function for serializing the transaction. It was decided not to add chain_id to the binary serialization result, as this value is already present in the response of database_api::get_config function.In addition, the API method database_api :: get_transaction_digest has additionally been implemented to extend functionality, whose result can be used to generate transaction signature on a client side.

Assets 2
Loading