Skip to content

Instantly share code, notes, and snippets.

@kaypon

kaypon/masternode_info.md

Last active November 1, 2018 14:58
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kaypon/0c5a95c02211fa9093bbf636010aa7c0 to your computer and use it in GitHub Desktop.
Save kaypon/0c5a95c02211fa9093bbf636010aa7c0 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
masternode_info.md

Masternode Info

This is an official statement from the ANON core dev team, please read and ask questions on proper media channels.

Intro:

ANON core dev team has been hard at work, focusing mostly on improvements to the network and future upgrades. Unfortunately, we have noticed a lot of confusion in the community about how to properly operate and maintain an ANON masternode.

It is important to understand, your masternode must be actively operated and maintained. Actively maintaining and operating a masternode means the following:

  • You must remain informed regarding the ANON network.
  • You must keep your masternode and sentinel up-to-date with latest releases and versions.
  • You must play an active role in the governance and proposals of the network.

Why all these responsibilities?

Running a masternode is an active support to the ANON network. They are essentially the backbone's strengthening the network. Masternode operators who are not informed are essentially holding back ANON's full potential. Hence, here we advocate and strongly urge all masternode operators to stay informed and regularly update and maintain their masternodes.

Reasons:

ANON is a new and rapidly growing blockchain, the community and dev team have big aspirations and goals for the future of the project. In order to maintain continuous growth, we must ensure that all participants of the network are regularly updating their nodes (as mentioned above).

The ANON dev team has conducted a series of statistical analysis on the overall network participation and masternode health status.

Stats:

Recorded on 10/30/2018

Current network protocol version: 180005

Status Masternodes %
Running Optimally 1191 55%
Need Maintenance 959 45%

Total MasterNodes : 2150

Understanding update types:

There are two major types of upgrades and updates. They are VERSION updates and PROTOCOL updates and they work as follows:

VERSION updates

Version Updates provide new features and improvements. These do not update your protocol version. (Current network protocol version is 180005)

PROTOCOL updates

PROTOCOL updates also provide critical bug fixes, however, the main focus is to update the protocol version. These do update your protocol version. (Current network protocol version is 180005)

The 45% that need attention:

We urge that all masternode operators perform a "spring cleaning", and please check your ANON full node and masternode protocol versions. If they are not up to date, please update them.

Please be aware the latest versions are:

Call to Action:

We ask that you please check your masternode version using the cli command getinfo, and ensure that you are on the 180005 protocol.

As a reminder, whenever you update your masternode protocol version you MUST update your local wallet and full-node, as well as reissue the start masternode command.

Links:

A full masternode and sentinel update script can be found at: mn_sentinel_update_script.md

Updating sentinel guide can be found here: sentinel_guide.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment