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

v0.22.0RC1

Pre-release
Pre-release
Compare
Choose a tag to compare
@afalaleev afalaleev released this 25 Jul 17:38
· 12 commits to golos-v0.22.0 since this release
v0.22.0RC1
7eef021
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 HardFork 0.22.0 version

Golos·Core team announced the release of the HardFork 0.22.0 version, in which new functionalities are presented and failures of previous versions are fixed. Updates approved by majority votes of witnesses. The release will happen on 2019.08.15.

The changes for HardFork 0.22.0 version are uploaded to a separate branch. Golos blockchain volunteers can take advantage of the provided changes and independently implement them in the Golos blockchain. The changes include new features for the Golos blockchain, as well as solutions that eliminate failures found in previous versions.

The changes for the HardFork 0.22.0 version

  • New great functionality — «workers», which includes the following procedures:
    • submitting a proposal (an idea);
    • implementation of the proposal;
    • report on the work done by the worker for evaluation it by witnesses;
    • evaluating the work done by the worker;
    • payment of rewards to the SOW author and to the worker for the work done;
    • determination of commission payments to be credited to the workers' fund;
    • protection of the workers fund from the lack of funds to pay for the work performed;
    • termination of payment if the work was accepted hastily;
    • involvement of interested users to raise funds for the implementation of proposals;
    • saving memory resources on witnesses’ nodes;
    • termination of work on the initiative of witnesses;
    • resumption of work on the initiative of the SOW author;
    • simplified procedure for reviewing proposals (ideas) already implemented at the time of their submission;
    • assigning a worker on the initiative of the SOW author.
  • Wider range of deductions from delegation operations.
  • The ability for delegates to set curatorial fees in a wide range.
  • Fixed the bug prevented users from adding comments.
  • Delegation of funds in two ways: with payments to the user's balance or to the balance of vesting.
  • Involving users to support newbies.
  • The new voting procedure for witnesses.

The new «Workers» functionality. Solutions implemented within the «Workers» functionality

The functionality «Workers» allows a user to directly participate in the development of the Golos blockchain technology. The user is provided with the following features:

  • the user can submit a proposal for the implementation of a certain idea to increase the blockchain capabilities.
  • the user can make a statement of work (hereinafter - SOW) for the implementation of the submitted proposal (this may also be a third-party proposal).
  • the user can implement the proposal himself.

Golos witnesses evaluate the user's activities and the user is rewarded according to the result of these activities.

Submitting a proposal (idea) №1017

Solution: A post is created by user. The user marks this post as a proposal for the implementation of ideas in Golos. The user selects the type of the sentence - “task” (a brief idea that has not been executed yet outlined by verbal description) and “premade_work” (already including a specific implementation plan). The submitted proposal should be available for consideration by other users who discuss this proposal in the comments to his post, and evaluate it by voting for / against the post.

The implementation of the proposal №1019

Solution: The user creates a post with a Statement of Work (hereinafter: SOW) in which he describes the steps for implementation of the proposal. The user marks this post as SOW, indicating in it the amount of the payment to himself for the SOW compiled and to the performer (worker) for performing the work on this SOW.
Witnesses vote for SOW, and in case it becomes accepted, funds are allocated from the reward pool for work. The allocated funds are in a «frozen» state, which serves as a kind of guarantee of payment to the worker for his work.
The SOW author can choose a specific worker himself before starting to work on the specific SOW. If the SOW author does not specify the concrete worker, he may be charged by other user. If case the SOW author rejects the assigned worker, SOW post get closed automatically.

Publication of a report on the work done by the worker for witnesses’ evaluation №1022

Solusion: Upon completion of the work in accordance with the SOW, it’s author publishes a post (with a report mark) on the results of the work done. The result is evaluated by independent witnesses’ voting.

Evaluating the work done by the worker; №1023

Solution: Witnesses vote on the result of the work done on specific SOW. In case of acceptance of the work (outlined by the majority of upvotes) both the SOW author and the worker are rewarded. In case of failure to accept work (outlined by the majority of downvotes), the SOW is closed automatically.

Payment of rewards to the SOW author and to the worker for the work done №1024

Solution: Payments to authors and workers are carried out either at a time, or to separate parts in accordance with specific time intervals individually specified by the SOW author when filling the SOW data in.

Determination of commission payments to be credited to the workers' fund №1061

Solution: When voting, witnesses set the amount of deduction (in percent) from each of funds (posting reward fund, Vesting fund, witness’ fund) to the worker fund. The resulting percentage is determined by the median, like the other settings in chain_properties. There are no restrictions (limits) implied.

Protection of the workers fund from the lack of funds to pay for the work performed №1073

Solution: When witnesses’ voting for the SOW proposed takes place, the commission is forecasting whether there will be enough funds to pay for the work. In case of prediction of fund shortage, the SOW is not accepted.
When witnesses vote for SOW, the amount of reward for the work will be taken into account when forecasting the fund and adopting the other SOW.

Termination of payment if the work was accepted hastily №1105

Solution: In case the witnesses commission had mistakenly voted to accept the result of the work given in the report, and later realized that the decision was incorrect or simply premature, the payments already made will be cancelled.

Involvement of interested users to raise funds for the implementation of proposals №1107

Solution: In case a proposal is getting enough user attention, but lacks the worker pool fund for its realization, any user can contribute to this fund from his own balance sheet.

Saving memory resources on witnesses' nodes

№1126, №1169
Solution: The witness can enable or disable the automatic deletion of outdated information (for example, such information as voting results or payments for already closed SOW).

Termination of work on the initiative of witnesses №1258

Solution: Witnesses can vote to stop work if there are no results for this work.
The funds allocated for this work will be unlocked and allocated for other SOW when forecasting funds for them.

Resumption of work on the initiative of the SOW author

№1254
Solution: When being confident in achieving a positive result of the work, the SOW author can notify witnesses about this by labeling the «Work In Progress» status of the work in until it’s closed.
Such status does not restrict witnesses from further voting to discard the working process кegarding this SOW . However, setting this status notifies all the witnesses who will vote later.

Simplified procedure for reviewing proposals (ideas) already implemented at the time of their submission

№1270**
Solution: The author of the proposal creates a post with the «premade_work» mark. Only he is empowered to publish a SOW related to it which also serves as the result. After a SOW gets checking by witnesses, it is sent out for proceeding with rewards.

Assigning a worker on the initiative of the SOW author

№1281**
Solution: The author of the SOW may represent the worker to the witnesses even before accepting the work by them (for proposal with the «premade_work» type, the appointment of a worker is mandatory).

Miscellaneous

Wider range of deductions from delegation operations

№1008
Solution: The limit (maximum 80 %) on the restriction of interest for witnesses, which is delegated to the vesting, is excluded. Now the witnesses can set the boundaries of the percentage of fees for delegated vesting in the range from 0 to 100 %

The ability for delegates to set curatorial fees in a wide range

№1009
Solution: Exclusion of the limit (25 %) on the optional witnesses’ limiting of curatorial deductions. Now witnesses can set the boundaries of curatorial deductions in the range from 0 to 100 %.

Fixed the bug prevented users from adding comments №1010

Bug description: If the user has exceeded the threshold of his activity (bandwidth) for posting, then despite the fact that another threshold of his activity for posting comments has not been exceeded he also could not previously add comments to posts.

Solution: The correlation between user activities when posting and commenting is eliminated.

Delegation of funds in two ways: with payments to the user's balance or to the balance of vesting

№1045
Solution: The setting has been added that allows you to send payments not only to the one who delegated funds, but also to the vesting balance.

Involving users to support newbie

№1014
Solution: When voting, the curator determines the share of the deduction (as a percentage) from his reward, which will be subsequently transferred to the author to support him. Percentage rate is not fixed and can be updated at any time. When paying for the post, the author is charged this amount, with the only exception when the penalty box is set not in favor of the author, but in favor of the «whale» curator or foundation.

The new voting procedure for witnesses

№820
Solution: The new voting procedure for witnesses has been implemented.
The voting algorithm:
- A single user can vote only for one witness.
- User can change his/her opinion and re-vote for another delegate during the voting process.
- At the first or repeated (in case of re-ballot) voting at the user, the GP tokens are recalculated.
- Recalculation of GP tokens from other users does not occur.

Notes

  • The implementation of this functionality starts off straight after the nodes of the chain fully transition to the new code. Voting for witnesses is the will of the holders of Golos tokens, respectively, each of them should independently and consciously make a decision on the choice according to the new rules.
Assets 2
Loading