[8/18]
We just released mainnet v 2.3.4. There are 2 major changes in this release:
command-line option for the harmony binary.
Rosetta server framework on the node program.

This release requires a manual update of node.sh and harmony binary. The new node.sh is not compatible with the old binary. Please make sure you are updated to the latest binary version before the next mainnet release by following the upgrade instruction in the medium post.

medium - https://medium.com/harmony-one/harmony-release-v2-3-4-1925e2ea4de3
github - https://github.com/harmony-one/harmony/releases/tag/v2.3.4
version
- node.sh: v2 20200811.1
- harmony: v6268-v2.3.4-0-g7a6fd23f

Some update notes:
1. Now harmony binary provides a clean CLI interface to start a node. Users can choose to start node through CLI as an alternative to node.sh.
2. Old node.sh is not compatible with the new binary file. If user choose to run with node.sh, he will need to update node.sh through harmony.one/node.sh
3. This is not a mandatory update, but users are recommended to update the program before August 24th, as we are likely to have some mandatory update after that.
4. For more update notices, please checkout the tutorial here: https://docs.harmony.one/home/validators/node-setup/installing-updating/installing-node/using-binary-cli
kudos to our eng team 🙌🙌🙌

Hello everyone! Now that the network has been running stable for months and most of the validators are settled with their strategy and positions, it’s time to bring back the 7-epoch locking period to fully enforce the network security as originally designed.

Similarly we are introducing the feature of Redelation!

With the restoration of 7 epoch locking period and the newly introduced redelegation support, we are bringing back the security guarantee of the original EPoS model without significantly affecting the existing stakers’ workflow. Learn more here:

https://medium.com/harmony-one/restore-7-epochs-locking-period-with-redelegation-6b15c47c532c

Hi, Harmony mainnet validators, we've just released mainnet binary v2.3.6 (https://github.com/harmony-one/harmony/releases/tag/v2.3.6), which will enable redelegation and 7 epoch locking period
for undelegation at epoch 290 which will happen around Sep 26 5:00 AM UTC. This is a mandatory upgrade with incompatible changes with old version. So please remember to update your node before epoch 290. Cheers!

To all validators, urgent call! Make sure you have the node version below installed. If not, please upgrade urgently to the latest:

./harmony -V
Harmony (C) 2020. harmony, version v6348-v2.3.6-0-gaba83d46 (jenkins@ 2020-09-24T02:51:38+0000)

Check here for instructions on how to upgrade your node version:
https://docs.harmony.one/home/validators/node-setup/installing-updating/upgrading-node
Also check if your nodes are in sync accordingly to blocks on https://monitor.hmny.io/status

@here We've just published this urgent release to fix a non-deterministic map order error on the the receipt data of delegation transactions. It was causing some nodes not able to verify blocks randomly on delegation transactions which involved the new redelegation logic. Please update with this latest binary ASAP to avoid having further signing issues: https://github.com/harmony-one/harmony/releases/tag/v2.3.6-2. Thanks.

new release: https://twitter.com/leo_hao/status/1315782907198238720?s=20

Dear Validators, for those who are still using node.sh script, a major change will happen shortly. While we strongly recommend that those who are still using it migrate to the node binary, if you are still running the old node.sh script for any reason, check the changes below!

The new node.sh version will download the latest node binary version available and run the binary. Downloaded binaries are saved in staging/ directory. This new version also adds a placeholder for btcrelay and ethrelay.

How to check all node.sh arguments:

./node.sh -h

For now on, all arguments will be passed directly to the node binary. Previous node.sh arguments are deprecated.

How to check all node binary arguments:

./node.sh validator -h

How to run a Validator:

./node.sh validator

How to download the latest node binary version:

./node.sh -d validator

How to run an Explorer on Shard 0:

./node.sh validator --run explorer --run.shard=0

Make sure that you change your Systemd file accordingly!

Usage:

./node.sh [OPTIONS] PROCESS [ARGS]

PROCESS can be: validator/harmony, btcrelay, ethrelay

OPTIONS:
   -h             print this help and exit
   -d             download only (default: off)
   -v             print out the version of the node.sh
   -V            print out the version of the Harmony binary

ARGS will be passed to the PROCESS.

Ex:
   ./node.sh -d validator
   ./node.sh validator -h
   ./node.sh validator --run explorer --run.shard=0

Please check the release v3.1.0 and upgrade your validator node. This is a mandatory upgrade.
https://github.com/harmony-one/harmony/releases/tag/v3.1.0

Instructions on how to upgrade here:
https://docs.harmony.one/home/network/validators/node-setup/installing-updating/upgrading-node

Calling all validators, if you don't have upgraded your validator please do so now. We have almost 50% of the validators on the correct version.
You can find the latest version here: https://github.com/harmony-one/harmony/releases/tag/v3.1.0

Please upgrade your nodes as soon as possible to version v3.1.0. Nodes that don't upgrade will STOP signing at Epoch 442 around Thursday Feb 4th 2020, 11AM PST.

~30% of nodes are still on an old version.

https://github.com/harmony-one/harmony/releases/tag/v3.1.0

Instructions on how to upgrade here:
https://docs.harmony.one/home/network/validators/node-setup/installing-updating/upgrading-node