...
This guide provides an overview of verifying stake addresses for Horizen Super Nodes and Secure Nodes along with links to specific instructions and resources.
...
The Horizen Stake Verification Tool is an application used to verify ownership of a transparent address used to stake ZEN for Super Nodes or Secure Nodes. This feature is known as Single Address Staking (SAS) and provides multiple benefits:
...
In simple terms, a small predetermined amount of ZEN is sent from a stake address and the results are sent to the tracking system to be verified. Once the address is verified it can be populated with one or more stake amounts (e.g. at least 84 ZEN for two Secure Nodes or at least 1500 ZEN for three Super Nodes). Holding more than the required stake for the number of nodes you’re running does not result in any additional rewards.
...
The Stake Verification Tool has three general steps and supports multiple methods to complete the verification process:
Create a stake verification request. This generates the amount needed to send from the stake address either from a wallet or optionally creates a raw transaction to sign.
Send the verification amount from your wallet and obtain the transaction id or sign the raw transaction with your private key using signtxtool (signtxtool can do this offline).
Send the verification request to the desired Node Tracking Servers (include the transaction id if sent from a wallet)
The tracking servers validate the verification request and check the transaction on the blockchain.
...
The node must be configured with the stake address as it normally is
The node must be configured to use the ‘category’ field that is associated with the API subkey used in the verification process for that specific address.
Setting up API keys for Secure Nodes API and Super Nodes API
Maintaining The Balance
...
Only transparent addresses are supported as stake addresses (not private z-addresses).
A stake address must be ‘fresh’. It cannot be an existing stake address used previously by any Secure or Super Nodes.
A stake address cannot be used across both systems, i.e. it can’t be both a Super Node and a Secure Node stake address.
There is no upper limit on the amount in a stake address and any excess ZEN over the amount needed for the associated nodes does not have any advantage or earn any extra rewards.
Staketool does not yet support creating multisignature transactions verifying an address, though it is possible to verify multisignature addresses by manually creating and signing a raw transaction with the required amount. Contact Support for instructions.
The verification process and assignment of nodes to the address requires an API subkey which can be obtained from your hosting provider or created on a tracking system server if you do your own hosting.
Once a verification request has been submitted the transaction must be broadcast to the network and included in a block within four hours.
...
The ZEN address where the stake amount will reside.
A small amount (<0.1 ZEN) to create the verification transaction is needed in this address.
One to five 'payout' addresses.
If more than one payout address is used a percentage of the node earnings may be assigned to each address.
Prebuilt Staketool binaries for your OS from Github or nodejs and the Staketool source code.
The private key of the stake address, unless you prefer to send the verification transaction from a wallet like Sphere by Horizen or use the zen-cli command line.
A Horizen Super Node or Secure Node API subkey. This subkey is provided by your Node hosting provider or, if you host your own nodes, you can create it on the Secure Node API Settings or Super Node API Settings page.
...
The Stake Tool tracks the information about a verification request in local files in the same folder as the application or in files specified on the command line. Verification progress for each system and testnet are saved in different folders under the main ‘verificationfiles’ folder (subfolders are: secure, super, and testnet). If any issues arise, the files can be viewed and status checked. No private keys are ever saved to the files.
...
The My Stakes page also provides a list of nodes assigned to the stake address along with the minimum balance needed to cover all the nodes.Secure Nodes: My Stakes
Super Nodes: My Stakes
A verification request may have one of the following statuses:
...