📝 HF 0.2 Some Clarity and Soberity (GOLOS)

Due to the difficulties with the dates of the expected HF and facetiousness of perpetual date movements we’ve decided to publically announce the HF date 7 days before the final tag for HF appears on github. Such practice will apply to all future hardforks (which will contain up to 4-5 significant updates, as was announced at the fest). The only difference would be with that date of the following hardforks will be announced not after the appearance of the final tag, but after the first release candidate.

At the moment RC3 is no longer relevant. Several critical errors were found and corrected there. Before releasing RC4 we still need to fix the error with restarting the node, and incorrect calculation of rewards.

We are talking about several days before the appearance of RC4. Delegates will be able to find RC4 on the github release (it will be also forwarded into the delegate channels by someone from the golos core team, as usual).

PS - some clarification about info instruction and assert exception, this is normal since the node starts operating “normally” only after updating to version 17.

PPS - after a request by @vik I remind you that the Golos core team has bounties (rewards) for finding and public fixes of bugs. Bounties usually are 25000 GOLOS tokens. This is to announce that all delegates that can publically (but not only) test the testnet and can find and fix bugs (via pull request on the github) can expect a reward.

The following text is from developers.golos.io:

Errors and vulnerabilities
Bounty for fixing critical errors and vulnerabilities in GOLOS blockchain.
Bounty is paid out in Golos tokens for finding critical vulnerabilities in blockchain protocol, as well as finding bugs that affect Golos.io web client. Public proof of found error or vulnerability is the essential requirement for the payment of the bounty.

Vote for our GOLOS witness - BLOCKCHAINED