Posted on

Horizen (Zencash) software update scheduled for release on September 27th 2018

There is a new version of ZEN software (2.0.15) scheduled for release on September 27th, 2018.

All mining pools, node operators, and Swing wallet users must upgrade to ZEN 2.0.15 prior to block 392512 which will occur around midnight on October 10th.

ZEN 2.0.15 replaces the current version 2.0.14, which is set to deprecate (no longer run). The major focus of this version is the new 51% attack prevention feature.

ZEN 2.0.15 replaces the current version 2.0.14, which is set to deprecate (no longer run). The major focus of this version is the new 51% attack prevention feature. This is not a hard fork.


  • 51% attack prevention code
  • Update RPC commands/thread names/messages with new Horizen name
  • Update Horizen logo
  • Fix erroneous log messages on wallet rescan


  • Miners and node operators: ZEND will not work and thus you will not be able to earn ZEN until you upgrade to ZEN 2.0.15
  • Swing wallet users: You will not be able to access your funds until you upgrade to the latest Swing wallet version.

Zen version 2.0.15 is scheduled to be released on September 27th, 2018 to address the upcoming deprecation of the current version on October 10th, 2018.

The release includes the new 51% attack prevention code which has been successfully tested and works as expected. It also includes some backend rebranding updates. Zen 2.0.14 will shut off at block height #392512 around October 10th (near midnight UTC or shortly after) automatically.

All node operators, exchanges, and anyone running the full version will have to update to zen 2.0.15 before then. The new 2.0.15 version will be available at on September 27th by end of the day. Updated versions of the Swing wallet will be available several days after.

Update instructions for node operators and miners will be provided soon.

Posted on

ZenCash (Horizen) To Fight Against The 51% Attack

The past two weeks have been an exciting and trying time for the ZenCash (Horizen) team. However, even in the face of adversity, the ZenCash (Horizen) team continues to thrive and deliver on our promises to you, the community.

Approximately two weeks ago, our exchange partner was the victim of a double spend attack, where a malicious actor was able to spend their ZEN twice. Double spends are possible in all proof-of-work chains due to consensus rules inherited from Bitcoin.

This attack targeted the exchange, not the ZenCash (Horizen) blockchain.

We just want to kill this, we don’t want this ever be a problem again for the industry.  – Rob Viglione, Co-founder of ZenCash (Horizen)

This attack ignited the ZenCash (Horizen) team to create a comprehensive protocol level defensive strategy for our project and for the entire industry. The ZenCash development team has proposed an enhancement to the Satoshi Consensus in order to prevent 51% attacks.

The longest chain rule, or Satoshi Consensus, worked well in the relatively decentralized environment in which it was introduced in 2009.  Mining resources have since concentrated and dropped in cost for lease, such that the original dominant strategy of playing by the rules no longer holds for all proof-of-work (PoW) blockchains that rely on the longest chain rule.  As recent events have proven, in some circumstances it can be economically feasible to launch 51% attacks on operational public blockchain networks.  This paper proposes a novel adjustment to Satoshi Consensus that makes it exponentially more costly, and hence unlikely, to launch such attacks for any proof-of-work mineable cryptocurrency system.


Posted on

Ready for super nodes?

Click here to host a hassle-free secure node or a super node.

During the ramp/beta testing up period, the stake amount will be set at 3 Zen and it will be raised to the correct amount of 500 Zen on July 18th.


  • At least 500 ZEN in a t-address for staking
  • Four CPU cores minimum
  • 8GB of RAM or more
  • 100GB of storage or more
  • Zend: Both IPv4 and IPv6
  • Tracker: either IPv4 or IPv6 similar to Secure Nodes
  • 96% node uptime per earning period
  • Maximum Challenge time of 150 seconds (may be adjusted)
  • Valid, non-expired TLS certificate

If you are setting up a new Super Node:

When the Super Node tracking servers are ready on July 10th, a Super Node can be created and tested to ensure it passed challenges.

  • Set up the VPS following the requirements which are greater than a Secure Node
  • The node must be set up using the new 0.3.x tracker.
  • The tracker prompts for the type of node during setup
  • Only 3 Zen is needed in the stake address until the 18th.
  • The stake address must be different than any stake address used by a secure node.  They will be cross-checked.
  • A small amount of Zen is needed in the node’s private addresses for challenges
  • When the stake is increased to 500 Zen, an Exception will be created and an email sent
  • Super Node Installation Guide (Link available soon)

If you are migrating a Secure Node:

It’s likely you will want to wait until the last moment to migrate a Secure Node to a Super Node. The following general steps are suggested

  • Update the node to the physical requirements for a Super Node
  • When 0.3.0 is released, update your Secure Node and during setup enter ‘secure’
  • The new nodetracker keeps your configuration for each type of node
  • When you are ready to switch to Super Node, rerun the node setup and enter ‘super’ using the new stake address
  • Restarting the tracker will connect to the Super Node tracking servers
  • Once configured like this the node can switch between Secure and Super node types.
  • Migration Guide (Link available soon)

Click here to host a hassle-free secure node or a super node.

Posted on

ZenCash Super node in beta!

Most of ZenCash investors and node enthusiast eagerly waiting for the moment is finally at the horizon. Yes, ZenCash super node will be going live around July 19th.

ZenCash team has announced that super node will be available for beta testing between July 10 – July 18. There is no significant change in the application layer except for the new tracker version. The new tracker version 0.3.0 will be the only change for now. This new ZenCash secure node and super node tracking app allows it the respective nodes to communicate with its corresponding tracking server. It provides data to the server about the node and performs compliance challenges. Nodes that are in compliance receive a percentage of the block rewards. The tracking networks runs on completely separate from the zencash network.

The name of application is changes from secnodetracker to nodetracker. Each nodetracker must have:

  • a unique IP address (v4 or v6) also used by zend
  • about 0.04 ZEN for challenges in one or more z-address on the node

Secure Node – maintain a stake address with at least 42 ZEN – be able to perform challenges in less than 300 seconds – uptime of 92% or greater.

Super Node – a stake address with at least 500 ZEN – be able to perform challenges in 150 seconds or – uptime of 96% or greater.

This new tracker will be used for secure node as well as super nodes. Existing secure nodes may not need to upgrade unless you are planning to host super nodes to same server.


These are instructions to update your tracker software. If you are doing a new install see the New Installation instructions further down or in the online Installation Guide

  • Check the version of nodejs: Run the following command
node -v

Suggested version is 8.11.x since it will have long-term support. Node.js versions greater than this have not been tested but should work.

  • To update or change run:
sudo n lts
  • Change to the secnodetracker folder and update the tracker application. This may be ‘~/zencash/secnodetracker’ if the install guides were followed.
cd ~/zencash/secnodetracker
git fetch origin
git checkout master
git pull

If git complains about overwriting a file use: git checkout -- filename
e.g. git checkout -- package.json
Then run the last 3 above commands again.

  • Add node.js environment variable when updating the npm modules.This will stop the next step from installing development libraries. Install new nodejs module and remove old ones.
NODE_ENV=production npm install
  • Run setup (this will refresh the list of servers) in the tracker’s config folder. You should be able to accept all the previous values. There are two new propmts: the node type (secure or super) and an optional category. The category can be used to help filter your nodes (if you have many) in certain API calls.
node setup
  • Stop the tracker application and restart it

node app

or restart using your management application such as Sysctl or PM2

During the ramp/beta testing up period the stake amount will be set at 3 Zen and it will be raised to the correct amount of 500 Zen on July 18th.


Posted on

Official Guide: Setup ZenCash Secure Node


Here is the official guide to setup secure node. If you know a bit about Linux, you can easily setup secure node by following this guide. If you are not comfortable, we are here to help you. Please visit our hosting service page here. Otherwise, you can continue with the official guide and setup secure node on your own by clicking on the link below.

ZenCash Official Setup Guide



Posted on

ZenCash Mandatory Upgrade: Zen 2.0.14

June 20 UPDATE – We are pleased to announce ZenCash 2.0.14 for Linux is available. All node operators, exchanges, and pool operators must update from the previous version before June 28th when the current version is deprecated and will stop working (at block 332576). – Source ZenCash Blog


To upgrade from any version prior to 2.0.14 you will have to re-clone the repository. The ZencashOfficial/zen repository was replaced by a new repository based on Zcash upstream with a different commit history, merging/pulling is not possible without issues.

Refer to detailed instructions to build from the source to update the zend daemon.

Posted on

What is required to host ZENCash Super Nodes

We are hosting ZenCash Super Nodes – check here!

ZenCash team recently announced the plans to add Super Nodes to the ZenCash network by the end of 2018. This step will place ZenCash to be much more than a cryptocurrency.

An updated white paper has been released this week outlining greater details, for more information please download ZenCash Supernode White paper.

Within just three months of launching their secure node system, ZenCash’s network has reached over 9000+ nodes. If you are interested in hosting your secure node, we are here to help you. Please contact us for more details or visit our

What is a Super Node?


Basically ZenCash Super Nodes will be even more powerful than Secure Nodes, tasked with managing key network and system functions, including hosting multiple services on sidechains, tracking and measuring Secure Node uptime, and queuing the node payment schedule for miners.

Super Nodes will ensure the utility not only of ZenCash as a currency, but also the future services that will be layered in the infrastructure.

What is a requirement for Super Node?

Super nodes must follow higher criteria:

At least 500 ZEN in a t-address for staking
Multiple CPU cores
8GB of RAM or more
100GB of storage or more
96% node uptime per day
Our target Super Node and Secure Node counts are between 2000-2,500 Super Nodes and 20,000-25,000 Secure Nodes, respectively.

When is Super Nodes going to be released?

As mentioned earlier ZenCash team is planning to add this functionality by end of 2018. The testing may begin sometime in July 2018 though.

What is the reward payout for Super Node?

The current block reward will be changed from 3.5% to 10% secure nodes, 10% supernodes, 10% treasury, and 70% miners. Good news, isn’t it? If you would like to find out ROI, you may visit ZenCash ROI Calculator.

An updated white paper has been released this week outlining greater details, for more information please download ZenCash Supernode White paper.

Is TheSecureNodes Team going to provide Super Nodes hosting?

Of course yes, we are, managed services company, we currently provide managed hosting for secure nodes. We have plans in place to start managed hosting for Super Nodes as well.

For any queries please contact us. We are available on WhatsApp as well.


Posted on

Update ZEN Secure node zend daemon

As we all know Zen version 2.0.11 has been released to solves some blockchain indexing issues on secure nodes. The current version 2.0.10 will be deprecated in April and hence all Secure Nodes need to be updated before then.

For higher up-time and better performance, we recommend using Contabo VPS for hosting secure nodes.

Here are few simple steps to update the zend daemon on your ZEN secure nodes:

  • Updating the zend daemon from new APT repo:

The APT repo has just been updated with the SSL/TLS bug fix. To install the updated daemon with minimal downtime you can do the following:

sudo apt-get update
sudo apt-get install zen
zen-cli stop (then wait for 5 seconds)

You can verify that you are at the latest version by running:

zen-cli getnetworkinfo | grep version


  • This process will only work for those who built their zend from source not the APT repo:

To update the zend daemon on your secure nodes you would have needed to have built your zend daemon from source. If you did this, you can update your secure nodes by running the following:

Navigate to the zen directory, if you followed mine or Blockops guides this will be located in the zencash directory:

cd ~/zencash/zen/

Next we need to fetch the updated code:

git fetch origin
git checkout master

Note: if it asks you to ‘git pull’ please run

git pull

Now we need to build the daemon:

./zcutil/ -j$(nproc)

Now we need to stop the zend daemon and update zend and zen-cli binaries in /usr/bin. This can be done by running the following commands, if you use monit to run your zend daemon.

sudo monit stop zend

wait for 5 seconds and then run:

sudo cp src/zend /usr/bin
sudo cp src/zen-cli /usr/bin
sudo monit start zend

If you do not use monit on your secure nodes you can stop the daemon by running:

zen-cli stop

(wait 5 seconds)

sudo cp src/zend /usr/bin
sudo cp src/zen-cli /usr/bin

And finally starting the daemon again:


You can verify that you are at the latest version by running:

zen-cli getnetworkinfo | grep version